Skip to main content
Documentation
Documentation
Last Updated: 2025-10-03
Reference: Flow To Create Ticket Custom Actions

Reference: Flow To Create Ticket Custom Actions

Context

You can automate the creation and submission of intake forms for mapped Contract Management and Document Intelligence workflows using the
Flow to Create Ticket
 custom flow action, included in the Salesforce Connector for CLM and CI Package. This enables you to configure automatic intake form submissions based on field values from a Salesforce record and its related records.

How to Use

When using this flow action, you need to provide these inputs:
recordId
The dynamic Salesforce record ID of the opportunity, or other Salesforce record, containing the fields mapped to the intake form. Example: Opportunity ID.
workflowId
The 36-character Workflow ID from Contract Lifecycle Management. You can find this in the workflow URL in Contract Management and Document Intelligence. Example: https://clients.evisort.com/…/workflow/builder/
20d6304b-e19b-4469-a949-33be90d4527a

Guidelines and limitations:

When using the
Flow to Create Ticket
 flow, consider:
  • When a new version of the workflow in Contract Management and Document Intelligence is published the ID will change. You must update the workflowId in all flows referencing that workflow.
  • All field values for the intake form must exist on the triggering Salesforce record, or related records.
  • You can’t use child relationships in the workflow mapping because they require user interaction to select a child record. Mapped child fields remain blank in the intake form.
  • When a required field in the Contract Management and Document Intelligence workflow doesn’t have a corresponding value in the Salesforce record, Salesforce still submits the intake form but the field will be empty in Contract Management and Document Intelligence.
  • When no workflow mapping exists in Evisort Admin for the specified object and workflows, Salesforce submits the intake form with blank or default values.
  • When mapped fields are not populated on the Salesforce record and default values for those fields are specified in Contract Management and Document Intelligence, the fields are populated with the default values.