Welcome > Process Designer module > Activity types > Common activities > CCM Distribute activity > Configure a CCM Distribute activity

Configure a CCM Distribute activity

  1. Add a CCM Distribute activity to the map. See Add an activity.
  2. On the Extended Properties page of the CCM Distribute activity, click the Configuration tab.
  3. Consume a CCM Instance.
    Note Distribution is not supported for a cloud deployment of CCM and an error will appear if an unsuitable instance is consumed.
  4. Consume a String variable for Pack ID.

    You must pass in the ID of a pack previously created in CCM and stored in TotalAgility.

    Note The pack generated for CCM does not contain the signed documents. The signed documents
  5. Consume a variable or enter a static value (alphanumeric) for the Tracking ID.

    This value is reflected in the Customer Communication Management logs on the CCM server if an error occurs. For example, you can enter the value of a JobID or a Case Ref to correlate between your job in TotalAgility and document distribution in CCM.

  6. Select a Distribute Mechanism from the list.
    • Archive: The CCM server sends the documents to archive storage configured within the CCM server.
    • Email (Default): The CCM server distributes the documents through email.
    • Portal: The CCM server posts the documents to a Web portal so that recipients can view online.
      Note An email with a URL to access the documents, is sent to the user who must logon to a secure portal to view the documents.
    • Print: The CCM server sends the documents to a printer so that they can be printed.
    • SignDoc: The CCM server sends the documents for eSigning. Consume the SignDoc Server, Package ID, Signed PDF and the Package State. See Configure a SignDoc activity. At runtime, the activity completes only after the signing ceremony has been completed. The signers are defined in the template and the data in the backbone determines the actual signers.

    Note When composing and distributing documents to SignDoc, the pack that is returned is the pack that is generated in CCM for signing; it does not contain the signed documents. The signed documents are held in a document variable mapped to the signedPDF property.

    CCM uses scripts to perform the distribution. The scripts are custom written and are shared across projects. Therefore scripts have no access to the data in the data backbone. The only way to pass data into the script is through metadata (a set of key/value pairs).

  7. Configure the metadata:
    1. Enter a Key name. (free text)
    2. In the Value box, consume a variable or enter an inline value.
    3. Click . The key-value pair appears in the table.
  8. Click Close.
    Note If you configure the CCM Distribute activity on the Integration Server, the activity executes using the CCM server that is configured on the Integration Server.