KTA Job 'State' Being Set Before Precondition Is Met
A TotalAgility (KTA) activity is configured with a Precondition for a process event and a job State to be changed when the activity becomes pending, but the job State is set even before the Precondition is met. Why does this occur?
The Precondition and Set State options work independently of each other, so whether or not the Precondition is met, the State will be set because the "Set State" option happens when the activity becomes available/pending. An activity becomes available as soon as the activity before it completes and the job moves to the next activity. Due to the Precondition the activity will remain in a 'pending' status with an 'Awaiting Event' status. At this point, though, the activity is considered 'available' and 'pending' so the State will be set. The following information is from the KTA Online Help regarding what functions occur when an activity becomes available. Note that setting the State happens when the activity becomes available/pending.
Configure the properties of an activity to record once it becomes available.
A process event to record once the activity becomes pending.
A milestone to record as achieved once the activity becomes pending.
Calculate or record an achieved milestone date either upon one activity being completed or another activity starting. For example, in a software project, a set of activities must be completed or become pending before you can achieve the Code Complete milestone. Recording milestones depends on the configuration of process activities at design time.
Note: All nodes can have completed milestones except the decision and end nodes, which can only have pending milestones.
If selected, calculates the score once the activity becomes pending.
A state to record once the activity becomes pending. See Associate States.
Level of Complexity
Add any references to other internal or external articles
Article # 3046333