Customized application overview documents in App Studio
Valid from Pega Version 8.3
Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.
For more information, see Creating project documents for stakeholders in App Studio, Exporting a data model into a document.
Task board enhancements for improved tracking of tasks
Valid from Pega Version 8.3
App Studio and end-user portals, such as Case Manager, now provide an enhanced task board which helps you improve collaboration on task resolution. For example, you can create a checklist within a task, and then update the checklist to inform other users about the progress of the task. Attach content to a task to ensure that all users have the information that they need, and to make tasks more meaningful. Now you can also categorize tasks, and then filter them by category, to quickly access relevant information.
For more information, see Monitoring and tracking tasks in Dev Studio, Monitoring and tracking tasks in App Studio.
More efficient navigation between applications in App Studio
Valid from Pega Version 8.3
The new My Applications gadget helps you switch applications in App Studio more conveniently. You can also search applications by name instead of choosing an application from the list, and then select the access role that you want to use. In addition, you can see descriptions of your applications and create an application by going to the My Applications landing page. To use the My Applications gadget, ensure that you update the UI Kit to version 14.
For more information, see Adding the My Applications gadget, Switching between applications in App Studio.
Sign and encrypt signatures and content with additional algorithms
Valid from Pega Version 8.4
You can now authenticate using JSON Web Token (JWT) token profiles to symmetrically and asymmetrically encrypt both signatures and content. All algorithms in the Nimbus JWT library are supported, including nested tokens. Custom key identifier headers (kid) are also supported. Use token profiles to securely propagate identities and transfer data between systems.
For more information, see Creating a processing JSON Web token profile.
For more information, see Creating a generation JSON Web token profile.
Set the status of a case on stage entry
Valid from Pega Version 8.1
You can now set the status of a case when it enters a stage. By setting the status of a case on stage entry, you can communicate to stakeholders how close a stage is to resolution. For example, if a case is in the approval stage, you can set the status of the case to "Under review" when the case enters the stage.
For more information, see:
- App Studio – Changing the status of a case
- Dev Studio – Changing the status of a case
Conditionally skip a stage
Valid from Pega Version 8.1
You can now define a condition in App Studio and build an expression in Dev Studio that causes a case to skip a stage. The system evaluates the condition or expression at run time and skips the stage if a true value is returned. By skipping the current stage when it is not relevant, you can resolve a case more quickly by moving the case to the next stage in the sequence.
For more information, see:
- App Studio – Requiring conditions for stage entry
- Dev Studio – Requiring conditions for stage entry
Conditionally start a process
Valid from Pega Version 8.1
You can now define a condition that causes a case to start a process in a stage. When the condition evaluates to false, the case skips the process. You can resolve cases more quickly by moving a case to the next process in the sequence when the current process is not relevant.
For more information, see:
- App Studio – Conditionally starting a process by using a condition
- Dev Studio – Conditionally starting a process by using a when condition
Extract summaries from the analyzed text
Valid from Pega Version 8.1
You can now configure a Text Analyzer rule to extract information-rich blocks of text from the analyzed content and combine them into a comprehensive and coherent summary. By summarizing large documents, such as emails, you can facilitate making business decisions without having to read an entire document. In Text Analyzer rules, you can combine summarization with other types of text analysis, such as topic or entity detection, to extract the full context from a message.
For more information, see Configuring text extraction analysis and Tutorial: Extracting email context with Text Analyzer rules.
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
Automatically generate OpenAPI Specification documentation for application REST APIs
Valid from Pega Version 8.3
You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.
For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.