Published Release Notes

Post files and links with pxPostMessage API

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Case Management

This release has continued to focus on improving the functionality of the design environment with improvements to the Case Designer and stage configuration. Additional end user capabilities were also added to allow for processing a wider variety of cases, for those with and without stages and improved bulk processing handling.

• Flow action processing now uses the primary page instead of the interest page when using case/stage local actions, so that embedded flows are properly populated.
• Case-wide local actions rely on pzInternalStageFlow when there are no active, non-hidden assignments on the case. These case-wide local actions will now appear on a stage-less flow with no assignments.
• If a (valid) error is displayed in the outline view, saving or clicking around will not delete the error - the error will remain as a reminder to the developer to solve whatever problem is being flagged.
• May now add Cascading Approval validation and edit the parameters from the Case Designer Stage and Step page.
• Page labelling ("Page 1 of X") appears in the history list presented in the audit tab.
• The bulk processing feature has been enhanced.
• The Outline View functionality was changed so that the visible page will no longer refresh each time a flow is edited.
• The Post value was added to the instructions text field, so data isn't lost between nodes in the outline View.
• When Assign to Operator or workbasket is included as a filter, the bulk processing gadget is supposed to get a list of assignments. The UI for the results was enhanced for assignments to include a column for instructions so that the different assignments on the same work item can be distinguished.
• When designing a case type’s stages, it is no longer possible to skip the last stage (by using the "skip stage when" setting). When creating or editing the last stage, developers may no longer set a skip when rule; if tried, the system will display a warning and prevent that. If a Skip When rule is set up for a stage, and then all the intervening stages are deleted so that this stage becomes the last stage, the warning will display, and the Skip When rule will not be visible. If another stage is then added after that, the Skip When rule becomes visible again.
• When one or more locked work objects are processed using the Process Selected Items button, the action will be performed on the selected work objects. If the action is successful, a green tick appears on the work object. If it is not successful, a red cross will appear.
• When the topmost RuleSet in the RuleSet Stack is locked, customers may now open up Outline View by clicking "Configure Process Details" and make exploratory changes to experiment. Because the RuleSet is locked, these changes may not be saved, but the experiment can be tried.

Quickly create ad-hoc cases

The My Cases work area on the Case Manager portal introduces a Quick Create feature that lets users create cases and assign tasks that are not included in the processing of business cases (instances of case types defined in the Cases Explorer).  For example, a manager can create a case and a task to set up a phone conference with her staff, or a reminder to enroll in an online seminar. Users can also set up a series of tasks to represent all they work they need to do to accomplish a specific goal.

Integration

Critical customer-driven product improvements were made to SOAP services, SOAP connectors and connector wizard, CMIS connectors, and the Pega Image Viewer. These fixes addressed a handful of functionality gaps discovered in PRPC 7.1 and earlier releases by internal and external customers.

• A Connect-CMIS instance which was created using a reference to an ATOM Server Instance may now use Global Resource Settings.
• The Execute Synchronously (one-way operation) has been enhanced for SOAP Services.
• The Silverlight version of PegaImageViewer has been enhanced to print ranges of multiple pages at once.
• The SOAP Wizard has been improved to show all the ports which are available in the WSDL file.
• Two way SSL has been enhanced for the Connect-REST rule.

Support for sending emails by using Microsoft Graph

Email integration with Microsoft Office 365 now supports sending emails by using Microsoft Graph. With this enhancement, you can send email with a more secure protocol that complies with your organization’s security policy.

For more information, see Creating an email account.

Support for REST connectors to route network traffic via proxy

To easily route network traffic, you can now configure proxy details for individual REST connectors. This enhancement allows you to manage your proxy settings so that you can securely access online resources that lie beyond your proxy servers.

For more information, see Configuring a REST connector.

Connect-HTTP support discontinued

Pega Platform™ no longer supports Connect-HTTP rules. HTTP connectors were used to start HTTP request/response interactions between Pega Platform and external systems identified by a Connect HTTP rule (Rule-Connect-HTTP rule type).

After an upgrade to Pega Platform 8.6 and later, you can still use and modify existing HTTP connectors, but you cannot create new ones. As a best practice, use REST connectors instead, which offer more capabilities and have better support from development teams.

For more information, see Connect REST rules.

Data import wizard compatibility with Cosmos applications

The data import wizard is now Cosmos-compliant. When you launch the data import wizard as a page, you can leverage the new features provided by Theme-Cosmos, such as adding custom buttons and functionality to your Cosmos applications.

Improved processing of correspondence details

When you send correspondence, the system now does not update the pxSendDateTime property on the pxCorrSummary work page that belongs to pyWorkPage. In previous versions of Pega Platform™, after sending correspondence, the update of the pxSendDateTime property could cause errors when working with an application at run time. To prevent such issues, Pega Platform now includes a pyEnableCorrSummary when rule that, by default, is set to false. If your business scenario requires updating the pxCorrSummary work page, set the when rule value to true.

For more information, see:

• Notifying participants about events
• Approval by email
• Sending automatic emails from cases

Support for picklists with parameterized data pages in App Studio in Cosmos React UI

You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.

For more information, see link Dropdown control Properties — General tab.