Confluence Workflow - multiple transitions?

[Sonja Behrmann]

Hi everybody,

1. I aim to expand a default content review workflow (4 statuses) to enable the development from project idea to project charter (within 6 statuses).
   
   Definition ends in reasonable diagram (see below)
   and I wonder
   1. what else transitions (next to 'approved', 'rejected', 'updated') do exist?
   2. how many transitions are allowed (inbound and outbound)/
      / is there a limit of transitions (e.g. 1 x inbound, 2 x outbound)?
      
      
      
      
2. It would be great to have an addition:
   Either by approving the project idea to a 'project'
   or by rejecting the project idea to a simple 'task'
   I want the approving person to manually assign a budget available to project lead (who is to 'finish' the workflow).
   Ideally placed AFTER click to approve by a pop-up window asking for the option (!optional field might be empty) to indicate an amount at free disposal.
   1. Is it possible to arrange that?
   2. if yes, how can I arrange this?

Thanks a lot for input!

[Elena_Lurye]

I used other transitions in my workflows as well. You can specify conditions on your triggers, based  on some events:

(https://wiki.comalatech.com/display/CWL/Conditions)

https://wiki.comalatech.com/display/CWL/Events

For example, you can change state if

1. specific label was added/removed to/from the page
2. you can base state transitions on specific user or group being assigned/unassigned 
3. you can set multiple tasks for a state, and use their completion/expiration time to transition between states as needed (or to send notification emails).
   
   You were asking for available budget assignments - you can accomplish it using tasks. 
   Name each task as your budget proposals. 
   Have a project approve select (complete) specific task and use this completion as a mechanism to change states (and to send out notifications with this budget number..

[Yves Martin]

Here are some other transitions I have found from examples and documentations - next to 'approved', 'rejected', 'updated':

• submit
• completed (from tasks list)
• expired (from due date)

As far as I understand, these transitions are associated to page lifecycle event: https://wiki.comalatech.com/display/CWL/Transitions

They are all referred in "state" macro documentation, mixed with other parameters: https://wiki.comalatech.com/display/CWL/state+macro

If none matches your need, or you want to avoid automated transition from events, the easiest way is to use "state-selection" as child macro in "state": https://wiki.comalatech.com/display/CWL/state-selection+macro

[Nic Brough -Adaptavist-]

How are you implementing this workflow in Confluence?  With Comala workflows?

[Sonja Behrmann]

Yes, Comala Workflow is the plugin. ✔

[Sonja Behrmann]

Do you expect problems due to using this plugin?