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 Logic App Events

  • Last UpdatedNov 24, 2023
  • 2 minute read

Use the Associate option to associate a workflow with a Logic App event.

To associate a workflow with a Logic App 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 Logic App Event to associate the workflow with a Logic App event.

  3. Enter the following details:

    • Enterprise Console: Select an Enterprise Console site. The list shows Enterprise Console sites to which repositories are mapped, and for which Azure Service Bus (with Shared Access Signatures) are configured.

    • URI: The URI is automatically generated based on the selected Enterprise Console.

    • Authorization Token: The authorization token is automatically generated based on the selected Enterprise Console.

    • Logic App Alert Key: The default value is the name of the workflow being associated. You can enter any other value, if required.

    • User: The default value is the username of the logged-on user. You can select any other user, if required.

    • Workflow Version: The default value is the latest version of the workflow. You can select any other version, if required.

    • Logic App JSON Data: Enter the JSON schema to be passed from the Logic App.

    • Logic APP XML Schema: After entering the JSON schema for Logic App JSON Data, click Get XML Schema to auto generate the XML schema.

  4. Click Save to associate the workflow with the Logic App event.

    The association is created, the LogicAppAssociationData XML variable is created for the schema, and an information message appears.

  5. Click Close.

    The information message is closed.

Note: While posting alert from the Logic app, ensure the following are part of the HTTP request:
- URI as generated based on the selected Enterprise Console.
- Authorization Token, as generated based on the selected Enterprise Console, is in the header.
- ApplicationName and LogicAppAlertKey in JSON schema are in the body.

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