Trelica can connect to both US and EU Ironclad instances. The integration uses OAuth, so you will be prompted to consent to the specific permissions required when you connect.
Choosing what agreements to import
Ironclad is very flexible and Trelica lets you define various filters to limit the records that are pulled in to Trelica. For example, you would ideally want to restrict to IT related contracts.
The filters are optional but where specified they are combined. If you select a Record type and multiple Workflow Configurations, then the agreements imported will be of the specified Record type and one of the specified Workflow Configurations.
Record title checks to see if the title contains the specified text (case-insensitive).
Filter field name and Filter field value checks for an exact match for the given field name and value. Both field name and value must be provided for this filter to be applied.
What data will be imported into Trelica?
Ironclad is very configurable. Please contact Trelica support if there are additional field mappings required.
| Trelica | Ironclad |
|---|---|
| Vendor | 'Counterparty name' |
| Agreement date | 'Agreement date' (or 'Standard Agreement date' if not provided) |
| Contract ID | 'Ironclad ID' |
| Start date | 'Contract start date' |
| End date | 'Contract end date' (or 'Expiration date' if not provided) |
| Auto renewal? | 'Contract clause auto renewal' |
| Requested by | 'Workflow owner' (or 'Workflow creator' if not provided) |
| Notes | 'Inbound contract description' concatenated with 'Additional notes' |
| Total value | 'Contract value' (or 'Contract value total' if not provided) |
| Documents | Any associated documents will be imported |
Comments
0 comments
Please sign in to leave a comment.