Multiple preconditions for operation behaviour.
![]()
I am trying to set-up an operation behaviour when delivering change-sets to a stream. First, what is the difference between Deliver (client) and Deliver (server) ? Does client mean the Eclipse IDE ? But, the Web front end could be a client too.
The second question is about the description of Pre-conditions as seen in the page for setting operations from the Eclipse client (emphasis mine). Preconditions are checked before running an operation; follow-up actions are executed after. An operation's preconditions and follow-up actions can be configured differently for each role. Note that operation configurations completely replace each other; they are not additive. The process runtime will choose the most appropriate operation configuration for the logged-in user and will use only the preconditions and follow-up actions defined in that configuration.The text in bold is apparently referring to the fact the final condition is not a AND of the comprising conditions. So, what happens if multiple configurations are actually provided ? Here is an example. For Deliver (client) and Deliver (server), there is a precondition for to have a Work Item and comments. (I presume, comments are for change-sets ?). Then, there is one for the Work Item to have an Approval. My requirement is to have both. That is, a change set should be delivered if an associated Work Item exists AND the Work Item has an approval. So, if both preconditions have been selected, then exactly what is in effect ? I seem to have achieved my goal by selecting the precondition for approval; but, I do not understand what do the options on this page actually mean. |
Accepted answer
2 other answers
![]()
Ralph Schoon (61.8k●3●36●43)
| answered Dec 28 '12, 2:05 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please have a look at https://jazz.net/library/article/292 for how that works. Also look at https://jazz.net/library/article/291 .
Comments And be aware that if a higher priority role has a configuration, configurations for lower priority roles are not going to trigger. E.g. If you have a precondition for TeamLead, the preconditions for Everyone won't trigger for someone wit TeamLead role. |