DCO
Valid from Pega Version 7.1.3
In this release, specification support in Case Designer was improved. Also, improvements and fixes were made to the New Application Wizard.
- Changes were made to support a split schema environment
- Shared and Component RuleSets can be copied.
- Can edit in Word from either Grids or Lists.
- More than 50 case types are now supported for an application.
Integration
Valid from Pega Version 7.1.3
Usability enhancements have been made to the integration wizards. The REST end-point integration has been improved, and XML parsing functionality has been enhanced.
- PRPC services can return Report or Listview data as XML.
- Work items may now be processed when accessing from a link in system-created emails.
- An SMTP outage will not cause an application to stop working.
- File listener will now read files using a leading asterisk (*).
- XML Parse rule will handle schema validation.
- PegaImageViewer will now work with Version 7.1.
- Security measures are enhanced for SOAP connections to web services.
- After generating rules using REST wizard, the Undo Generation button will delete all the generated rules.
- Email wizard has been improved.
Reporting
Valid from Pega Version 7.1.3
This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback. A series of cosmetic changes and fixes are also included.
- Multiple boxes may be checked on List view checkboxes
- Dashboard Charts slider has been improved.
- Summary View reports and charts have been enhanced.
- Column properties can be added to a report in the Report Editor.
- List view column widths can be set by Smart Info.
- Listviews will display correctly for updated systems.
- Improvements to the GuardRail Report.
System Management
Valid from Pega Version 7.1.3
The PRPC installer has been enhanced to handle additional error conditions related to partial installs and duplicate keys; additionally, the hotfix rollback feature has been improved, and the Rulebase compare tool now supports HTTP(S) environments.
- Rollback feature has been enhanced.
- RuleBase Compare will work for secure (HTTPS) environments as well as non-secure (HTTP) environments.
- Install will gracefully handle the presence of a duplicate key during import.
- When install fails, system will set tables back to original state.
- Remote MBean methods will now work on multi-servant load-balancing systems.
- Enhancements were made to harnesses in Split Schema systems.
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.
Application Express and the Content Security Policy
Valid from Pega Version 7.1.7
Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.
When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.
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.