Testing Workflow Actions and Saving Sample Payloads

You can test workflow actions and generate a sample response to produce a payload which can be referenced in future workflow actions. Additionally, workflows can be tested with sample responses to ensure they're valid with the added benefit of saving that response.

Important:

Testing a workflow will run an iteration of the workflow, potentially impacting integrated systems regardless of workflow status.

To test and generate a sample response from actions

  1. On the Integrations menu, select Integrations.

    The Integrations screen appears.

  2. Click on an existing integration or click the Add New button to create a new integration.

    The Integration Builder screen appears.

  3. Open the desired action by clicking the Edit icon.
  4. Select the Account Credentials for the action.
  5. In the Request tab, edit the Request URL and Body fields as necessary to remove dynamic references before testing the action.
  6. Click the Response tab.
  7. Select which payload type you want to test and generate.
    Note:

    Attachment payloads are not supported for testing. The Test Action button will be disabled.

  8. The payload values will be fetched from the system using the provided credentials and request URL entered in the Request tab.
    Note:

    You must update any dynamic references with valid values in order to generate a valid response. Afterwards, the request URL and payload must be returned their original state.

  9. Click the Test Action button. If the request is valid, the Generate Response modal appears. If the system credentials or request URL are invalid, the application will produce an error message.
    Attention:

    Clicking the Test Action button will call the external system with the URL and payload provided. Review the URL and payload to ensure you don't mistakenly call an action which might have unintended effects.



  10. Enter or edit the sample response as necessary in the Response Data field.
    Note:

    In order to test this sample response against actual data in your OneTrust application, see Step 7 in To save a sample response using custom event data.



  11. Click the Save button. This sample can now be used when selecting response values in subsequent actions.

To test a workflow with event data

  1. On the Integrations menu, select Connections.

    The Connections screen appears.

  2. Click on an existing connection or click the Add New button to create a new integration.

    The Integration Builder screen appears.

  3. Click the Context Menu icon.
  4. Select Test Workflow.

    The Test Workflow pane appears.

  5. Select which type of event data to test the workflow.


    Field
    Description
    Saved Event Data

    Choose one of the saved events populated in the selection field.

    Create New Event Data

    Provide a unique name and event data in the given fields.

  6. Click the Test button.
  7. The Response tab will return a success or failed status. You can use the Logs tab and Expand button to further investigate this payload.


To save a sample response using custom event data

  1. On the Integrations menu, select Connections.

    The Connections screen appears.

  2. Click on an existing connection or click the Add New button to create a new integration.

    The Integration Builder screen appears.

  3. Click the Context Menu icon.
  4. Select Test Workflow.

    The Test Workflow pane appears.

  5. To use the sample response generated above, select Create New Event Data.
  6. Provide a unique name for the new event.
  7. Enter a sample response in the Event Data field.
    Note:

    This sample should include values or IDs that are native to your modules' use case or instance of the OneTrust application.

    Example: Data Subtask Access System Subtask Created

    For this payload, you would need to update the values to correspond with the data in the Privacy Rights Automation module. so they can be referenced later in the workflow, including but not limited to:

    • requestId

    • requestRefId

    • otherData



  8. Click the Save Event Data button. The application will confirm the save and the new event can be used when choosing a Saved Event Data.