Published Release Notes

Applications not working as expected when using fast processing for Connect REST and Service REST integration

In Pega^® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:

• The JSON property names and the clipboard property names must match.
• The JSON tree structure and the clipboard tree structure must be similar.
• The scalar arrays in JSON must be mapped to the clipboard as page lists.
• Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

In addition, page groups, value groups, and Java objects are not supported by fast processing.

Pega Survey documentation refers to deprecated field

The documentation for Pega^® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.

Data pages can source information from a robotic desktop automation

You can now configure data pages to source information from robotic desktop automations (RDA). Using an RDA to source a data page allows you to connect your Pega Platform™ application to any application that is accessible from an end-user's desktop. By using automations to retrieve data and load it into a data page, you can use data virtualization to separate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

Set the status of a case on stage entry

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

Resolve child cases with the parent case

You can now configure a stage to resolve open child cases when the parent case is resolved. Resolving child cases on the resolution of the parent case ensures that no child cases are left open when the parent case reaches the end of its life cycle.

For more information, see:

• App Studio – Configuring case resolution
• Dev Studio – Configuring case resolution

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