Attachment support for requirements
Valid from Pega Version 7.1.6
Requirements now support attachments. You can add attachments from the Designer Studio > Application > Profile > Requirements landing page, the Add/Edit Requirement modal, or the requirement rule form.
Use the UI Tree to view artifact hierarchy
Valid from Pega Version 7.1.6
The UI Tree tool allows developers and designers to view the hierarchy of Pega artifacts in an application, both when using Designer Studio and at runtime. Activating this tool displays a column on the right-hand side of the screen containing a list of the artifacts on the current page, including harnesses, panels, sections, layouts, flow actions, cells, and properties. Selecting any of these elements allows for read-only interaction with hierarchy information.
See How to use the UI Tree tool.
Quickly add an attachment step to your processes
Valid from Pega Version 7.1.6
The Attachment step allows you to quickly add an Attach Content subprocess to your flow. Once added, choose the attachment type and instructions to present to users:
Dynamic layout improvements
Valid from Pega Version 7.1.6
The following usability improvements have been made to dynamic layouts:
- Refresh conditions can be specified on a dynamic layout. You no longer need to create sections to create refresh boundaries.
- Labels on an included section or nested dynamic layout can be specified with label-positioning specified in the skin.
- Validation errors in a dynamic layout now display below the field.
- Use natural label width for inline dynamic layouts so only necessary space is used.
Signature Capture control
Valid from Pega Version 7.1.6
The Signature Capture control allows you to capture a user's signature when using either a desktop application or a mobile app accessed from the Pega 7 mobile application. Once a user has input a signature, it is added to the work item as an image attachment.
Access the Signature Capture control from the Advanced dropdown in Designer Studio.
See How to use the Signature Capture control.
A single starting flow creates all ad hoc cases
Valid from Pega Version 7.1.6
An operator can uniformly create ad hoc cases in the My Cases area on the Case Manager portal, on user forms, and in Pega Pulse by way of the standard starting flow pySimpleCaseWorkFlow. Operators can define the routing of the case and an overall SLA when creating the case.
The default action created by the ad hoc flow contains a dashboard that also enables operators to quickly define tasks and add attachments.
Previously, the standard flows pyManualTaskStandardAssignment and pyManualTaskStandardApproval were employed. These are deprecated, but are still supported in existing configurations.