Create, Save As, and Specialization forms
Valid from Pega Version 7.1.4
The familiar “New” and “Save As” forms have been streamlined to make record creation faster and more intuitive. You can easily target a specific layer in your application stack, interactively define the record’s configuration and select only those circumstance definitions that make sense for your use case.
While the underlying behavior for creating a record is not new for this release, the redesigned UI of these forms and new defaulting strategy for fields is worth noting:
To launch these forms, use one of the new options found in the action area of the form header:
Note that not all record types support the ability to specialize by circumstance.
For more guidance on how to use the Create, Save As and Specialization forms, please refer to: Intuitive record creation and specialization
Redirect users to logout screen
Valid from Pega Version 7.1.4
New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout.
A new template, Web-Session-Return-Template, has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish. This template can be copied to a ruleset visible to unauthenticated requestors (via node configuration) and used to override Web-Session-Return.
Source field not displaying in data transform
Valid from Pega Version 7.1.4
On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.
(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)
Workaround
- Below is a data transform that has been configured to use Update Page.
- If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
- At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
- Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
Core Engine
Valid from Pega Version 7.1.4
This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.
- A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
- Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
- Caching and performance have been enhanced.
- Declare expressions will work with embedded page lists when creating forms.
- Mandatory parameters on a data page can handle blank values.
- Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
- System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
- The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
- When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
- When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy.
Designer Studio
Valid from Pega Version 7.1.4
Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.
- The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
- Expression Builder has been enhanced to work with IE8.
- New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
- Performance improvements were made when saving and validating rules.
- Performance of the Guardrails Dashboard has been improved.
- The display of circumstanced rules in Application Explorer has been enhanced.
Customized application overview documents in App Studio
Valid from Pega Version 8.3
Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.
For more information, see Creating project documents for stakeholders in App Studio, Exporting a data model into a document.
New send email automations and enhancements
Valid from Pega Version 8.3
You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.
You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.
For more information, see Calling an automation from an activity and Viewing automations.
Remote device log retrieval from online-only mobile apps
Valid from Pega Version 8.3
In addition to device logs from offline-enabled mobile apps, Pega Mobile Client™ can now upload device logs from online-only mobile apps. The upload to Pega Platform™ starts when a user restarts the mobile app. You retrieve device logs from a specific device to support remote users and troubleshoot mobile apps.
For more information, see Retrieving device logs.
Improved mobile user experience with spaces
Valid from Pega Version 8.3
Spaces in mobile apps have been enhanced to provide a wider screen area for navigation between content tabs such as Pulse, Boards, Subspaces, and Tasks. Mobile users can now use native selection controls to choose from the same space-specific actions that are available to users of desktop-based applications. The enhancement improves the usability of spaces and promotes collaboration between mobile users.
Spaces on mobile apps do not require any additional configuration.
For more information about spaces, see Collaborating with users by using spaces.
Increased display area in mobile apps
Valid from Pega Version 8.3
Mobile apps now support hiding the top and bottom bars when the user scrolls down. When the user scrolls up, the bars appear again. This enhancement improves the mobile user experience by presenting more data on the screen, for example, a longer list of items.
For more information, see Advanced layout options.