Encoded Id is Blank or eSign Link is Missing the Id

Issue: When a user creates an eSign document, the Encoded Id field is null or the eSign Link field is missing the Encoded Id (for example, the value is “https://accept.today/v2/” instead of “https://accept.today/v2/0994ce0f-8f8e-4e86-98e1-67fccc8999zz“).

Cause: The user creating the esign documents does not have sufficient field-level security access to the eSign Doc object fields. Users creating eSign Documents need edit access to all fields on the eSign Doc object.