...
A consent to digitally sign statement is provided above the Sign this section button. It reads "By clicking the button below, you consent to the use of digital signatures."
Signed sections that are authenticated based on the logged in user will display "Digitally Signed (identity verified)" above the signature. Signed sections that are authenticated based on email address will display "Digitally Signed (email verified) above the signature.
When the user signs and clicks Continue/Submit, a unique signature ID is created. You can see this ID under the signature on future steps and on the completed submission.
| Tip | ||
|---|---|---|
| ||
Visit the Electronic Signatures Documentation to learn more. |
...
Templatized String Values for Integration
Templatized String Values
When templatized strings are used in integration, such as Document Actions, they will now always send the control's submission document value and not the control's UI formatted value. In past versions, this behavior was inconsistent between forms and workflows. For example, date control values will be sent as yyyy-mm-dd regardless of the date format set in the designer.
Repeat Control Value Separator for JSON Format
A new repeat control separator for templatized strings has been introduced that formats the control's value as a JSON array. JSON array format is commonly used when generating metadata for the Filesystem Connector and other integrations. To include values from repeating controls and multi-select controls in your metadata, designers can now use the built-in separator 'json' i.e. /{json|controlname}. This special separator resolves to JSON format. The same result can be accomplished by specifying the JSON format i.e. ["{","|controlname}"].
Migration Considerations
- Signed sections have a slightly new look. You will now see a consent message before signing, a digital verification message after signing, and a signature ID after the user signs and clicks Continue/Submit.
- The CSS class f-page-break-inside-avoid is deprecated, but will continue to work on existing forms/workflows. We encourage customer to use a new f-break-children-avoid CSS Class which when applied to a group control it will avoid page break inside child controls. If there is need to avoid a page break inside a specific control then use "f-break-inside-avoid" CSS Class.
- Integration: For all connectors, the template values will now send the document (internal) value, not the control value shown in the UI at run-time. For example, date control values will be sent as yyyy-mm-dd regardless of the date format set in the designer.
...