Signatories Workflow redesign

[GoogleCodeExporter]

Signatories Workflow
----------------------

Problem
-------

Currently when you add cosignatories to a motion, there is no workflow
for cosingatories to give "consent" for becoming signatories.
Add a consent workflow for cosignatories.

To Do
-----

Current Behavior 
-----------------

MP creates a new motion in the system, the motion is in "draft" state.
The next transition is "submit to clerk".
The system allows the member to "add cosignatory" in "draft" state.
Approval of the 'cosignatories' is not sought currently, and neither 
are they notified that they have been added as cosignatories.

New Behavior
-------------

Note: 
we shall henceforth call 'co-signatories' as just 'signatories'.

(1) 

In "draft" mode -- the owner MP is allowed to add multiple signatories.
 * If there are signatories in "draft" mode -- the workflow allows
a transition called "submit to signatories for consent".
 * If there are NO signatories in "draft" mode -- the workflow
allows a transition called "submit to clerk" (the existing behavior).

So the transitions possible at this point are :

draft -> submit to signatories for consent -> submit to clerk
draft -> submit to clerk

(NOTE: The above transitions happen "serially" NOT in "parallel" )

(2) When draft -> submit to signatories for consent :

  # the signatory MPs get the "signatory" document NOT on the bill/motion 
document in their workspace. The "signatory document" will have the link 
to the bill/motion. They can view the motion (but not Edit it). They get
 2 workflow actions for the "signature-document"; the current status is 
"awaiting consent" :
    * "consent" - marks consent to be a signatory
    * "reject" - does not give consent to be a signatory (NOTE: the 
"awaiting consent", "approve consent", "reject" are states that are on 
"signatory document)

  # when the bill/motion is in "submitted  to signatories for consent" 
the "owner" cannot Edit the bill/motion but the owner may add more 
"signatories". The owner can only "withdraw" (private) the document. At 
the point also the signatory documents in "awaiting consent" state should  
be "withdrawn"

  # The owner MP can review the current approval status of the signatories 
in the "signatory" tab:
      * currently only the list of signatories is shown, so this must
 also show the status of the consent : "awaiting consent", "approved",
"rejected" for every signatory.

  # the "submit to clerk" transition is only available to the owner MP when
at set number of MP, (e.g. 10 in the case of Angola) have "approved" their 
signing. This number must be a customizable parameter per content type 
workflow.

  # If you go into bungeni->members->current->member page, there is a 
"parliamentary activities" tab. If a member is a 'consented' signatory
on a parliamentary item, that parliamentary item must also be listed here.

(3) When draft -> submit to clerk:

  # As before - however the clerk can presently add signatories. This 
should not be allowed anymore in this state.

Original issue reported on code.google.com by ashok.ha...@gmail.com on 27 Apr 2011 at 10:09

[GoogleCodeExporter]

Original comment by ashok.ha...@gmail.com on 4 Jul 2011 at 10:31

• Changed state: TestingFix

[GoogleCodeExporter]

redraft -- needs to be factored into a new state since redraft is not really a 
"draft" state which can be deleted.

Original comment by ashok.ha...@gmail.com on 4 Jul 2011 at 10:35

[GoogleCodeExporter]

Fixed in this series of revisions:
r8266 r8269 r8278 r8283 r8289 r8298 r8299 r8300

Original comment by borona.m...@gmail.com on 9 Mar 2012 at 10:02

• Changed state: Fixed