Collaborate on shared content by using documents
Valid from Pega Version 8.1
You can now share additional information about cases with all users in your application by using documents. Documents enable you to view shared content on a landing page and collaborate on the content with other users in Pulse so that you can resolve cases more quickly.
For more information, see:
- App Studio – Collaborating on shared content by using documents
- Dev Studio – Collaborating on shared content by using documents
Capture real-time feedback with Agile Workbench
Valid from Pega Version 7.3
Project stakeholders can use the new Agile Workbench tool to capture real-time feedback directly in an application, which can increase the efficiency of application development. You capture feedback by creating a user story, bug, or feedback item, and these work items can include video recordings of screens, annotated screen captures, file attachments, or URLs. In Designer Studio, you can configure Agile Workbench to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems.
For more information, see:
- Pega Express 7.3 – Agile Workbench
- Pega Platform 7.3 – Agile Workbench
Enhancements to PegaUnit test cases
Valid from Pega Version 7.3
Several enhancements have been made to PegaUnit test cases.
- You can now use the following new comparators for the page assertion:
- Has errors – The assertion passes if the system finds all the pages for which there are errors.
- Has no errors – The assertion passes if the system finds all the pages for which there are no errors.
- You can now export a list of all the PegaUnit test cases that are in the system or that are configured on a specific rule type to Microsoft Excel format.
- You can now view PegaUnit test cases for built-on applications.
For more information, see the Configuring page assertions and Exporting PegaUnit test cases help topics.
Ability to edit and copy data from an email to case properties for an Email channel
Valid from Pega Version 8.1
The procedure for triaging an email case has been improved to help automate the process and to ensure that the case data is always up-to-date and accurate. The system can pull data, such as a date, name, or an address, out of the received email or its attachments, and automatically assign the data to a spun-off business case property. To help the system learn, you can highlight using a color, edit entity types, and map entity types for an email triage case to business case properties. You can also update cases with new properties, if triage cases are identified as duplicates and contain new detected properties. Each mapped entity type is marked in different color and an entity map legend helps you identify what each color represents.
For more information, see Email triage and Defining suggested cases for the Email channel.
Relevant records management shows more information
Valid from Pega Version 8.1
Relevant records for a class now include more information that you can use to manage the records for your application development. As a result of these enhancements, you can:
- View inherited and inactive relevant records for the specified class.
- Mark specific records as active or inactive for the specified class.
- Mark specific records as relevant on the rule form.
You can use these new details to filter the list of relevant records for a class on the Relevant Records tab of the selected class. For more information, see Managing relevant records and Marking records as relevant records.