Case Management
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.
Designer Studio
Valid from Pega Version 7.1.3
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.
Decision Strategy Manager
Valid from Pega Version 7.1.3
Fixes were made that improve the configuration and execution of Batch Decisions. In particular, the capability to use Structured Data has been enhanced. Some notable improvements have also been made to the UI of Visual Business Director.
- The structured data input configuration will now work even though there is no data.
- VBD has been enhanced to work with Version 7.1.
- The structured data input configuration will now work with nested structures.
- Association rules from Version 6.3 will now work with 7.1 structured data.
User Interface
Valid from Pega Version 7.1.3
Issues for cross-browser support for Designer Studio have been addressed. Improvements were made in run-time performance for data pages with grids, and a number of cosmetic changes and fixes were made.
- Improved loading of Javascript files during saving Harness rules.
- Login Performance improvements
- A cursor pointer issue was addressed in Case Manager.
- In reports, data in columns will now right-align.
- Improved section validation functionality
- Harnesses with screen layouts will now save when there is a refresh condition on a panel.
- Outline View tree has been improved.
- Improvements to Repeat Grids using Data Pages as a source.
- Formatted text cells can be put into a grid to display the value of a property retrieved from a Report Definition join.
- Designer Studio changes to support IE9 and IE10.
- Improved designer studio layout
- Designer Studio changes to support quirks mode in IE8 and IE9.
- Improvements to SmartLabels in Data Pages
- Tab groups will take parameters for pre-activities in a defer load setup.
- Sections support nested dynamic layouts.
Certain flow actions deprecated and replaced
Valid from Pega Version 7.1.7
To ensure compatibility with supported browsers and mobile devices and to enhance ease of design, the following flow actions are deprecated and replaced. As a best practice, use the replacement actions for new development. The deprecated rules are still supported and do not have to be updated.
| Deprecated | Replacement |
|---|---|
| Transfer | Transfer Assignment |
| TransferAdvanced | " |
| TransferToManager | " |
| TransferToWorkbasket | " |
| Approve | Approval |
| Reject | " |
| AttachAFile | Attach Content |
| pyAdjustSLA | Adjust Assignment SLA |
| pyAdjustSLATimes | " |
| pyChangeAssignmentSLA | " |
| pyUpdate | Update Case |
For example, the new Transfer Assignment action supports the most common routing options such as operator, workbasket, and reporting manager. Advanced options allow users to escalate, set due dates, update status, and provide instructions.
Transform Assignment form
See Atlas - Standard Flow Actions (Local).
Service levels are available on stage steps
Valid from Pega Version 7.1.7
For greater flexibility when configuring stages, you can associate a service level (SLA) with a step within the context of the stage only. Because this SLA overrides the one associated (if defined) with a a step, other steps that employ the same flow are not affected and can be configured independently.
See Using the Stages & Processes tab.
Managers can create and update cases using the Bulk Actions tool
Valid from Pega Version 7.1.7
The capabilities of the Bulk Actions tool have been expanded so that managers can go beyond simply being able to make bulk updates to existing cases. They can now:
- Create top-level cases for any case type in your application. By default, you can specify the label, description, and work status for each case.
- Define the case information you want to display on the grid by overriding the section pyBulkUpdate and configuring the columns.
- Update the case information you created in the Bulk Actions tool.
Create Cases option in the Bulk Actions tool
See Case Manager Portal — How to process assignments and cases in bulk.
Define distinct names to implementation and framework class layers in Application Express
Valid from Pega Version 7.1.7
When generating both implementation and framework applications in Application Express, you can now name the framework application and workpool class layers independently. This eliminates the need to update a framework's class structure in the new application. Previously, the framework layers used the same names as the implementation and could not be updated.
Class structure name fields in Advanced Configuration dialog
See Application Express — Advanced Configuration.
New case types contain one stage
Valid from Pega Version 7.1.7
When you create a new case type in the Cases Explorer or in Application Express, the system creates only one default stage. A single starting stage provides an intuitive design experience and eliminates the need to delete unused stages. Previously, a new case type contained three default stages.
Edit process-based case type flows in Case Designer Process Outline view
Valid from Pega Version 7.1.7
If your case type does not employ a stage-based design, you can now employ the Step Tree and other features available in Process Outline view to facilitate your design.
Click a process tile in the Stages & Processes tab to open the flow in Process Outline. In this example, the Graffitti report is selected.
Processes in Stages & Processes tab
The process opens in Process Outline view. Note that the tree view allows you to easily see and update the underlying shapes and subprocess that compose the Single Approval process.
Process in Process Outline view