...
To create a new workflow group configuration, click the New Configuration button in the upper left part of the Desktop the Desktop window, and then select Workflow Group from the menu. To open an existing workflow group configuration, double-click the workflow group in the Configuration Navigator. The workflow group configuration opens in a tab.
...
- A workflow member might still be running according to its configuration , or as a member of a workflow group in the system.
- A workflow group member might still run as a member of another workflow group in the system.
...
- Right-click the member that you want to remove in the it in the Group Members list in the Members tab in workflow group configuration.
A menu appears on your screen. - Select the option Remove Member .
You will get a question if you are sure you want to remove the member. - Click Yes if you are sure.
...
| Note | ||
|---|---|---|
| ||
If you use the Continuous Workflow Execution setting, you can override this behavior by allowing scheduled workflows to workflows to execute even though all workflow members are not finished, see the section below, Execution, for further information. |
To configure members' execution order:
- Right-click on a member in the Group Members pane in the Members tab.
A drop-down menu opens.
- Select the option Prerequisites .
The Prerequisites dialog box opens.
The Prerequisites dialog box
- Select the check boxes for the members that the current member should follow.
- Click OK .
See the image below for an example of how it may look.
Workflow Group members' execution prerequisites
You can rearrange the members' order of appearance in the Group Members list, by using the Up and Down buttons. When rearranging a list, that is already configured with Prerequisites you will notice that the Prerequisites parameter is removed and a yellow warning icon appears instead. Note that this will not affect the workflow group validity. To remove the notification sign, either open the Prerequisites dialog box and click OK , or - to remove all the notification signs - save the workflow group configuration, and reopen it.
...
Entry | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Max Simultaneous Running Workflows | Enter the maximum number of workflows you want to be able to run concurrently.
| ||||||||||
Startup Delay | If Max Simultaneous Running Workflows is set to a value larger than 1, enter the delay (in seconds) of the execution start for each of the workflows that may run simultaneously.
| ||||||||||
| Continuous Workflow Execution | Select this check box if you want to allow members in scheduled workflow groups to execute on schedule even though all workflow members in the group have not finished execution. This may be useful in case one member is delayed for some reason. In that case remaining workflow members will not be prevented from executing on schedule.
| ||||||||||
Continue | This option activates the default behavior on member abort, which means that the workflow group will run until all its members are fully executed and/or all are aborted.
| ||||||||||
Stop | Select this option to have the workflow group stop when a member aborts. A batch Workflow will finish the current batch and then stop. | ||||||||||
Stop Immediately | Select this option to have the workflow group stop immediately when a member aborts. A batch workflow will stop even in the middle of processing a batch. | ||||||||||
Enable | Select this check box to enable the workflow group execution settings.
| ||||||||||
Distribution | A workflow executes on in an Execution Context. Specific ECs, or groups of ECs, may be specified by the user, or the system the system can handle it automatically. The Distribution settings are applied to all included group members i.e. workflow- and workflow group configurations. When there are conflicting settings, the members that are lowest in the workflow group hierarchy have precedence. When the Distribution settings of workflow group configurations are set on the same level in the hierarchy, they do not conflict with each other.
The following options exist: Sequential - Valid only if Execution Contexts are defined. Starts the workflow on the first EC/EC group in the list. If this EC/EC group is not available, it will proceed with the next in line. Workflow Count - Starts the workflow on the EC running the fewest number of workflows. If the Execution Contexts list contains at least one entry, only this/these ECs/EC groups will be considered. Machine Load - Starts the workflow on the EC with the lowest machine load. If the Execution Contexts list contains at least one entry, only this/these ECs/EC groups will be considered. Which EC to select is based on information from the System Statistics sub-system. Round Robin - Starts the workflow on the available ECs/EC groups in turn, but not necessarily in a sequential order. If EC1, EC2, and EC3 are defined, the workflow may first attempt to start on EC2. The next time it may start on EC3 and then finally on EC1. This order is then repeated. If an EC is not available, the workflow will be started on any other available EC. |
...
Entry | Description |
|---|---|
Day Plans | Use this table to plan timed triggers that will execute your Workflow group. Note that you can define a list of various plans. will The system will pick the plan that meets the top priority according to the section below, Day Plans Priority Rule. Click on the Show... button to open a calendar that displays the Workflow group execution plan, see the figure below, The Execution Calendar. |
Event Trigger | Use this table to define an event execution trigger for the Workflow group, see the section below, Event Triggers. |
Day Plans Priority Rule
The Day Plans table enables you to create a list of different execution schemes of the Workflow group. You configure each Day Plan to any interval between executions.
| Note | ||
|---|---|---|
| ||
Two Day Plans should not contradict each anotherother. An example of an invalid configuration: Day Plan A is set to Tuesdays Off, while Day Plan B is set to Every 5 minutes between 15:00:00 and 15:05:00 on Tuesdays. |
applies the following priority rule for picking a Day Plan out of the list:
- Last day of the month
- Day of month (1-31)
- Weekday (Monday-Sunday)
- Every day
...
- Click on the Show... button beneath the Day Plan table.
- The Execution Calendar opens.
Anchor fig_The_Execution_Calendar fig_The_Execution_Calendar 
The Execution Calendar - A green-colored cell in the calendar represents at least one scheduled execution during that time.
- Click on a green cell.
...
To trigger the execution of a Workflow group you add a row to the Event Trigger table. A row can be either a certain event , or a chain of events, that must occur in order for the Workflow group execution to set off.
| Note | ||
|---|---|---|
| ||
An Event Trigger that is comprised of a chain of events will take effect only when all the events that it includes have occurred. The events that have occurred are stored in memory. When is the system is restarted, this information is lost and none of the events on the event chain are considered to have occurred. |
To Configure configure an Event Trigger:
- Click on the Add button beneath the Event Triggers table.
The Add Event Chain Trigger dialog box opens.
The Add Event Chain Trigger Dialog Box
- Click on the Add button.
The Add Event Selection dialog box opens.
The Add Event Selection dialog box - Select an Event Type from the drop-down list, see Event Fields in 4.2 Event Notifications Configuration.
- Double-click on an entry in the Event Filter table.
The Edit Match Value dialog box opens. - Click on the Add button.
The Add Match Value dialog box opens. - If you want to filter all the events based on specific values of the selected type, enter the values in the Match Value(s) column. Otherwise, if you leave the default value, all the events of the selected event type will trigger the execution of the Workflow group.
- Close all four dialog boxes.
| Note | ||
|---|---|---|
| ||
There are no referential constraints for Event Triggers nor any way to track relations between workflows that are triggered by one another. For example: , Workflow A is defined to be activated when Workflow B is activated. Workflow B might be deleted without any warnings, leaving Workflow A, still a valid workflow, without a trigger. This might happen since value matching is based on a regular expression of the workflow name, and not on a precise link match. |
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||