This article will walk you through how to map your desired OneTrust metadata to the corresponding attribute in Ironclad.
One of the key benefits of the OneTrust integration with Ironclad is being able to pull in pertinent vendor information from OneTrust directly into your Ironclad workflow launch form. This article will guide you through how to set up that data mapping.
To learn more about the OneTrust integration, refer to the OneTrust Integration Overview.
Set up Workflow Launch Configuration
Required Permissions: Ironclad Admin & OneTrust Admin
To get started, it’s beneficial to have both an Ironclad admin and a OneTrust admin, as each will best understand the data model in each platform to ensure the right values are mapped correctly.
- In Ironclad, navigate to Company Settings > Integrations > OneTrust > + Add Workflow Configuration and select the desired workflow you wish to integrate with OneTrust.
- Click + Add Launch Configuration, and then + Add Attribute. A dropdown menu displays with the possible attributes included in your workflow.
- Select the attribute you want to map to, and then select a source attribute from OneTrust that you want to pull data from. A decision tree is created. This is where it is beneficial for your OneTrust admin to be proficient in your data model.
Click to view examples to help get you started.
Map Vendor Name
If you wanted to construct a simple mapping, such as the name for a vendor, you can configure it as shown in the screenshot below:
Map Vendor Organization ID or Name
For more complex relationships, such as if you wanted to map the vendor organization ID or name, you would need to follow the relationship chain to get that attribute. As your starting point, you would first map to data, then the organization object associated with that vendor, and then the id or value.
Notice how you navigate different relationship types. In this example, Organization is a single nested object under data, whereas in the above example, name is a direct field under data. These relationships match the documentation in OneTrust’s API.
Notice how you navigate different relationship types. In this example, Organization is a single nested object under data, whereas in the above example, name is a direct field under data. These relationships match the documentation in OneTrust’s API.
Set Up Approval Task Configuration
Required Permissions: Ironclad Admin & OneTrust Admin
The Approval Task configurations enable you to create OneTrust vendors or engagements directly from Ironclad during workflow launch step. This will also approve your Ironclad workflow whenever the Vendor's "Approval Status Field" reaches the "Approval Status Value" in OneTrust.
To set up this configuration, you must coordinate with your OneTrust administrator who will understand the field requirements of the OneTrust API.
Create a New OneTrust Vendor
- Click + Add Approval Task.
- Select an approval from the workflow to initiate a task whenever that approval is present.
- Select the Task: Create OneTrust Vendor.
- Map your values from OneTrust to the desired Approval Status Field and Approval Status Value.
- Map workflow attributes with the request properties to create your OneTrust Vendor object.
NOTE
The Name property is required.
Create a New OneTrust Engagement
The same setup applies regardless if you are launching the new engagement on a new or existing vendor.
- Click + Add Approval Task.
- Select an approval from the workflow to initiate the engagement whenever that approval is present.
- Select the Task: Create OneTrust Engagement.
- Map your values from OneTrust to the desired Approval Status Property and Approval Status Value.
- Map workflow attributes with the request properties to create your OneTrust Vendor object.
NOTE
Both the Name and Vendor → Organization ID properties are required.