Hidden Variables: use on documents for internal integration usage, yet be hidden from signers.
Be able to have "hidden variables" to be able to use on documents for internal integration usage, yet be hidden from signers.
Jaynna Ellis Dela Llana commented
Ability to hide fields to other recipients in the document
Ryan Wood commented
It works to add custom fields/variables to the Meta-data (using make.com) that are passed in the background. However, as James Barry said, a better solution is to return all variables in the token array. Otherwise, one has to literally hide (using white text for example) the variables in the template, which is a pretty hacky workaround, and not suitable for data that you don't want exposed.
Joel Hill commented
Having some way of passing fields or variables to downstream apps that the signers cannot see would be a massive business automation improvement!
James Barry commented
If the get template details api could return all custom variables, they wouldn't have to be hidden. I suggest we simlpy return all custom variables in the Tokens array object, including any default values, even if they are not used in the template, and let the client program decided ehow to use them (or not).
Ryan Juszyk commented
Include a token in a template so that the data is included with the document file, but the token is not visible on the document