New location for case-type settings
Valid from Pega Version 7.2
The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.
For more information, see Configuring case-type behavior.
No private posts in new Pulse gadget
Valid from Pega Version 7.2
The new Pulse gadget does not support private posts. When you upgrade to the new gadget, any private posts of the following types that you created by using the previous version of the gadget become public.
- Operator posts
- Case posts
- Posts that used the generic pxPostMessage API with private posts enabled
- Posts that used the Pulse smart shape in PRPC 6.3 or earlier with private posts enabled
For more information about the new Pulse gadgets for developers, Pulse gadgets and custom APIs.
For more information about the using the new Pulse gadget, see Communicating with Pulse.
Atom Server and SOAP Server rule forms are deprecated
Valid from Pega Version 7.2
The Atom Server and SOAP Server rule forms are deprecated. Use the Connect CMIS rule form instead.
Existing rules that were created with the deprecated forms still work, but you cannot create new ones.
End of support for Microsoft Internet Explorer 9 and Internet Explorer 10
Valid from Pega Version 7.2
In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 9 and Internet Explorer 10 in January 2016, Pega 7.2 will be the last version of the Pega 7 Platform to support Internet Explorer 9 and Internet Explorer 10.
For Pega 7.2.1, you must upgrade to Microsoft Internet Explorer 11 or later, or use Google Chrome, Apple Safari, or Mozilla Firefox.
For more information about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.
Processes run by default when a stage is restarted
Valid from Pega Version 7.2
The Run on re-entry check box in Case Designer has been removed. As a result of this change, processes run by default each time that a stage is restarted. Users who previously had this check box cleared can use the Start when option in Case Designer instead to define the criteria for skipping a process.
For more information, see Adding a process to a stage.
End of support for Microsoft Internet Explorer 9 in Pega 7.2.1
Valid from Pega Version 7.2.1
In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 9, Pega 7.2.1 will not support Internet Explorer 9. You should not upgrade to Pega 7.2.1 if you are still using Internet Explorer 9. Otherwise, upgrade to Microsoft Internet Explorer 10 or later, or use Google Chrome, Apple Safari, or Mozilla Firefox, which support certain HTML5 and CSS3 standards not supported in Internet Explorer 9.
For more information about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.
Conversion of single-step assignments is no longer required
Valid from Pega Version 7.2
You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
The following table lists the step labels in Case Designer that were updated to support this change.
Step label in previous versions | Step label in Pega 7.2 |
|---|---|
| Single-step assignment | Collect information |
| Approval | Approve/Reject |
| Attachment | Attach Content |
| Case | Create Cases |
For more information, see Adding a step to a process in a stage.
Discontinued support for multithreaded requestors
Valid from Pega Version 7.2.1
Multithreaded requestors are no longer supported in the Pega 7 Platform. Multithreading was previously specified by the prconfig setting initialization/allowMultiplePRThreads. If this setting is set to true when you upgrade to Pega 7.2.1, errors occur during the quiesce process.
Child case queries can be slow after upgrade
Valid from Pega Version 7.2.1
After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.
For more information, see Performance improvements for child case queries.
Unused agents run in background
Valid from Pega Version 7.2
The Update PegaRULES database table statistics agent and the Collect PegaRULES database blob size statistics agent have been added to support future development. These agents run in the background, but they do not do anything. You can, but do not need to, disable them from the Edit Agent Schedule landing page.
For more information, see Agent Schedule form - Completing the Schedule tab.