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.
Business logic-based routing cards enhancements
Valid from Pega Version 8.5
To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.
For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.