Associate states
You can associate single or multiple states with an activity, depending on the path to the activity. Associating states helps in determining the state of activity within a process, especially if an activity becomes pending for the second time. You can associate actions with a state to take place when an event becomes pending, depending on the path to that activity.
- In the Activity properties panel, click the Advanced tab.
- On the State list, select a state to use as the default state for the job when the activity becomes pending.
-
To use the state depending on the origin of the activity, select the state against the origin.
- If no origin-specific state is defined for the activity, the default state is used when the activity becomes pending.
- You can select a different or the same state as another origin, or the default state.
Before specifying optional states, specify the default state for the activity. Otherwise, a message appears.
The Develop Code process includes the following three states: Coding, Reworking and Releasing.
In a normal scenario, to have the job in a Coding state when the Write Code activity is first executed, and in the Reworking state when the Write Code activity is executed a second time, you must add another activity. For example, you would add another Writing Code activity or a .NET action to display the changed state.
In the Develop Code process, multiple states are defined for the Write Code activity. If out of the Rework decision the job takes the True path, the job status appears as Reworking; if the job takes the False path, the job status appears as Releasing.