Versions Compared

Old Version 3

changes.mady.by.user Chooi San Chong

Saved on

compared with

New Version Current

changes.mady.by.user Chooi San Chong

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Entry

Description

Max Simultaneous Running Workflows

Enter the maximum number of workflows you want to be able to run concurrently.

Note
titleNote!

If you do not specify a limit, your specific work environment and equipment will determine the maximum number of workflows that can run simultaneously. This value applies only to the workflow group that you are defining and does not affect members that are workflow groups.


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.

Note
titleNote!
  • If you do not enter any value, a very short delay will be applied by the system, by default.
  • You can assign a Startup Delay regardless of the members' status. Once the delay is up, if the member in turn is disabled, the Workflow group attempts to execute the next member.


Continuous Workflow Execution

Select this checkbox 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. 

Note
titleNote!

This feature is not supported for nested group members, only workflow members.

For a workflow group with a member that is delayed over the next scheduled time, this setting makes the member execute immediately when it is finished, and the group will be in a continuous Running state, not switching to Idle in between executions as is the default behavior.

This needs to be considered when making configurations based on workflow group states.  


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.

Note
titleNote!

This means that groups with real-time workflow members continue to run until all the members are aborted or stopped manually.


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 checkbox to enable the workflow group execution settings.

Note
titleNote!
  • Execution settings that you configure here, only apply to workflow members for which execution settings have not been enabled in the configurations that they are part of.
  • Workflow groups cannot run as stand-alones, and will be executed on the Platformare triggered by the Platform and workflows are executed by EC. For further information about stand-alone, see Execution Context Deployment(4.1).


Distribution

A workflow executes on an EC group. You can specify these EC groups, or the system can select them automatically. 

The Distribution rules are applied to all included group members, such as workflows and workflow group configurations. When there are conflicting settings, the members that are lowest in the workflow group hierarchy have precedence.

When the Distribution rules of the workflow group configurations are set on the same level in the hierarchy, they do not conflict with each other.

Note
titleNote!
  • If you configure the distribution using EC groups, the selected distribution type is also applied to the ECs within the groups.

The following options exist:

Sequential - Starts the workflow on the first EC group in the list. If this EC group is not available, it proceeds with the next in line.

Workflow Count - Starts the workflow on the EC group running the fewest number of workflows. If the Execution Contexts list contains at least one entry, only this/these EC groups will be considered.

Machine Load - Starts the workflow on the EC group with the lowest machine load. If the Execution Contexts list contains at least one entry, only this/these EC groups will be considered. Which EC group to select is based on information from the System Statistics sub-system.

Round Robin - Starts the workflow on the available EC groups in turn, but not necessarily in a sequential order. If ecg1, ecg2, and ecg3 are defined, the workflow may first attempt to start on ecg2. The next time it may start on ecg3 and then finally on ecg1. This order is then repeated. If an EC group is not available, the workflow will be started on any other available EC groups.


...

  1. Click the  (Add) button beneath the Event Triggers table.
    The Add Event Chain Trigger dialog opens.

    The Add Event Chain Trigger Dialog
     
  2. Click the (Add) button.
    The Add Event Selection dialog opens.


    The Add Event Selection dialog

  3. Select an Event Type from the drop-down list. See Event Fields in Event Notifications Configuration(4.1).

  4. Double-click an entry in the Event Filter table.
    The Edit Match Value dialog opens.

  5. Click the(Add) button.
    The Add Match Value dialog opens.

  6. 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 events of the selected event type will trigger the execution of the Workflow group.

  7. Click Add/OK/Close to close each of the four dialog boxes, confirming that your entry is included.

...