Frequently Asked Questions

E-Signature Related Issues

• Issue 1: E-Signature initiation fails with the error message “missing taskId by function” (Refer to: picture coming soon:)

  Cause: This error occurs due to a function issue. Check the call logs of the error data under the esign__c function and modify the problem accordingly (Refer to: picture coming soon:).

• Issue 2: The signer-related fields are not displayed when initiating an E-Signature?
  Cause: Reassign the Role layout for the signer object in the backend (The Role layout might not have been initialized with values, causing the fields to be invisible on the frontend).

• Issue 3: After selecting internal and external signers and submitting the E-Signature request, the system still prompts “Please add internal or external signers”?
  Cause: Verify whether the “E-Signature Signer” layout is correctly assigned. Internal signers should use the internal signer layout, and external signers should use the external signer layout.

• Issue 4: Different users see inconsistent E-Signature statuses for the same record?
  Cause: The record displays the latest E-Signature data initiated under the currently logged-in user. If inconsistencies occur, check whether the E-Signature data permissions for administrators and other users are consistent (Locate all E-Signature data for the corresponding initiated record under the E-Signature object and verify consistency).

• Issue 5: E-Signature initiation fails with the error “The selected external signer has no mobile information, so the E-Signature cannot be initiated.”?
  Cause:

  • Confirm whether the external signer has a mobile number configured. If not, set the mobile number before initiating.
  • If a mobile number is configured, ensure the field type for the mobile number is set to “Mobile.”