Executing a workflow

The Execute workflow action enables you to specify the name of the workflow, input parameters, if required, for remediating an event. You specify this action while creating a policy. 

While creating an action, you can use an event stored in the BMC Helix Intelligent Automation database or provide an event in a JSON format. 


The process described in this topic is for one of the TrueSight Orchestration actions supported by BMC Helix Intelligent Automation. Use the steps in this topic to add any TrueSight Orchestration actions while creating a policy.

To add the Execute workflow action to a policy

  1. In the BMC Helix Intelligent Automation console, click Policies and the click Create Automation Policy.
  2. In the Policy Information section, enter a unique name and an optional description for the policy. 
  3. Select Manual or Automatic depending upon whether you want to execute the policy manually or automatically based on the incoming events.
  4. In the Trigger section, click Browse and perform one of the following steps to select an event:
    1. From the Select Event Type tab, select an existing event type, and click Done.
    2. On the Paste Event JSON tab, enter event in the JSON format, and click Done.

      Sample service down event
          "id": "<Id>",
          "name": "Operations Management:  Remediate Windows Service Down",
          "type": "system",
          "description": "This policy triggers the plugin to remediate a Windows service down event",
          "trigger_condition_expression": "$ ? ($.event.event_type == \"tso_service_down\")",
          "checksum": "3c0692cd9c9c2592a086de0deb715e62a0e0d7bc1cd02b7b68a4e80129820ac2",
          "is_active": true,
          "actions": {
              "process_event": {
                  "plugin_type": "remote_plugin",
                  "credential": {
                      "type": "tso_key",
                      "account_id": "TSO123456"
                  "remote_plugin": {
                      "name": "AutomationDonotDelete"
                  "continue_on_failure": false,
                  "action": {
                      "server": "https://hostname.com:38080",
                      "/baocdp/rest/process/%3ABMC-SA-Event_Orchestration%3AProcess Event/Execute": {
                          "post": {
                              "parameters": [
                                      "in": "headers",
                                      "Authorization": "auth"
                              "requestBody": {
                                  "content": {
                                      "application/json": {
                                          "inputParameters": [
                                                  "name": "event data",
                                                  "value": "$.event"
                                                  "name": "action id",
                                                  "value": "BMC_Helix_Monitor-ServiceDown-1"
  5. In the Trigger Condition text box, use the expression builder to build the following conditional expression to match the trigger condition to the event:

    ( event.CLASS == PPM_SM_EV ) && ( event.severity == CRITICAL ) && ( event.Status == OPEN )
  6. To add system or custom tags to the policy, perform the following steps:
    1. System tags: Select one or more tags from the list of available system tags. 
      Based on the event, some system tags are displayed.
    2. Custom tags: In the Tags (Optional) section, enter a key-value pair. 
      Tag key should start with an alphabet and end with an alphanumeric character. Key supports alphanumeric characters and periods, dashes, and underscores. 
  7. To add action to the policy, click Add Action and perform the following steps by using the action wizard:
    1. From the Pick an automation tool section, click the connector name.
      Only configured connectors are displayed here. The wizard takes you to the next step to select an action. 
    2. Click Sync Actions
      All workflows in the modules enabled on the TrueSight Orchestration Grid Manager appear. 
    3. Click Select against the :BMC-SA-Event_Orchestration:Process Event action. 
      The wizard takes you to the next step to configure an action.
    4. Enter a name for the action. 


      You must enter the workflow name in the Module_Name:Process_Name format.

      For example, AutoPilot-OA-ITSM_Automation:ProcessEventWorkflow.

    5. In the Input Parameters section, provide the values for all the input parameters displayed for the workflow. 
      When you select an action, the workflow description appears and the tooltips describe the input parameters required for this action.


      Based on the selected event, the event slots with the values specified in the event appear under the Parameters section on the UI. You can click any of the parameters and its value gets copied. You can paste it while defining the action in the policy. 

    6. Click Done.
      The added action appears in the Action Configuration section on the Create Automation Policies page.
  8. In the Estimated Savings section, enter an approximate time (in minutes) and money (in USD) that you may save by automating this action.
  9. Select Publish Policy and click Save to publish the policy.

Was this page helpful? Yes No Submitting... Thank you