Configure the window size at run time in event strategies
Valid from Pega Version 7.4
You can now configure an Event Strategy rule to dynamically define the window size at run time by using a property value of the incoming record. To configure the window shape for dynamic size setting, you can use any property from the inheritance path that is available to the event strategy. This enhancement provides greater flexibility for strategy designers and broadens the scope of business scenarios in which event strategies can be applied.
For more information, see Event Strategy rule form - Completing the Event Strategy tab and Dynamic window size behavior.
Node classification replaces NodeID-based configuration
Valid from Pega Version 7.4
For simpler cluster administration and better application resiliency, Pega® Platform is moving toward a node classification model. Although agents will continue to work by using NodeIDs for several upcoming releases, use node types instead of NodeID configuration for agents, listeners, and decisioning services for more efficient operations and upgrades.
For more information, see Node classification.
Aggregate data in interaction history summaries
Valid from Pega Version 7.4
You can now group, aggregate, and filter interaction history data in a single strategy component. By using interaction history summaries, you can create refined data sets that simplify strategy frameworks and accelerate decision-making. Aggregated data sets are easier to process, manage, and troubleshoot.
For more information, see Data Sources landing page
New shape on the strategy canvas
Valid from Pega Version 7.4
The Strategy rule has been enhanced with the Embedded strategy shape, which simplifies the configuration of decisioning strategies that simultaneously apply to multiple types of audiences, for example, Devices, Households, and Subscribers. The Embedded strategy shape eliminates the need to switch between various classes to create a substrategy for each audience type that you want to target. Now, you can perform all configuration tasks on a single strategy canvas.
For more information, see Strategy components – Embedded strategy and Multilevel decisioning strategies.
New interaction history attribute
Valid from Pega Version 7.4
Pega® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:
- Single-level decisioning frameworks that use interaction history.
- Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.
For the single-level scenario, configure the Dynamic System Setting that sets the pySubjectType attribute when your framework reads interaction history records. The value of this Dynamic System Setting becomes the name of the customer class.
For the multi-level scenario, update the database table for all strategy levels manually. For each level, make sure that the value in the Subject Type column is set to the name of the class for the corresponding strategy. For example, the value for the top level strategy should be set to the name of the class of that strategy.
For more information about interaction history aggregations, see Data Sources landing page
For more information about multi-line strategies and contexts, see Strategy components - Embedded strategy
HBase data set type becomes resumable
Valid from Pega Version 7.4
HBase data set has been enhanced to be resumable. As a result, data flow runs that reference the HBase data set as their primary data source are now resumable. You can pause and resume such data flow runs.
For more information, see the Resumability of data flow runs section in Data flow run updates.
Pega Cloud Services File Storage service
Pega Cloud Services introduces Pega Cloud Services File Storage, a service that is fully integrated with the Pega Platform to support your Pega applications. New subscriptions and upgrades to the latest Pega Platform version make this the default storage repository.
For more information see Pega Cloud Services File Storage.
Pega Cloud Services introduced this new service as of QI 2018.
Support for Java 8
REST APIs added for management of agents and requestors
Valid from Pega Version 8.1
You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.
For more information, see Pega API for Pega Platform and Pega API.
Security fields in JFrog Artifactory repository do not work
Valid from Pega Version 7.3
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not implemented. In the Pega™ Platform 7.3 Designer Studio help, disregard the optional Security section in step 4 of the Configuring a JFrog Artifactory or Amazon S3 repository connection help topic, and disregard the optional Security section in step 5 of the Creating a repository configuration help topic in the 7.3.1 Designer Studio help.