Published Release Notes

Case Management

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.

Core Engine

This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.

• A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
• Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
• Caching and performance have been enhanced.
• Declare expressions will work with embedded page lists when creating forms.
• Mandatory parameters on a data page can handle blank values.
• Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
• System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
• The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
• When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
• When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy. 

Designer Studio

Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.

• The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
• Expression Builder has been enhanced to work with IE8.
• New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
• Performance improvements were made when saving and validating rules.
• Performance of the Guardrails Dashboard has been improved.
• The display of circumstanced rules in Application Explorer has been enhanced.

Case Management

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.

Designer Studio

Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.

• Treegrid controls work more quickly in IE9 and IE10.
• On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
• Message error handling has been improved.
• Log messages have been cleaned up.
• Connectors may now be used in Data Pages.
• Move Rules wizard has been enhanced to work in Version 7.1.

Automated Unit Testing (AUT) content removed from the help

Information about Automated Unit Testing (AUT) has been removed from the Pega 7 Platform help, beginning with version 7.2.2. The AUT information is still available in earlier versions of the Pega 7 Platform help and on the PDN in the topic category Testing Applications.

PegaUnit testing is now supported on data pages, activities, data transforms, strategies, decision tables, and decision trees, which you can use to quickly and easily create test cases for your Pega 7 Platform applications instead of using AUT.

For more information, see:

• Pega 7.2.2 behavior when switching between PegaUnit testing and Automated Unit Testing features
• Automated Unit Testing

Security fields in JFrog Artifactory repository rule form removed

The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.