Running Actions and Actionflows

Run Action

Actionflows and the Action nodes within them usually run as a result of a button click or task plan, however, on occasion you may wish to run an Actionflow or individual  HTTP action independently, such as, when testing or to see the result back from an API. 

Running Actionflows

To run the entire Actionflow, use the  Run Action option found in the Actionflow toolbar.

The  Run Action option can also be found via the  icon in the Actionflow  Properties, or by right-clicking on an Actionflow in the  Repository or on the Actionflow homepage.

Running Actionflows with Input Parameters

  1. Open the Actionflow you want to run
  2. Click the  Run Action option in the toolbar

  3. A prompt will display to enter any input parameters, if applicable 

    1. If any of the input parameters have Default Expressions, these will display greyed out but can be overridden by clicking the tick box and typing into the input box or toggling the true/false field 
      1. To set Default Expressions, click the  input node under Connections and double-click an Input Parameter

    2. Actionflows without input parameters can still be run

    3. Where the Actionflow contains multiple phases, the inputs must be entered for each phase, as displayed by the coloured circles 
  4. Click Run Action
  5. A Log File message will display if the Actionflow was successful
    1. If an output is connected, a Result for Action message will display the results of the Actionflow


Results and Log File Messages

As with all System Console messages, double-click each message to show more detail.

Running HTTP Actions

To run an individual  HTTP action, use the  Run Action option found under the More Options menu on the HTTP action's Properties.

  1. On the Test HTTP Action window, on the Inputs tab, enter values for the mapped attributes, if applicable
  2. On the Headers tab, existing headers can be edited by double-clicking
    1. To add headers, go to the HTTP action  Properties
  3. Press Send to see the Response
  4. The Headers tab contains the response from each header sent in the request
    1. These include headers you have not explicitly specified but are sent automatically with each request
  5. The Body tab shows the Response Body of the HTTP call