Valid from Pega Version 7.1.4
This release has continued to focus on improving the functionality of the design environment with improvements to the Case Designer and stage configuration. Additional end user capabilities were also added to allow for processing a wider variety of cases, for those with and without stages and improved bulk processing handling.
- Flow action processing now uses the primary page instead of the interest page when using case/stage local actions, so that embedded flows are properly populated.
- Case-wide local actions rely on pzInternalStageFlow when there are no active, non-hidden assignments on the case. These case-wide local actions will now appear on a stage-less flow with no assignments.
- If a (valid) error is displayed in the outline view, saving or clicking around will not delete the error - the error will remain as a reminder to the developer to solve whatever problem is being flagged.
- May now add Cascading Approval validation and edit the parameters from the Case Designer Stage and Step page.
- Page labelling ("Page 1 of X") appears in the history list presented in the audit tab.
- The bulk processing feature has been enhanced.
- The Outline View functionality was changed so that the visible page will no longer refresh each time a flow is edited.
- The Post value was added to the instructions text field, so data isn't lost between nodes in the outline View.
- When Assign to Operator or workbasket is included as a filter, the bulk processing gadget is supposed to get a list of assignments. The UI for the results was enhanced for assignments to include a column for instructions so that the different assignments on the same work item can be distinguished.
- When designing a case type’s stages, it is no longer possible to skip the last stage (by using the "skip stage when" setting). When creating or editing the last stage, developers may no longer set a skip when rule; if tried, the system will display a warning and prevent that. If a Skip When rule is set up for a stage, and then all the intervening stages are deleted so that this stage becomes the last stage, the warning will display, and the Skip When rule will not be visible. If another stage is then added after that, the Skip When rule becomes visible again.
- When one or more locked work objects are processed using the Process Selected Items button, the action will be performed on the selected work objects. If the action is successful, a green tick appears on the work object. If it is not successful, a red cross will appear.
- When the topmost RuleSet in the RuleSet Stack is locked, customers may now open up Outline View by clicking "Configure Process Details" and make exploratory changes to experiment. Because the RuleSet is locked, these changes may not be saved, but the experiment can be tried.
Valid from Pega Version 7.1.3
This release had a focus on extending key capabilities to improve the ease of configuration based on early adopter feedback. Improvements were made in run-time performance, especially in high volume situations with complex case configurations. A series of cosmetic changes and fixes are included.
- The Wait shape now supports dynamic references.
- Issues were addressed with the CreatePDF and the CascadingApproval Smartshapes.
- Attachments have been improved.
- Issues with the Create Case Type functionality were addressed.
- The Pega Pulse functionality has been improved, including its performance.
- When auditing a work item, History is now the default tab.
Limited question and answer formats in new surveys
Valid from Pega Version 7.4
Complex questions and some answer formats for simple questions, such as attachment, are not supported by the new surveys that you create. Although you can create stand-alone questions in your survey library that use these formats, you can add these questions to legacy surveys only.
For more information about supported answer formats, see Answer formats for questions in a survey.
Known issue: SAML IdP import uses only the last certificate
Valid from Pega Version 7.4
When you configure the identity provider for a SAML SSO authentication service, the backing keystore rule for the verification certificate is created with only the last certificate from the IdP metadata, instead of using all of the certificates.