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.
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.
Both Transfer and Transfer Assignment flow actions are displayed in the Bulk Actions tool
Valid from Pega Version 7.1.7
Both the deprecated Transfer flow action and its Pega 7.1.7 replacement Transfer Assignment (pyTransferAssignment) might appear in the menu on the Bulk Actions tool.
Either of the following situations can cause this behavior:
- The original application did not contain the UI-Kit-7 ruleset, for example, the application was built on Pega 7.1.5.
- The default flow actions are based on BulkProcessTransferFlowAction system settings.
- If you add pyTransferAssignment as a local action in a case type rule, users will see both old and new actions.
- The flow actions are still available unless you override the settings.
- The upgraded application uses the UI Kit ruleset, but the Transfer local action was defined in the original case type rule and copied to the application.
- The original is explicitly defined in the application.
- pyTransferAssignment is available through the system settings in the UI Kit.
As a best practice, upgrade Transfer flow actions to Transfer Assignment in your flows and local actions. The UI Kit ruleset ensures that the new flow actions are optimized for mobile interfaces. In addition, Transfer Assignment provides multiple transfer functions (to manager, workbasket, advanced options) in a single form.
Alternatively, keep the original system settings so that the existing flow actions are still available.
Flow import functionality is limited to Microsoft Internet Explorer Version 9 and Version 10 in Pegasystems Public Format
Valid from Pega Version 7.1.7
Importing a flow in the Rule-from-File wizard is limited to Microsoft Internet Explorer 9 and Internet Explorer 10 in the Pegasystems Public Format .
Search field type is deprecated
Valid from Pega Version 7.1.9
The search field type in Form Builder is deprecated. Use a data reference or user reference instead, both of which prompt users with an autocomplete field at run time.
For the full list of supported field types in Form Builder, see Supported display modes by field type.
WriteHistory parameter has been removed from Link-Objects method
Valid from Pega Version Pega Platform
The WriteHistory check box has been removed as a parameter to the Link-Objects method on the Activity form. Users who are upgrading from versions prior to Pega 7.2 do not have to take any action because history details rely on the "linked from" object and this option stored results in the "linked to" object.
To correctly capture a link event in the history of an object, call the History-Add method.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
Label in previous versions | Label in Pega 7.2 |
---|---|
Text | Text (single line) |
Text (multiple lines) | Text (paragraph) |
Check box | Boolean |
Date and time | Date & time |
Date | Date only |
Drop down | Picklist |
Number (integer) | Integer |
Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.