Binding Signatures in Supplementary Form
- Last UpdatedNov 06, 2023
- 2 minute read
This topic is related to Supplementary forms.
Signature Field Bindings
This topic provides further explanation on binding signature fields in Supplementary Forms. See Field bindings for supplementary forms.
|
Description |
Field |
Purpose |
|
SF signature |
SUPPFORM_SIGNATURE |
Mapped to name to populate a signature field. |
|
SF signature date |
SUPPFORM_SIGNATUREDATE |
Mapped to name to populate a signature fields and also populates with date/time. |
Bind a Signature in Supplementary Form
You can display applied signatures on forms that are linked to the performing of a process. While processing the entity from one status to another, the signature field will be populated. A signature will be displayed based on From and To status codes of a process and also role code.
Note: The processes and signature roles must already be configured in OSM Administration.
Place binding inside HTML form
Placing bindings of signatures inside a supplementary form is done using custom element attributes. You will still need to use data-cow-bind attribute, but also some additional attributes for the element.

You can map multiple roles from multiple processes using these types of attributes. The application will parse only valid entries in the element attribute values.
|
Description |
Element |
|
Signature binding |
data-cow-bind ="SUPPFORM_SIGNATURE" |
|
From Status code on a process |
data-cow-bind-signfrom |
|
To Status code on a process |
data-cow-bind-signto |
|
Signature role code |
data-cow-bind-signcode |
Signature
A sample format and attributes for mapping signature.
Signature Date
A sample format and attributes for mapping signature date and time.

