Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Use Case: Workflow for Automating Contracts

You can enable a workflow for setting up workflows for generating and activating NDAs or MSAs with limited dependency on the legal team, significantly streamlining the process for organizations. This allows users to quickly create, review, execute, and manage NDAs or MSAs. These workflows are beneficial for teams that frequently need to establish NDAs or MSAs but do not require complex legal reviews for each instance.

Workflow for Automating NDA Contracts

The use case explains how you can set up DefaultNDASelfServiceContractWorkflow workflow for generating an NDA contract, sending the document for signature, and activating the document.

The DefaultNDASelfServiceContractWorkflow is an out-of-the-box workflow that is unpublished by default. To publish the workflow, navigate to the Admin Console > Workflows > Staged Workflow and publish the workflow. This workflow is configured with appropriate triggers and entry criteria. This configuration determines when the workflow is initiated, and which contracts it applies to. By enabling and managing the DefaultNDASelfServiceContractWorkflow, you can provide a controlled yet flexible environment for handling NDAs. This workflow ensures a smooth and efficient process for users to generate, sign, and activate NDAs.

This workflow comprises the following three distinct stages that are connected to form a complete process. These stages reflect the lifecycle of an NDA based on the status category and status. To publish the stages, go to the Admin Console > Workflows > Stage and publish them.
  1. GenerateNDAOOBStage1: This stage involves creating the NDA document with the necessary details and generating a document using a predefined template. The document is then made available for review.
    Important: Ensure that the primary contact is updated when creating a contract. If it is not added, the workflow fails during the document generation stage.
  2. InSignatureOOBStage2: The workflow condition for this stage is set as Status Category = In Effect, Status = Activated. In this stage, the NDA is sent to the relevant parties for electronic signatures. The system tracks the signature status and ensures that all required signatures are obtained.
  3. InEffectOOBStage3: In this stage, once the NDA is signed, it moves to this final stage where the agreement is activated and stored securely. The NDA is now legally binding and can be managed as needed.

Workflow for Automating MSA Contracts

The use case explains how you can set up a DefaultMSASelfServiceContractWorkflow workflow to generate and negotiate an MSA contract, send it for signature, and activate the document.

The DefaultMSASelfServiceContractWorkflow is an out-of-the-box workflow that is unpublished by default. To publish the workflow, navigate to the Admin Console > Workflows > Staged Workflow and publish the workflow. This workflow is configured with appropriate triggers and entry criteria. By enabling and managing the DefaultMSASelfServiceContractWorkflow, you can provide a controlled yet flexible environment for handling MSAs. This workflow ensures a smooth and efficient process for users to generate, negotiate, sign, and activate MSAs.
This workflow comprises the following four distinct stages that are connected to form a complete process. These stages reflect the lifecycle of an MSA based on the status category and status. To publish the stages, go to theAdmin Console > Workflow > Stage and publish them.
  1. GenerateMSAOOBStage1: This stage involves creating the MSA document with the necessary details and generating a document using a predefined template. The document is then made available for review.
    Important: Ensure that the primary contact is updated when creating a contract. If it is not added, the workflow fails during the document generation stage.
  2. NegotiateMSAOOBStage2: The workflow condition for this stage is set as Status Category = In Signatures, Status = Ready for Signatures. In this stage, MSA contract is sent to all the contract stakeholders to negotiate the contract's terms and conditions.
  3. InSignaturesMSAOOBStage3: The workflow condition for this stage is set as Status Category = In Effect, Status = Activated. In this stage, the document is sent to the relevant parties for electronic signatures. The system tracks the signature status and ensures that all required signatures are obtained.
  4. InEffectMSAOOBStage4: In this stage, once the MSA document is signed, it moves to this final stage when the agreement is activated. The MSA is now legally binding and can be managed as needed.