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.
Default value of the threadpoolsize agent affects batch indexing
Valid from Pega Version 8.5.2
After you patch Pega Platform to version 8.5.2 or higher, the system changes the default value of the threadpoolsize agent, which controls the number of concurrent activities (threads) in the system, from 5 to 15. Batch indexing in Pega Platform™ does not require all 15 threads, so you can change the agent value to increase system performance by managing the indexing/distributed/batch/numworkers dynamic system setting.
If your deployment does not support that setting, and batch indexing does not use Queue Processors, the system uses the threadpoolsize value for batch indexing instead.
For more information, see Editing a dynamic system setting.
Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6
Valid from Pega Version 8.6
Upgrade impact statement
On-premises upgrades of Pega Infinity release 8.4.2 and later to version 8.5.1 or later on Tomcat and PostgreSQL are completed with near-zero downtime. However, upgrading to Hazelcast 4.x requires that you shut down and restart your application server.
What is required to update the application to be compatible with this change?
Hazelcast 3.x is enabled by default. For near-zero downtime upgrades, you do not need to perform any action.
For instructions about upgrading to Hazelcast 4.x, see one of the following topics:
- For near-zero downtime upgrades from Pega Infinity release 8.4.2 or later on Tomcat and PostgreSQL, see "Optional: upgrading to Pega Platform version 8.6: Upgrading to Hazelcast 4.x" in Near-zero downtime Upgrade Guide for Pega Platform version 8.4.2 and later for Tomcat and PostgreSQL.
- For all other upgrades, see "Optional: upgrading to Hazelcast 4.x" in the appropriate upgrade guide.
Insights from 8.5 require additional configuration after upgrade
Valid from Pega Version 8.6
Upgrade impact
After you upgrade Pega Platform™ version 8.5 to 8.6, the Explore Data landing page might not include insights that come from the earlier version of the product.
What steps are required to update the application to be compatible with this change?
Run the pxUpgrade85Insights activity to make all insights from version 8.5 accessible for you in 8.6. By running this activity, you upgrade insights with new metadata that is required in version 8.6. For example, the pxUpgrade85Insights activity provides you with the option to set the visibility of insights to private, public or shared.
For more information about insights, see Visualizing data with insights.
Improved indexing of StringList and StringGroup property types
Valid from Pega Version 8.6
Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.
Upgrade impact
After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed.
What steps are required to update the application to be compatible with this change?
On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.
For more information, see Indexing class data.
Change logic does not work in Report Editor
Valid from Pega Version 7.1.2
The Report Editor change logic button does not work. As a workaround, use the rule form to change the logic.
Flow rules not supported in IE8
Valid from Pega Version 7.1.1
In versions prior to 7.1.2, flow rules do not open in Internet Explorer 8 (IE8). Upgrade your system to the latest version of PRPC or access flows from another supported browser.
Stages and Steps may not appear as expected
Valid from Pega Version 7.1.5
There are some unique configurations of the newly enhanced pxDisplayStages gadget that can lead to case type "Stages and Steps" appearing more than once or not at all. In the event that your application experiences one of these scenarios, the recommended work around is to relocate the gadget:
- Add pxDisplayStages to the pyCaseContainer section (or equivalent)
- Remove pxDisplayStages from the pyCaseActionArea section (or equivalent).
Geolocation tracking requires browser permission
Valid from Pega Version 7.1.6
When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.