Published Release Notes

Conditionally skip a stage

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

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

Conditionally display an optional task

You can now define a condition that decides whether an optional task for a case type or a stage is displayed at run time. Optional tasks require additional processing, and by excluding the tasks that are not relevant, you can resolve cases more quickly.

For more information, see:

• App Studio – Conditionally displaying an optional task
• Dev Studio – Conditionally displaying an optional task

Conditionally display a supporting process

You can now define a condition that causes a case to display a supporting process for the case type or for a stage in the case type. When the condition evaluates to false, the case does not list the process. Supporting processes require additional processing, and by skipping the processes that are not relevant, you can help users resolve cases more quickly.

For more information, see:

• App Studio – Conditionally displaying a supporting process
• Dev Studio – Conditionally displaying a supporting process

Send email notifications for goals and deadlines

You can now configure an assignment or approval in a case type to send email notifications to the users associated with the case when the goals and deadlines are not met. You can create the subject and content for the notification message. The system sends email notifications when the suggested and required completion times for an assignment or approval elapse. By notifying relevant users about goals and deadlines, you can ensure that service-level agreements are strictly enforced during case processing.

For more information, see:

• App Studio – Setting goals and deadlines for task completion
• Dev Studio – Setting goals and deadlines for task completion

Supported artifacts section removed from repository rule form

The Supported artifacts check box has been removed from the repository rule form. Developers can use repositories to provide centralized storage, versioning, and metadata support for application artifacts.

For information about repository connections, see Creating a repository for file storage and knowledge management.

Improvements in the training data model for the Email channel

From the training data screen of the Email channel or while you are triaging an interaction case, you can now fix incorrect entities and add new entities that were not detected. These improvements to the data training model that has been defined for the Email channel interface help the Pega Intelligent Virtual Assistant for Email make better predictions.

For more information, see NLP model for an Email channel and Updating entities for an Email channel.

Search added for case data

You can enable search for individual case types. When search is enabled for a case type, all text in the case data is searched, making it easy for your application users to find work items.

For information about enabling search for a case type, see Including indexed data during case search.

Ability to generate a dedicated search index for a case type

You can generate a dedicated search index for a case type. Using a dedicated index makes reporting faster without putting additional requirements on the database. 

For more information, see Including indexed data during case search.

Use repositories as sources for File data sets

You can configure remote repositories, such as Amazon S3 or JFrog Artifactory, or a local repository, as data sources for File data sets. By referencing an external repository from a File data set, you enable a parallel load from multiple CSV or JSON files, which removes the need for a relational database for transferring data to Pega Platform™ in the cloud.

For more information, see Creating a File data set record for files on repositories and Configuring a remote repository as a source for a File data set.