Real-time event processing
Valid from Pega Version 7.1.9
Real-time event processing is a mechanism that can be used to analyze a high velocity stream of events entering the system and derive conclusions from them. It is possible to define metrics, measurements, and conditions under which subsequent trigger events are generated.
For details, see Real-time event processing.
New form of the HBase rule
Valid from Pega Version 7.1.8
There is a new form of the HBase rule. While you cannot create any new instances of the Pega 7.1.7 HBase rule, legacy instances in your application remain functional. You can still use the Pega 7.1.7 instances of the HBase rule, but you cannot make changes to them.
New data sets
Valid from Pega Version 7.1.8
There are three new types of data sets:
- HDFS Data Set, which reads and saves data from external, distributed Apache Hadoop file systems.
- HBase Data Set, which supports HBase storage.
- Stream Data Set, which processes the continuous data stream of events.
Real-time processing of data flows
Valid from Pega Version 7.1.8
It is possible to run, manage, and monitor data flows that use stream as their data source. You can create a new run from the Real-time processing landing page.
Decision Data Store data sets can be used only on DNodes
Valid from Pega Version 7.1.8
Data flows that contain Decision Data Store data sets as the primary or secondary source must be created and executed only on DNodes.
Data flows are not restarted automatically after application server restart
Valid from Pega Version 7.1.8
When you restart the application server or the Pega 7 server, you stop the execution of your data flows. The interrupted batch and real-time runs are marked as Failed.
Recommendation:
- Go to the > > > > tab and start the failed batch runs.
Go to the
> > > > tab and activate the failed real-time runs.
Value list and value group properties are not supported inside data flows
Valid from Pega Version 7.1.8
Value list and value group properties are not supported inside data flows, and you need to instead use other property types.
See the Pega 7 developer help to check all available property types.
Data flow preview size is fixed to 10
Valid from Pega Version 7.1.8
The Preview option for each shape in data flows returns the first 10 records. This value is fixed and currently cannot be changed.
Data Flow transformation shapes cannot be used in combination with the Compose or Merge shapes
Valid from Pega Version 7.1.8
When you reference another data flow from a data flow that contains the Compose or shape, the referenced data flow cannot contain transformation shapes ( , , ).
Data flow validation does not currently prevent you from designing a data flow that goes against this design pattern. Make sure that your data flows follow this design pattern by checking the referenced and referencing data flows.
Data flow destination is resolved at assembly time
Valid from Pega Version 7.1.8
Data flow execution always uses the design-time destination data sets or destination data flows, regardless of the input records at run time.
Example:
You create a data flow and set the destination to a specific data set. In the data flow, you use a strategy that produces some results. Regardless of these results, the execution of your data flow always uses the destination data set that you specified when you designed the data flow.
The same applies when you set the destination to a data flow.