Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Word merge support with Microsoft Silverlight plug-in

Valid from Pega Version 7.1.3

PRPC features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with IE) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft, as it is not shipped with PRPC.

Some common PRPC features affected by this change include the Application Document Wizard, App Profile, Specifications Landing Page, Specification form, and Case Type Landing Page.

Prior to using these features, Users of PRPC 7.1.3 need to set up their client system(s) as follows:

1. Install Silverlight plug-in

Follow the PRPC prompt to install Silverlight when you attempt to use the Word merge feature:

Silverlight1.jpg

Or download package directly: www.microsoft.com/silverlight/

2. Install PRPC prerequisites

Microsoft Internet Explorer (IE) browsers automatically detect the need for PRPC prerequisites and will prompt for install:

Silverlight2.jpg

Non-IE browsers will load a pop-up window when the user attempts to use the Word merge feature.  Use the link to manually download PRPC prerequisites:

Silverlight3.jpg

Extract the .zip file, execute setup.exe and follow the install wizard:

Silverlight4.jpg

Administrators setting up multiple clients at once may refer to the pzSLpreReqs.cab available in the PRPC 7.1.3 resource kit.

3. Restart browser

Log out of PRPC, close all open sessions and restart your browser.

The PRPC feature integrated with Word merge is now ready for use; Silverlight prompts are no longer displayed.

4. Troubleshooting

Silverlight installation requires access to your file system and a registry setting update to “trust” the associated Verisign certificate.  Contact your administrator if you encounter any security or permission errors during this process.

While Silverlight is cross-browser, it is not fully cross-platform.  Mac users may use Word merge features in Chrome via Parallels.

See the PRPC Developer Help for more information on browser setup requirements.

Customize your report headers

Valid from Pega Version 7.1.5

You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.

Advanced inline report filters

Valid from Pega Version 7.1.5

You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.

Tracer supports SOAP messages

Valid from Pega Version 7.1.5

You can now select a Tracer Settings option to display SOAP connector and services messages in Tracer, which provides users with a better understanding of SOAP connector behavior.

Service levels for case stages

Valid from Pega Version 7.1.5

Service levels are available for stages in stage-based case management applications.

The service level starts when a case enters a stage and stops when it exits. The service level is defined in the Service level for stage field on the "Stage Configuration" dialog, which is accessed on the Case Designer Stages and Processes tab.

108951_stagesla.png

Alternatively, you can add a stage service level on the case type record's Stages tab.

Customize your starting flow list

Valid from Pega Version 7.1.5

The Designer Studio Create menu now populates the list of starting flows by referencing the case types that you select (including case types in Create Menu checkbox) on the application form's Cases and Data tab. The order of the case types on the tab dictates the order of flows that appear on the menu.

108956_CreateCaseMenu.png

Previously, the Create menu displayed all starting flows in the current workpool. This new feature enables you to control which flows appear on the menu.

You can change the sort order by customizing the extension activity pySortStartingFlows. For example, you can sort the flows by their short descriptions.

Where-Am-I? includes stage and step progress

Valid from Pega Version 7.1.5

In stage-based case management applications, the Where-Am-I? display includes a read-only presentation of primary stage and step shapes. Green checkmarks indicate completed steps. A red arrow indicates the current step.

108961_whereami_0.png

Stop active processes on stage exit

Valid from Pega Version 7.1.5

The Change Stage smart shape provides a "Remove processes on exit stage" option that stops all active processes in a stage when a case leaves it. The system removes the stage's open assignments from user forms.

Standard page lists for attachments

Valid from Pega Version 7.1.5

The following new standard page lists allow you to easily reference attachments in your designs:

  • pyAttachments — Holds a list of attachments of the current case.
  • pyAttachmentCategoriesList — Holds a list of attachment categories of the current case. This property can be used to fetch the attachment information by category (pyAttachmentsByCategory).
  • pyAttachmentsByCategory — Holds a list of attachments for the category set in the pyAttachmentCategory property in the current case.

When a user or system adds an attachment, the system automatically associates the page lists with the case, and populates them when the properties are referred to.

Creating an attachment category in a case type record automatically creates a property reference. See Redesigned Attachment Categories tab on Case Type record.

In addition, you validate the existence of an attachment by referencing the new function alias pxIsAttachmentOfCategoryInCase in a validate record. For example, you can use the properties and a validate record for building when logic that makes it necessary for a user to attach a document of category "SECCompliance" before the case can enter a stage.

Redesigned Attachment Categories tab

Valid from Pega Version 7.1.5

The Attachment Categories tab on the case type record has been redesigned as follows:

  • In the Category field, you can associate case types with a case by selecting one in the application ruleset stack, or create a new one by typing a name in the field.

    When you add a category to the list and save the record, the system automatically generates a page list property that that can be used to easily reference attachments by category.

    ​In the example shown below, the page list property AuditComplianceAttachments can be used to access a list of attachments in the Audit Compliance category.
    108697_attachments1.png

For ease of use during your design session, you can access this functionality using the "Attachments" option on the Case Designer Details tab.

The new function alias pxIsAttachmentOfCategoryInCase checks if an attachment of a particular category is attached to a case.

  • Auto-Attach capabilities are deprecated but still supported. The tab displays a read-only list of attachments that were configured with this feature in previous releases.
    • To remove this capability, delete the item.
    • For new development, use the Attach Content smart shape in your process diagram.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us