In the workflow properties, you can specify the steps where a rule will be used. (This is an alternative to specifying rules as you define the properties of each step.)
TIP The steps must already be present on the workflow map.
To specify steps where rules will be used
NOTE The list of maps is restricted to modifiable maps for you to select steps where a field, attachment, milestone, or rule will be used. Some steps on inherited maps might use fields, attachments, milestones or rules, but the inherited maps that contain these steps are not included in the list of maps because these maps are read only.
CAUTION It is strongly recommended that you do not use Asynchronous Rules with OnSave option because a step which was previously locked will be automatically unlocked after the rule has been executed, which may cause unexpected behavior in your application. When a rule executes asynchronously, the work item is removed from its queue, put into the isi queue for execution by the vwisi process, and then returned to the original queue. During this procedure, it is not possible to retain the lock on the work object, so after the asynchronous rule executes, a work item that was previously locked will no longer be locked by the user. This issue does not apply for rules executed asynchronously Before Execution or After Completion of the step.