Using Subflows and Data Transformation in Integration Workflows
Subflows store shared logic in a single location for reuse in other OneTrust workflows, which allows the integration to perform complex actions such as nested apply to each logic that otherwise cannot be easily configured within a single workflow. This supports the integration with additional actions steps to improve asynchronous execution by performing a logic sequence through multiple steps to improve batch processing. Additionally, subflows also are an alternative to webhooks when there is a need to call another workflow from inside another workflow. They can replace OneTrust webhooks in that scenario without the need for creating an external endpoint.
Data Transformation is a contained logic step that adds the ability to perform calculations, update dynamic values, and manipulate data without executing a specific action within the workflow. This can be helpful for aggregating information inside an apply to each sequence and then sending the combined payload in a single action upon completion of the sequence.
To create a subflow
Before subflows can be selected as an available step in the Integration Builder, they must be created as a built-in trigger in the initial workflow action.
Integration workflows can only have one Apply to Each logic action per workflow. This is designed to avoid excessive processing time, as workflows processing for more than 25 minutes will fail. OneTrust recommends to send a second Apply To Each loop to process in a subflow workflow.
To add Subflows in existing workflows
Subflows can be called as a workflow step to perform additional actions that otherwise aren't available in a standard workflow.
To create Data Transformation logic
Data Transformation logic can be applied as a final step in an conditional logic sequence. This enables the payload to perform the transformation on each applicable step in the sequence using various arrays and dynamic values.