Subprocess Properties Process Tab
When creating a subprocess task, you can associate the subprocess with a list of process and rule combinations, and sequentially order them. The first rule an order satisfies defines the process that is used as the subprocess.
Select the Properties view Process tab to define the values for the following:
Field | Use |
---|---|
Pivot Node |
Click Select to access the Order Template Selection dialog box, where you can select the data element on which OSM will spawn the individual instances. For example, if you have subprocess that will create an email address for every person in a list, you might select the node Person as the pivot node, so that the subprocess repeats, spawning an instance for each person. |
Sequential |
If you anticipate that a large number of task instances will appear in the Task web client Worklist, and you prefer that the system display the instances in the worklist one at a time, you can specify a sorting option. Specifying a sorting option here causes OSM to execute the task instances sequentially, instead of in parallel, and to display the individual instances in the worklist one at a time, in the specified order. As you complete each task instance, OSM spawns the next instance. You can select one of the following sorting methods: Non Sequential: The subprocess initiates every instance simultaneously. No Sorting: The Task web client Worklist displays the instances of the task in the order that they are spawned. Ascending: The Task web client Worklist displays the instances of the task in ascending order, based on the attribute (date, alpha, or numeric) of the data element that you select in the Sort Element field. Descending: The Task web client Worklist displays the instances of the task in descending order, based on the attribute (date, alpha, or numeric) of the data element that you select in the Sort Element field. |
Sort Element |
If you selected a reusable structure as the pivot node, click Select to identify which of the data elements the system should use to determine the order in which to display the individual task instances in the Task web client Worklist. This option is available only when you sort the task instances in descending or ascending order. For example, consider that you have three levels of DSL service: Regular, Gold, and Platinum. You want to ensure that customers ordering the Platinum level of service have priority over the lower two levels. In the Pivot Node field, you might select the reusable structure called service_type, which contains the attributes regular, gold, and platinum. In the Sequential field, you can select ascending, then select the value platinum in the Sort Element field to ensure that the orders with the Platinum level of service are initiated first. |
Continue if rule failed |
Select if want the process to continue if none of the rules associated with the subprocesses equate to True. |
Association |
The Association table lists the process and rule combinations that determine which process the system will initiate when a rule in the table evaluates to True. The system evaluates each rule in the order that they appear in the Association table. When a rule evaluates to True, the system runs the corresponding process and ignores the remaining processes. You can prioritize the processes listed in the table by using the Move Up and Move Down buttons. Click Add to display the Add Rule and Process Association dialog box. In the dialog box, indicate which rule and process combination triggers the subprocess. To change the order of the process rule combinations, highlight a combination and click the Move Up or Move Down button. Select a process rule combination and click the Modify button to change the combination pair, or click the Remove button to delete from the list. If you drag a process from the Studio Projects view on to a subprocess entity, the system automatically adds that process to the Association table, and uses null_rule as the default rule. Select the table row and click Modify to change the rule and process combination. Note: You can manipulate ordered tables in Design Studio using keyboard controls. For example, you can launch the Add Rule and Process Association dialog box by pressing the Insert key on your keyboard. You can highlight a table row and press the Delete key to delete a process and rule combination from the table. Use the Control key in conjunction with the arrow keys to select one or multiple table rows and move those rows up or down in the index order. |