Published Release Notes

Flow rules not supported in IE8

In versions prior to 7.1.2, flow rules do not open in Internet Explorer 8 (IE8). Upgrade your system to the latest version of PRPC or access flows from another supported browser.

Deprecated end user portals

The following portals are no longer be supported:

• SysAdmDD
• WorkUserDD
• WorkManagerDD

As a best practice, customize standard, supported portals rather than update your existing portals to include new features.

Limited access for end user portals

The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:

• WorkUser
• WorkManager

Nesting dynamic containers not supported

Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.

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