Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

Associate Workflow with ArchestrA Events

  • Last UpdatedSep 11, 2024
  • 3 minute read

Use the Associate option to associate a workflow with ArchestrA Events.

The ArchestrA Event association window appears.

To associate a workflow with an ArchestrA Event for a specific event

  1. Select the workflow, and then click Associate from the ribbon.

    Alternatively, select and right-click the workflow, and then select Create Associations.

  2. Click ArchestrA Event to associate the workflow with the ArchestrA Event list for a specific event.

  3. Enter the following details:

    • Event Provider: Select the name of the event provider from which you want to poll for new events.

      The Event Provider field is mandatory, and the maximum length of the event provider name is 250 characters.

      Based on the data available in the ArchestrA Event main list, the Event Provider list is populated. You can add other event providers to this main list, if required.

      Example of Event Providers are InBatch Server or Avantis.

    • Event Type: Select the Event Type of the Event Provider.

      It is the type of event which defines the properties the event will have.

      For InBatch Server, Batch is an event, and possible values for Batch events are such as, Batch, Equipment, UnitProcedure, Operation, Phase, MaterialInput, MaterialOutput, Custom, and BatchError.

      Based on the data available in the ArchestrA Event main list, the Event Type list is populated for the selected Event Provider. You can add other event types for the event provider, if required.

    • Source: Type the Source property name of the event. It is the name of the event provider sending the event. For example, for a Batch event, BatchMngr is the source.

      Select the appropriate operator from the operator drop-down list.

    • Area: Type the Area of the event. Areas provide a key organizational role in grouping alarm information and assigning it to users who use alarm and event clients to monitor their Areas of responsibility.

      The Area object plays a key role in alarm and event distribution. All objects belong to an Area. Areas can contain sub-Areas. Alarm and event clients are configured to subscribe to a set of Areas.

    • Priority: Type the priority for each designated event.

      Priority, which is an integer value from 1 to 999 indicating the severity of the alarm which raises an event. An alarm priority of 1 is most urgent and 999 least urgent.

    • Workflow Version: Select the version of the workflow to be associated with the ArchestrA Event. The workflow will be initiated only if the published version at the time of the occurrence of the event is the same as the version selected here. To trigger the currently published version of the workflow whenever the event occurs, select Latest. When a version is specified, the workflow alerts the latest published version of that version series. For example, if the specified version is 1.1 and the latest published minor version for 1.1 is 1.1.1.3, then 1.1.1.3 is alerted.

    • Properties: Based on the Event Type that you enter, select values in the Properties section. For example, for a Batch event type, BatchServer is a property of the data type String. The Properties field is optional.

      Based on the data available in the ArchestrA Event main list, the properties of the Event Type list is populated. You can add other properties of the event type, if required.

  4. Click Attach Event to associate the workflow with ArchestrA Event for that specific event.

    Click Cancel to abort.

    The confirmation message, Successfully associated the workflow appears.

Limitations

  • The Between operator is not supported for Priority and Properties.

  • The data type of the operators are not validated. Ensure to provide valid values to the property data type.

  • Only one workflow with one event provider is supported. That is, different event providers for a workflow with different association is not supported.

  • While creating a filter condition, duplicate properties are not supported.

  • The OR condition is not supported while creating a filter condition.

TitleResults for “How to create a CRG?”Also Available in