Published Release Notes

Emit remaining event strategy data at the end of a data flow run

Data flows have been updated to prevent data loss in event strategies. By default, when a batch or a real-time data flow stops and it contains an event strategy with Tumbling windows, all of the events that are in the Tumbling windows are emitted. Event emission triggers further processing in the event strategy, like aggregations and joins.

For more information, see Enhancements to data flows that contain event strategies and Event Strategy rule form - Completing the Event Strategy tab.

Like and bookmark Pulse messages

You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.

For information about Pulse enhancements, see:

• Pega Express 7.3.1 – Communicating with Pulse
• Pega Platform 7.3.1 – Pulse enhancements for social collaboration

Attach Content control enhancements

You can now use the Attach Content control in Pega^® Platform to configure compression options that limit the size of files created on a mobile device. For example, you can choose from predefined settings to limit video duration or image size. These settings apply when the user records a new video or takes a new photo, but they do not apply to prerecorded media.

Also, when attaching content to a custom mobile app, users can now select any type of file from any source that is available in the device's native file picker component.

For more information, see Configuring file size options for the Attach content control.

Real-time updates in Pulse

You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.

For information about Pulse enhancements, see:

• Pega Express 7.3.1 – Communicating with Pulse
• Pega Platform 7.3.1 – Pulse enhancements for social collaboration

Ability to map JSON to clipboard properties by using a data transform

You can now map the entire JSON file or individual properties to and from the clipboard by using a data transform. Using a data transform makes it faster and easier to connect your Pega^® Platform to your system of record.

For more information, see Data transforms.

Customize themes for your application

You can now customize themes for your application by selecting the background, border, button and text colors; border width; and text font and size. You can further customize themes by using Cascading Style Sheets (CSS).

For more information, see Customization of themes.

New aggregation functions in event strategies

You can use new functions in event strategies to build standard and complex aggregations. With new aggregation functions you can detect additional patterns in streams of data and deliver actionable insights.

For more information, see Adding aggregations in event strategies.

Pega Cloud Services support for the AWS EU (London) and US East (Ohio) regions

Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) EU (London) and US East (Ohio) regions. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.

For more information about regions and availability zones, see Pega Cloud Services capabilities.

.

These additional regions are available as of QIV 2017.

Legacy landing pages removed

The following legacy landing pages and their links in the Designer Studio menu have been removed:

• Designer Studio > Data Model > Clipboard Pages > Data Pages
• Designer Studio > Data Model > Clipboard Pages > Undefined Pages
• Designer Studio > Data Model > Classes & Properties > Class Relationships

The streamlined Designer Studio menu facilitates locating and navigating to landing pages.

For information about the replacements for these landing pages, see Deprecated features.

Service REST monitoring

You can now monitor response and request data for REST services and view the results in Pega^® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.

For more information, see Service REST monitoring.