Use Page-Change-Class method to change a Page class
Valid from Pega Version 8.3
With the release of Pega Platform™ 8.3, using the Property-Set method to change the Page class shows a guardrail warning. Use the Page-Change-Class method to change the Page class instead.
For more information about the Page-Change-Class method, see Changing the class of a page and Page-Change-Class method.
CyberArk password vault support added for Pega database
Valid from Pega Version 8.3
With the CyberArk password vault, you can store your systems' passwords in a secure, central location and retrieve them from that location instead of directly entering credentials into the systems. This support is available only for IBM WebSphere environments.
For more information, see Pega Platform deployment guides.
Simple associations for quickly joining classes
Valid from Pega Version 8.3
Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Exploring the data model.
Association changes after upgrade
Valid from Pega Version 8.3
Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.
Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Associations.
Support added for multiple mashups
Valid from Pega Version 8.3
You can now include multiple mashups on a single webpage or browser, even if the mashups have different application and authentication requirements. Use mashups to embed a Pega Platform™ application as a gadget on your website. For example, you can embed Web Chatbot and Self-Service Advisor on the same website.
For more information about mashups, see Configuring the Mashup channel.
Changes to URL format for Pega Web Mashup
Valid from Pega Version 8.3
The format of Pega Web Mashup URLs now supports multiple mashups on a single web page. The new URL format prevents a mashup from sharing cookies with another mashup.
If you want to include multiple mashups on a single web page and one of the mashups was created before 8.3, you must regenerate the mashup to reflect the new URL format.
For more information, see <link to help topic>.
Change tracking tab removed from declare expressions
Valid from Pega Version 8.3
To simplify the configuration of a declare expression, the Change tracking tab has been removed from the declare expression rule form. To use the Change tracking tab, on the declare expression rule form, click Actions > Use legacy expression.
For more information, see Supported and unsupported configurations in simplified declare expressions.
Upgrade impact
The declare expression rules have been moved from the pr4_rule table to the new pr4_rule_declare_expression table.
The upgrade can fail if you customize the pr4_rule table, such as increasing the length of an existing column.
After a successful upgrade, the declare expression rule form is simplified and lightweight pages support declare expressions.
What steps are required to update the application to be compatible with this change?
Read-only data pages by default are lightweight. You could also enable lightweight pages for:
- Editable data pages by selecting the Enable option in the editable data page rule form.
- For all pages in a REST service by using the Lightweight clipboard mode in the Service REST form in the Rest API service.
Only simplified declare expressions are supported in lightweight pages. In simplified declare expressions, context-bound rules are not supported. However, a page context could be specified on the New or Save As form of declare expressions. For more information, see Declare Expression rules - Completing the New or Save As form.
Redirectguests mashup configuration has been removed
Valid from Pega Version 8.3
The authentication/redirectguests server configuration and data-pega-redirectguests attribute have been removed and are no longer required when you configure a mashup. This prevents you from needing to maintain multiple nodes to support some use cases that require the configuration value to be true and other uses cases that require the configuration value to be false.
For more information, see Configuring the Mashup channel.
Case-insensitive filtering in reports
Valid from Pega Version 8.2
Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.
For more information on report filtering, see Editing filter conditions.
Improved search indexing performance
Valid from Pega Version 8.2
Search indexing now uses a queue processor to improve indexing performance. Indexing can automatically restart if the database goes down temporarily. This saves time and manual action. As a result of using the queue processor for indexing, the following changes have been made to the Search Landing page.
- You cannot cancel indexing from the Search landing page. Cancel indexing by stopping the queue processor from the Data flow landing page.
- The progress message is not shown. View progress on the Queue Processor landing page.
- Queue processor information has been added.
For more information, see Stopping or pausing search reindexing.