Before
Sales operations had to find accepted quotes, retrieve the related opportunity and account details, and re-enter those values into the appropriate contract workflow. They also had to check for an existing CLM contract, reconcile returned identifiers, and notify support when data or workflow startup failed.
How it works
- Retrieve the opportunity, account, and quote, then validate acceptance status, required fields, dates, currency, and contract-template coverage.
- Check for an existing CLM workflow; skip and log duplicate requests, or start the mapped contract workflow when the deal is eligible.
- Write the resulting CLM identifiers back to Salesforce, or log, flag, and notify support about data or CLM errors.
Workflow details
- Trigger and retrieval: A secure webhook receives the opportunity and optional quote references, then retrieves the related opportunity, account, and quote data from Salesforce in one read.
- Validation and mapping: The flow maps deal and quote details into contract parameters, checks that the quote is accepted, verifies mandatory fields, validates the currency and date range, and confirms that a contract template is mapped to the contract type.
- Duplicate protection: Before starting a new workflow, it checks whether the opportunity already contains a CLM workflow reference. Existing contracts are not started again and are returned as duplicate triggers.
- Contract launch: For an eligible opportunity, the flow starts the mapped contract workflow using the selected template and deal details, then writes the CLM identifiers back to the Salesforce opportunity and logs the successful start.
- Exception handling: Invalid or incomplete data is logged, the opportunity is flagged, and support is notified. If CLM rejects the start, the opportunity is marked with a CLM error, the failure is logged, and support receives an error notification. The definition includes simulated connector responses for website demonstration.
What changed
An accepted quote now moves through standardized validation, duplicate protection, template routing, contract initiation, and Salesforce updates in one flow, while only exception handling remains for support when data is invalid or CLM rejects the start.
Work removed
Repeatedly looking up deal details, checking quote eligibility and duplicate contract status, retyping contract parameters, reconciling CLM identifiers, and manually routing data or CLM errors to support.
Expected outcome
For each eligible quote, the workflow can replace roughly four recurring manual actions—deal lookup, duplicate checking, data transcription, and CLM-ID reconciliation—with a traceable contract-start result.
