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.
Geolocation tracking Map it links do not appear
Valid from Pega Version 7.1.6
If geolocation tracking is enabled, the first time you create a case in the first browser session, the Map it links do not appear next to the initial audit trail entries. When you submit the first flow action, the links appear next to all subsequent entries.
Cannot copy final section rules in UI Kit ruleset
Valid from Pega Version 7.1.6
You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).
Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at
, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.User interface distortions in the Decision Manager portal
Valid from Pega Version 7.1.6
By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.
Workaround:
- Open the application record.
- In Application Rulesets, remove UI-Kit-7.
- Save the application record.
User interface distortions in the Predictive Analytics Director portal
Valid from Pega Version 7.1.6
By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.
Workaround:
- Open the application record.
- In , remove UI-Kit-7.
- Save the application record.
Add additional columns to customized work history tables
Valid from Pega Version 7.1.6
The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:
<decimal name="pxLatitude" size="19" scale="9"/>
<decimal name="pxLongitude" size="19" scale="9"/>
Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button
Valid from Pega Version 7.1.6
A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.
Improved case auditing in App Studio
Valid from Pega Version 8.5
In Cosmos UI, App Studio now supports expandable case steps. This enhancement helps users quickly navigate a case and provides deeper insight into the case flow. In addition, Cosmos UI also introduces an improved history view that helps you better meet your business auditing requirements.
For more information, see Managing Cosmos UI settings in case designer.
Upgrade impact
After an upgrade to Pega Platform 8.5 or later, the history and chevron designs change automatically. However, applications with custom history settings might still display the styling that you defined in the override.
What steps are required to update the application to be compatible with this change?
If your application uses custom settings and you want to use the updated history, remove the overrides from the pyWorkCommonActions rule.
Removal of Pega Mobile Client 7
Valid from Pega Version 8.5
You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.
Upgrade impact
After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.
What steps are required to update the application to be compatible with this change?
Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.
Limits on active data flow runs
Valid from Pega Version 8.5
You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.
For more information see, Limit the number of active runs in data flow services (8.5).
Upgrade impact
If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.
What steps are required to update the application to be compatible with this change?
You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.