Create Definition#

The creation wizard has four tabs at the top: General Data, Pre-Conditions, Acceptance Gates, and Post Action Validations.

Steps#

1. General Data#

The General Data tab is where you configure the core behavior of the Definition. It contains the following sections:

• The Definition contains basic identification and validity settings for this Definition.
• The Context determines which Automation Instances this Definition applies to. When the Definition is saved, the system resolves the context and creates one task per instance found. Tasks are de-duplicated, so if the same instance appears more than once in the resolved list, only one task is created. See Context Resolution for guidance on configuring this field.
• The Detector defines what "ready" means for the instances in scope. The system evaluates the detector on every polling cycle and only proceeds when the result is true. See Detectors for guidance on configuring this field.
• The Action is the maintenance operation to perform on the instance once all conditions are met. Exactly one Action is configured per Definition, and it determines what the system will do to each target instances. See Actions for guidance on configuring this field.
• Up to four Notification templates can be configured, one for each point in the task lifecycle. Each field accepts the name of an existing MES Notification Template. See Automation Scheduled Action for guidance on configuring templates and available tokens.

2. Pre-Conditions#

In the Pre-Conditions tab you can configure multiple or no Pre-Conditions. See Pre-Conditions for guidance on configuring this field.

3. Acceptance Gates#

In the Acceptance Gates tab you can configure multiple or no Acceptance Gates. See Acceptance Gates for guidance on configuring this field.

4. Post Action Validations#

In the Post Action Validations tab you can configure multiple or no Post Action Validations. See Post-Action Validations for guidance on configuring this field.

5. Save#

Select Save to create the Scheduled Action definition. The system then runs Context Resolution and creates tasks for each entity instance.