You can use the Before Activation tab to configure procedures which occur before the Activity workstep is activated.
To configure procedures:
1. The Activation Limit checkbox is only available for a system process, as defined in ProcessType attribute in process properties (see Setting process properties). Select this checkbox and enter a value (greater than 0), which sets a maximum limit that this workstep is executed in loop for a process instance at runtime. To execute the workstep loop indefinitely, specify the value as -1. If no value is specified, the value of the bpserver.ws.max.activationcount parameter in the OEBPS_Home\conf\bpserver.conf file is considered as the maximum limit.
2. Select the Activate On checkbox to enter the date and time when the workstep will be activated. Click the ellipsis button and select one of the following options.
Enter a value option: to open the Activate On dialog box, in which you can select a static date value.
Use a dataslot option: to open the Select Dataslots dialog box, in which you can select any of the DATETIMETZ dataslots listed, to define a dynamic date for the workstep activation.
You can also add, edit or delete DATETIMETZ dataslots. These dataslots are saved as <ActivateOn>@dsname</ActivateOn>.
3. Select the Activate After checkbox to specify the time interval until activation starts. Click the ellipsis button and select one of the following options.
Enter a value option: to open the Duration dialog box in which you can enter a duration value in terms of days, hours, minutes, or seconds.
Use a dataslot option: to open the Select Dataslots dialog box, in which you select any of the INTEGER dataslots listed to define the interval until the workstep is activated. These dataslots are saved as<ActivateAfter>@dsname</ActivateAfter>.
The value of this INTEGER dataslot must be in milliseconds, since this is the unit of time that BP Server expects for the duration until workstep activation. For example, if the workstep is to be activated after two minutes, then the dataslot value must be specified 120,000 milliseconds.
4. You can use the Wait for Condition dialog box to specify a condition to be satisfied before the workstep is activated. Click the ellipsis button to open the Wait for Condition dialog box. Use the Expression Builder feature to define a valid condition.
a. Select a dataslot from the drop-down list on the left (The Basic mode only includes CHARACTER, INTEGER, INT64, LOGICAL, and DATETIMETZ dataslot types; Advanced mode includes all data types). Select an operator. To complete defining the condition, select a dataslot from the drop-down list on the right or enter a value.
b. To add another condition, click and select the And or Or option. To remove a condition, click .
c. To create a condition, click Advanced option by adding specific dataslots or by entering or pasting a condition. You can drag any of the dataslots listed (from the Dataslots section) to the Condition text area and build a condition, for example, jst.getStringDataSlot(“CREATOR”).equals(“Peter”).
d. To check on your expression’s validity, click Validate.
5. You can use the Skip Condition dialog box to define a condition which, when satisfied, allows the performer to skip the workstep before it becomes activated. Click the ellipsis button to open the Skip condition dialog box. Procedures to define a condition is the same as those described for “Wait for Condition” feature.
6. You can use the Execute script box to define the event, which is executed before the workstep is activated.
To define the event, click Add Script. The Graphical Event Logic (GEL) tool appears with the defined event. You can use this tool to configure the action to be executed. For more information, see Using the GEL tool in BPM projects.
Enter a value option: to open the Activate On dialog box, in which you can select a static date value.
and select the And or Or option. To remove a condition, click 
.