How to Define Steps and Actions

Start and end steps are always required and are automatically created even if you do not explicitly define them. You can add and define intermediate steps. Each step can consist of multiple actions that must be performed by an assignee or CA Clarity PPM.

You can create custom actions that include custom GEL scripts. The start and the end steps can be contained in a group.

You can use the previous value comparison of an attribute in pre or post conditions to check if in the same step has modified the attribute value rather than to check the overall object update.

Do the following to define steps and actions:

  1. Define step properties.
  2. Define pre-conditions.
  3. Create step actions.

More information:

About Steps

About Groups