Adding a Signature capture control
You can add the Signature capture control to a cell, enabling users to capture a user signature, either through a mouse input or through a touch interaction on a mobile device. This control works when used in the context of a work object. Interacting with this control in an application occurs by displaying a field inline where a signature can be scribbled. It can take up a large portion of the screen.
You can define the minimum height and maximum width for the control. Aspect ratio is used to determine the height for the signature capture and is based on current width. The control is responsive and will automatically use 100 percent of the width when rendered on a mobile device. This control also contains the Accept and Clear actions. You can hide the default Accept and Clear actions for the control and use your own custom buttons instead - see Customizing a Signature capture control for details.
When a user clicks Accept the entered signature is saved as an image attachment in the work object. Entering a signature and accepting it can be repeated as many times as necessary, however, only the last signature saved as an attachment is used when submitting an assignment. When a user clicks Clear, the current signature is wiped out so that a new one can be entered in the field. Multiple versions of a signature are not kept. In other words, only the last entered signature is saved as an attachment, no matter how many times you repeat this action on the same control.
You can make the Signature capture control:
- automatically, if it appears in a read-only section,
- based on a defined expression,
- based on a defined when rule,
- force it to be always editable, even if it appears in a read-only section.
Refer to Customizing a Signature capture control for details on the available presentation options.
A user can also sign a work item using the Signature capture control while working offline if this capability has been enabled for the application. This includes adding a signature for work objects that were also created offline. Furthermore, previews of signatures entered while online are available when you are back offline. You can view the attachment of an offline signature in desktop after the next synchronization has taken place. See also Offline capability.
The thickness of the signature varies depending on the speed at which it is entered by the user in the application. An entered signature is automatically cleared when the control is resized - for instance, when changing the orientation of a device. This is a known limitation.
To show a captured signature once the object is resolved, for instance, in the Review harness, follow the steps listed in Packaging a signature after the work object is resolved.
On the Design tab, from the Data capture list, drag Signature capture onto the work area.
If you are using a cell-based layout and you drag the control into a cell that is not empty, then the dropped control replaces the current contents of the cell.
Click the View properties icon to display the Cell Properties dialog.
On the Cell Properties dialog, customize the Signature capture control using the tabs described in the table in Customizing a Signature capture control.
- Customizing a Signature capture control
The Cell Properties dialog for the Signature capture control consists of the following tabs. You can create or modify CSS base styles for the control and create custom Accept / Clear buttons, as described in the subsequent sections, below. See also Adding a Signature Capture control.
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.
Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.
Sections are the building blocks of your user interface. You can populate a section with components, such as fields and controls, to create a functional chunk of user interface that can be reused in different contexts for improved consistency and efficient development.