Configure the eSignature Process

The following additional process and system configurations may be required to support the electronic signature feature in Trimble Unity Construct.

Since the actions that can be taken on each step are role based, a valid role must exist for the signee or potential signees of the eSignature step.

Creating a role with specific users is a two-step process. You must first create the role, and then add users to the role.

As you select a role for the signing step, ensure that it includes only those persons that are allowed to sign the document. Otherwise, all actors in the selected role will have the ability to sign.

  1. Click Setup to access Administration Tools.
  2. Click Users > Manage Roles.

    3. The Manage Roles page is displayed.

  3. Click Add Role.
  4. Enter a name for this role in the Name field.

    5. Example: A naming convention might be <Process Name>, <Step Name>.

  5. Optional: Enter a description in the Description field.
  6. Select Yes if this is an administration role.
  7. Click Save.
  1. Click the name of the account role.
  2. Click Add User To Role.
  3. Filter for users and then select the check box next to the user's name.
  4. Click Add User.

File data fields make it possible for actors to upload documents. The same or different file data fields can be used to point to the destination folder of your choice.

If you already have file data fields created that can be incorporated into your eSignature process, then this task is not required. Complete this task only if you do not already have the appropriate file data fields available.

Create a file data field for the upload of the final document as well. This way, you can store the final signed document in the appropriate location, perhaps in a limited-access folder.

  1. Go to the Data Tab for the process.
  2. Click Add Field.

    3. The Add Data Field page is displayed.

  3. Select the File radio button, and then click Next.
  4. Complete all necessary fields.
  5. Select the destination folder of the file in the Destination Folder Path field. If you do not choose a folder, users will have to choose one at the time of upload.
  6. Click Next.
    A preview of the field just created is displayed on the field summary page.
  7. Click Save or Save & Add to create another data field.

Create a string data field that will be used in the script added to the automation step of your eSignature process.

It is recommended that you do not use an existing field or reuse it for other purposes within a single process.

  1. Go to the Data tab of the process.
  2. Click Add Field.
  3. Select the String radio button, and then click Next.
  4. Complete all necessary fields.

    5. The field can be given any name, but “DownloadSuccess” is recommended so that our Support team can easily locate it when finalizing this process for you, or if troubleshooting becomes necessary.

  5. Click Next. The field summary page displays a preview of the field just created.

  6. Click Save or Save & Add to create another data field.

eSignature data field settings allow administrators to specify the destination file data field, and a naming convention for the final version of the signed document.

  1. Go to the Data tab for the process.
    2. Data Tab - Data Field eSignature Settings
  2. For each file data field that will contain a document to be signed, click the adjacent Destination File Data Field drop-down menu to select the file data field that will be used as the destination folder for the signed document. When more than one Destination File Data field is mapped, only one of those files is required to prepare the document for eSignature. Users will no longer have to upload “placeholder” files in DocuSign process instances when more than one file field is mapped by Admin.

    3. This drop-down menu includes all existing file data fields. Files will go to the destination folder associated with the selected data field. To add or change the destination folder, edit the data field. If a folder is not specified, the user will be asked to make a selection when the file is uploaded.

  3. In the Naming Convention field, enter a name to be appended to the end of the final document after all documents in the document set have been signed.

    4. If you use the suffix_signed and the name of the document is Trimble Unity Construct User Guide, the final version that includes all signatures will be called, Trimble Unity Construct User Guide_signed.

  4. Click Save eSignature Settings.

Create a read-only layout to prevent modification of the documents that need signatures.

As a business rule, you may not want to give signatories the ability to modify the files they need to sign; however, in a revision step, you might. Create the read-only layout based on the business rules that govern the process.

  1. Go to the Page Layouts tab of the process.
  2. Click Add Layout.
  3. Enter the name of the layout in the Layout Name field.
  4. Click Save.
  5. Select the data field on the right side of the page and drag into the Data section.
  6. Select the field so that it is highlighted.
  7. Right-click the highlighted field and select Edit Field Properties.
  8. Select the Read-Only check box, and then click Save.

    9. The dialog box closes and you are now on the Layout Properties page.

  9. Click Save.

The eSignature feature is enabled on the action of a process step. There are two parts to this particular step of the configuration. You must create a signing action and a non-signing action in order to give the signee an alternate action in case they choose not to sign the document during a particular process instance.

Optionally, you can also allow user(s) in document preparation roles to open a Sending session to tag documents for eSignature by internal and external recipients. Document preparers can precisely tag locations on documents for eSignature by each recipient, eliminating any missed signatures or initials. Project stakeholders who only interact with the construction program on rare occasions can be tagged as external recipients so that no Trimble Unity Construct license or user training is necessary in order to perform eSignatures.

In some cases, the process initiator is the actor that uploads documents to the eSignature Source fields and then takes action to prepare documents for eSignature. To make the workflow more efficient, documents can be prepared for eSignature from the Submit action on the Start step of the workflow. This will eliminate the requirement for Administrators to configure a subsequent Data Entry step that supports the Prepare Document for eSignature option.

On the Submit action for the Start step of the workflow, only the Prepare Document(s) for eSignature check box will be available for selection. The Require eSignature(s) check box option will not be available for the Submit action from the Start step.

To add a signing action

  1. Go to the Workflows tab of the process.
  2. Click the title of the workflow you want to access.
  3. Click Design Workflow.
  4. Go to the Workflow Designer.
  5. To create a new step, drag and drop the Data Entry step to the Workflow Designer.

    6. The Edit Step page is displayed.

    —Or—

    To modify an existing step, right-click the step, and then click Properties. The Edit Step page is displayed.

  6. Complete all necessary fields.
  7. To make the file read-only, select a read-only layout from the Actor Layout drop-down menu.
  8. Click Add Action.

    9. The Add Action page is displayed.

  9. Complete all necessary fields.
  10. Select the Require Signature(s)? check box.

    Only one signature option, either the Prepare Document(s) for eSignature check box or the Require eSignature(s) check box can be enabled on a step action at a time. Once either check box has been selected, the other one will be greyed out and cannot be enabled.

  11. Select the signee's user role(s).

    12. All users within the selected role will have the ability to sign the document. To limit these users to the required signatories only, create a user role that includes only the qualified signees.

  12. Click Save.

A non-signing action is required in order to give the actor an alternate action. A probable secondary action might be Decline or Revise and Resubmit, which could potentially kick start the process all over again.

If the same file or a new file is uploaded, the current envelope ID becomes void and a new envelope will have to be created. In this case, all previous signees will have to sign each file again. A single envelope can contain a number of documents.

To add a non-signing action

  1. Go to the Workflows tab of the process.
  2. Click the title of the workflow you want to access.
  3. Go to the Workflow Designer.
  4. To create a new step, drag and drop the Data Entry step to the Workflow Designer.

    5. The Edit Step page is displayed.

    —Or—

    To modify an existing step right-click the step, and then click Properties. The Edit Step page is displayed.

  5. Complete all necessary fields.
  6. To make the file read-only, select a read-only layout from the Actor Layout drop-down menu.
  7. Click Add Action.

    8. The Add Action page is displayed.

  8. Complete all necessary fields, EXCEPT the Require Signature(s)? check box. Leave this check box clear.
  9. Select the signee's user role(s).

    10. All users within the selected role will have the ability to sign the document. To limit these users to the required signatories only, create a user role that includes qualified signees only.

  10. Click Save.

To add a document preparation action

  1. Go to the Workflows tab of the process.
  2. Click the title of the workflow you want to access.
  3. Click Design Workflow.
  4. Go to the Workflow Designer.
  5. To create a new step, drag and drop the Data Entry step to the Workflow Designer.

    6. The Edit Step page is displayed.

    —Or—

    To modify an existing step, right-click the step, and then click Properties. The Edit Step page is displayed.

  6. Complete all necessary fields.
  7. To make the file read-only, select a read-only layout from the Actor Layout drop-down menu.
  8. Click Add Action.

    9. The Add Action page is displayed.

  9. Complete all necessary fields.
  10. Select the Prepare document(s) for Signature(s)? check box.

    Select this option to allow a document preparer to set up the document for eSignature before sending it to the recipients. The Require eSignature(s) check box will still be available on the Edit Action page. However, only the Prepare Document(s) for eSignature check box or the Require eSignature(s) check box can be enabled on a step action at a time. Once either check box has been selected, the other one will be greyed out and cannot be enabled.

  11. Select the signee's user role(s).

    12. All users within the selected role will have the ability to sign the document. To limit these users to the required signatories only, create a user role that includes only the qualified signees.

  12. Click Save.

An automation step must be placed at a point in the process after all documents have been signed. This step compiles the final document which includes all eSignatures and an encrypted certificate that solidifies it as a unique and final version of the document.

The end of your eSignature process should look similar to the highlighted portion of the diagram below:

e-SignWorkflow

  1. Go to the Workflow Designer.
  2. Drag and drop the automation step to the Workflow Designer.

    3. The Edit Automation Step page is displayed.

  3. Complete all necessary fields and specifically:
    • Click the e-Signature File Download radio button.
  4. Click Save.

Adding a conditional step that branches off of the automation step will help offset any unexpected errors. This optional step safeguards the process by ensuring that the final document is created by creating a loop that gives the process an alternate action if there are any unexpected errors.

The conditional step will be similar to the highlighted portion of the diagram below:

e-SignWorkflow

  1. Go to the Workflow Designer.
  2. Drag and drop the conditional step to the Workflow Designer.
  3. Complete all necessary fields.
  4. Click Save.

eSignature Workflow Troubleshooting Actions - for Adobe Acrobat Sign

While designing workflows with the eSignature process, it is important that you check that your workflow is valid and free from errors.

  1. Go to the Workflow Designer.
  2. Click the Error Check button.
    Any validation errors found in your workflow will be displayed.
  3. Perform the following steps to resolve validation errors in your workflow:

    Error Message

    Troubleshooting Actions

    {Step Name} can be reached without required actions: 'Prepare document for eSignature(s)' or 'Require eSignature(s)'

    • When using the Prepare document(s) for eSignature option, ensure that there is a workflow step configured for this. To do this, edit the workflow step action for the actor responsible for tagging documents to ensure that the Prepare document(s) for eSignature check box is selected (mandatory).

    'Prepare document for eSignature(s)' action on {step name} requires eSignature 'Destination file data field' configuration and Automated File Download Step

    • If the Prepare document for eSignature(s) check box has been selected for the Submit action on the data entry step, an automated file download step must be added to the workflow.

     

    eSignature 'Destination file data field' requires configuration

    For each file data field that will contain a document to be signed, ensure that you configure the Destination File Data Field settings correctly on the Data Field eSignature Settings section of the Data tab (Setup> Administration Tools> Processes> Manage Processes>Click on a process name to view it).

eSignature Workflow Troubleshooting Actions - for DocuSign

While designing workflows with the eSignature process, it is important that you check that your workflow is valid and free from errors.

  1. Go to the Workflow Designer.
  2. Click the Error Check button.
    Any validation errors found in your workflow will be displayed.
  3. Perform the following steps to resolve validation errors in your workflow:

    Error Message

    Troubleshooting Actions

    {Step Name} can be reached without required actions: 'Prepare document for eSignature(s)' or 'Require eSignature(s)'

    • Ensure that all the users who need to sign and approve the document are required to perform eSignatures. To do this, edit the workflow step action for each signing user and ensure that the Require eSignature(s) check box is selected (mandatory).

      AND

      If using the new Prepare document(s) for eSignature option, ensure that there is a workflow step configured for this. To do this, edit the workflow step action for the actor responsible for tagging documents to ensure that the Prepare document(s) for eSignature check box is selected (mandatory).

    • On any possible path leading up to the document download step, at least one step actor must be required to e-Sign for the workflow to be valid.

    'Prepare document for eSignature(s)' action on {step name} requires eSignature 'Destination file data field' configuration and Automated File Download Step

    • For each file data field that will contain a document to be signed, ensure that you configure the Destination File Data Field settings correctly on the Data Field eSignature Settings section of the Data tab (Setup> Administration Tools> Processes> Manage Processes>Click on a process name to view it).

    • If the Prepare document for eSignature(s) check box has been selected for the Submit action on the data entry step, an automated file download step must be added to the workflow.

    • A validation error will be displayed if either of the above requirements are not met.

    eSignature 'Destination file data field' requires configuration

    For each file data field that will contain a document to be signed, ensure that you configure the Destination File Data Field settings correctly on the Data Field eSignature Settings section of the Data tab (Setup> Administration Tools> Processes> Manage Processes>Click on a process name to view it).

    'Prepare document for eSignature(s)' or 'Require eSignature(s)' workflow requires these account preference to be defined: DocuSignBrandID, DocuSign TraceOn, DocuSignPassword, DocuSignUsername
    • An eSignature enabled workflow cannot be published without a DocuSign account.
    • If the 'Prepare document for eSignature(s)' or the 'Require eSignature(s)' action has been added to the workflow, you need to setup your DocuSign credentials in Trimble Unity Construct as well. Contact Trimble Support to configure your DocuSign account settings to work with your account in Trimble Unity Construct.