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.
Address Map control
Valid from Pega Version 7.1.6
The Address Map control creates an instance of Google Maps in an application at runtime that can be used in both desktop applications and mobile apps that use the Pega 7 mobile application.
This control allows users to interact with multiple points on a map and see location details, and can display directions and distance between a current position and a specified address.
Access the Address Map control from the Advanced dropdown in Designer Studio.
See How to use the Address Map control.
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.
Custom shortcuts for mobile apps
Valid from Pega Version 7.1.6
When using a mobile web browser to access your mobile app, you can create a shortcut to a specific URL by selecting "add to home screen" from your web browser's menu when on the page. The shortcut icon displays showing the Pega 7 mobile app icon by default, but the icon can be customized in Designer Studio. When you tap the icon, the mobile device's default web browser opens directly to the saved URL.
See Using the Pega 7 mobile app.
Maintainable warning, error, and tip information
Valid from Pega Version 7.1.7
Use the redesigned Message form to define warning, error, tip, or custom category information in your application. Encapsulating these details in a message makes them easier to maintain and review. After you have created a new warning, you can quickly add it to a rule in your application using the new pxAddGuardrailMessage function.
For more information on the tabs and available fields on the Message form, see About Message rules.
Easy-to-browse warning catalog
Valid from Pega Version 7.1.7
All Pega 7 warnings have been converted to Rule-Message instances, each with a clearly written, risk mitigation path. This allows you to use the Records Explorer to browse through all warnings in the system, organized by category. To view warnings associated with specific rules in your application, refer to the Application Guardrails landing page.
Communicate guardrail compliance with the pxAddGuardrailMessage function
Valid from Pega Version 7.1.7
Now that guardrail warnings are in the model, you can easily attach them to rules in your application using the new pxAddGuardrailMessage function. Call this function to display warnings to your application users when they do not adhere to guardrails or best practices. Adopting this function in your application allows you to:
- Use localizable Rule-Message instances that are categorized by severity and application impact.
- Add dynamic warnings to your rules by passing parameters to a standard or custom message.
- Stop using and maintaining hard coded strings.
Design time view of warning messages
Run time view of an attached warning
This function supersedes the addWarning function, which has been deprecated. You can continue to use the CheckForCustomWarnings extension point, but it is recommended that you convert hard coded strings to messages and migrate any dependencies on addWarning to pxAddGuardrailMessage.
For more information on message attaching techniques, see Working with messages.
Track custom details with extensible messages
Valid from Pega Version 7.1.7
The customizable Message form gives you the freedom to expand upon default categories, store application specific data in a message, and enforce specialized validation. Leveraging these options makes it easier for you to identify a specific variety of message and incorporate new properties into your existing message processing logic.
For more details on which rules to override, see How to extend the Message form.
Collections more effectively model business decisions
Valid from Pega Version 7.1.7
Use the redesigned Collection form to model business logic or implement rule engine patterns in your application. This form is now located in the Decision rule category.
You can add response actions to each collection step to process return values transparently, and simplify your implementation by calling a function alias or when condition instead of an activity. Use one of the supported Stop methods to cease processing in the current collection or all collections in the call stack.
For more information on the available features on this rule form, see About Collection rules.
Existing collections are deprecated
Valid from Pega Version 7.1.7
The original implementation of the Collection form is deprecated. Legacy instances in your application remain functional; however, any new instance you create uses the redesigned Collection form. Use the Decision category in the Records Explorer to view all collections available to you.
For guidance on upgrade limitations, see the Deprecated Collection form.