Signature How To's

How to's for the Signature guide.

How to Use Signature?

How to Use Signature?

The following steps describe how to add and use the Signature component on a form.

Add the Signature Component to the Form

1. Open the form design screen.
2. Go to the Toolbox panel.
3. Locate the Signature component.
4. Drag and drop it onto the form.

Configure General Properties

When the Signature component is selected, the following tabs are displayed in the Property Viewer panel:

• General
• Label
• Behavior
• Appearance
• Events

General Tab

From this tab, you can configure:

• Visibility settings
• Required field status
• Size and layout settings

User Signature Process

• The user clicks on the Signature area to start signing.
• The signature can be drawn freely using a mouse, touch screen, or stylus.
• When the form is saved, the signature data is saved together with the form data.

Clearing the Signature (Reset)

• The user can clear the signature and sign again if needed.
• The reset action can be triggered via the related button or action.

Using Events

The Signature component can be used together with events, such as:

• Validating the signature before form save
• Preventing form submission if no signature is provided
• Triggering additional business rules after the signature is completed

Usage Scenarios

• Approval forms
• Delivery / acceptance documents
• Contract approval screens
• Authorization workflows

Notes

• The Signature component is typically used as a required field.
• It is ideal for touch-based usage on mobile devices.
• Organizational and legal requirements should be considered before using it in legally binding processes.

---

How to Perform Digital / Mobile Signing in a Process?

How to Perform Digital / Mobile Signing in a Process?

To use digital or mobile signatures in a process, the content to be signed must be in PDF format and stored in the Document Management System (DM).
To meet this requirement, there are two main approaches.

Signing by Adding an Existing Document from DM to the Process

This method is used to sign a file that already exists in the Document Management (DM) system within a process.

Steps

1. Open the process design screen.
2. Add a Related Documents or similar document attachment step to the process.
3. Include the document from DM that needs to be signed in the process.
4. Define the Digital Signature / Mobile Signature action in the relevant step.
5. When the process runs, the user can sign the document using:
   • Digital signature
   • Mobile signature

When Should It Be Preferred?

• If the document to be signed is already prepared
• If there is an existing PDF file in DM
• If template generation is not required

Converting the Form to PDF Using a DM Template and Signing It

This method allows form data used in the process to be converted into a PDF document and then signed.

Steps

1. Create a PDF Template in the Document Management (DM) system.
2. Map the template fields to the form fields.
3. At the relevant step in the process:
   • Convert the form data to PDF using this template.
4. The generated PDF is automatically saved to DM.
5. In the same step or a subsequent step, initiate the digital/mobile signing process.

When Should It Be Preferred?

• If form data needs to be signed
• If dynamically generated documents are required
• If standardized and corporate outputs are desired

Summary Comparison

Method	Description	Purpose
Add DM Document	An existing PDF document is added to the process	Signing ready-made documents
DM Template → PDF	Form data is converted to PDF	Dynamic and standardized document generation

Important Notes

• Digital / mobile signing works only on PDF documents.
• The document to be signed must be stored in the Document Management system.
• The signing step is typically used for:
  • Approval steps
  • Managerial controls
  • Official processes

Tip

If both form data and attachments need to be signed in a process:

• First generate a PDF from the form
• Then add additional documents to the process
• Finally, use a single signing step to sign all documents

---

What Is Signature?

What Is Signature?

The Signature control is a form component that enables end users to create a digital signature directly on a form.
Users can draw their signature using a mouse, a touchscreen, or a stylus, and the signature is stored as part of the form data.

This control is commonly used in scenarios that require signatures, such as:

• Approval processes
• Contract forms
• Delivery and acceptance reports
• Authorization and consent forms

The Signature control provides a digital equivalent of a handwritten signature, allowing processes to be completed entirely in an electronic environment.

Key Features

• Freehand signature drawing
• Mouse and touch support
• Signature stored as form data
• Clear (reset) functionality
• Can be used together with validation rules

Use Cases

• Collecting official user approvals
• Digitizing documents and business processes
• Eliminating the need for physical signatures
• Accelerating legal and operational workflows

Notes

• The Signature control is typically marked as a required field.
• It is widely used in workflow and approval processes.
• Signature data is stored together with the form record.

---

How to Use Client Enabled?

What is Client Enabled?

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?

The property allows developers to:

• Control when a form control becomes interactive.
• Prevent users from entering or changing data until prerequisites are met.
• Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:

1. Select the “Signature” field in the form editor.

2. In the Properties panel, find the Client Enabled field.

3. Set the value to False — the field will now be disabled by default when the form loads.

4. Open the Rule Manager.

5. Add a new rule:

   Condition:

Action:

6. Save and publish the form.

Result:

• When the form loads, the “Signature” field is disabled.
• Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary

Property State	Description
True	The control is active and ready for user interaction when the form loads.
False	The control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices

• Use the Client Enabled property to manage client-side interactivity without requiring server actions.
• Combine it with Rule Manager to define when and how controls become active.
• Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
• By default, this property is set to True (active).

Summary

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.