Hi everybody,
Thanks a lot for input!
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
Here are some other transitions I have found from examples and documentations - next to 'approved', 'rejected', 'updated':
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How are you implementing this workflow in Confluence? With Comala workflows?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.