Process Configuration: Behavior: 'server' vs 'client'
In the Project Area / Process Configuration / Operation Behavior / Operations table, there is a list of operations for which preconditions can be set. Unser Source Control there are two rows for code delivery - one marked (server) and one marked (client). I assume this shows whether the precondition checking is performed by the RTC client or server process? I want to set the precondition that a change set must be associated with a WI for delivery - should I set this on the server, the client or both, and why?
2 answers
A benefit of a client precondition is that it can interact with the user
(a server precondition cannot). A benefit of a server precondition is
that it is guaranteed to be run (you cannot count on a client
precondition being run, because a user could write/obtain a client that
does not to support the running of client preconditions).
Cheers,
Geoff
amulholl wrote:
(a server precondition cannot). A benefit of a server precondition is
that it is guaranteed to be run (you cannot count on a client
precondition being run, because a user could write/obtain a client that
does not to support the running of client preconditions).
Cheers,
Geoff
amulholl wrote:
In the Project Area / Process Configuration / Operation Behavior /
Operations table, there is a list of operations for which
preconditions can be set. Unser Source Control there are two rows
for code delivery - one marked (server) and one marked (client). I
assume this shows whether the precondition checking is performed by
the RTC client or server process? I want to set the precondition
that a change set must be associated with a WI for delivery - should
I set this on the server, the client or both, and why?