Revenue Cloud

Configure Contract Lifecycle Management

This covers setting up how contracts move through Revenue Cloud: creation, approval, internal review, document generation templates and e-signature. The user ends up with contracts that can be drafted from clauses, reviewed, generated as documents and sent for signature.

29 tasks
Method

How MeshMesh does it

  1. Explores the org and confirms that Industries CLM is active.
  2. Checks existing Auth Providers, Named Credentials and External Document Storage configs before connecting outside services such as Office 365.
  3. Writes a phased implementation plan for the user to approve.
  4. Works through approval, check out, internal review and e-signature configuration.
  5. Diagnoses failures, such as an internal reviewer search that returns no users or an e-signature send that fails, and fixes blockers like a clause that would not save because of a large embedded image.
  6. Builds the user-facing pieces: a contracts console app with clause selection from the clause library, and flex template document generation with rich text and context definitions.

Contract changes after signing continue in Configure Contract Amendments.