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.
Enabling security policies now requires current password
Valid from Pega Version 7.1.3
As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced. When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.
For more details, review the Designer Studio > System > Settings > Security Policies landing page.
Guardrails compliance score
Valid from Pega Version 7.1.5
The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:
- A weighted compliance score (0-100) based on warnings, severity, and justification
- A percentage of compliant rules in your application
- Total number of rules in your application
- Total number of rules in your application with warnings (justified and unjustified)
Additional metrics include alert and interaction count trends over the last four weeks.
For more information, see Guardrails compliance score.
Access Manager portal
Valid from Pega Version 7.1.5
Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.
Directed inheritance view in Application Explorer
Valid from Pega Version 7.1.5
You can now specify which inheritance model is used to populate classes in the Application Explorer. From the top level menu, use the “Explorer Inheritance” option to choose between:
- Pattern: only display class names whose prefix matches the root node class name.
- Directed: first display classes that explicitly name the root node as the parent class; then display classes with pattern inheritance.
By default, the Application Explorer loads using Pattern inheritance.
Save Application Explorer filter selections
Valid from Pega Version 7.1.5
Application scoping control selections made in the Application Explorer are now persisted between sessions. These preferences are stored in an operator record on an access group level. If you delete (and later re-add) an access group on your operator form, the application scoping control defaults to all layers selected:
External access control DASS
Valid from Pega Version 7.1.5
A new Dynamic Admin System Setting (DASS) controls the Designer Studio's access to external systems, specifically the PDN RSS feed found on the home page.
By default, Pega-Desktop.AllowAccessToExternalSystem is set to TRUE. Update this setting to FALSE to hide the PDN RSS feed and ensure that no RSS fetch is performed.
Pinned classes in Application Explorer
Valid from Pega Version 7.1.6
The Application Explorer now includes a Pinned Classes section. This feature allows you to interact with a customized list of classes without having to explicitly switch context in the explorer.
Ability to deprecate a rule
Valid from Pega Version 7.1.6
You can deprecate any Rule- instance to indicate that it is no longer supported.
Users are warned when they open or reference a deprecated rule instance.
