Skip to main content

 –

Aggregation on the Visual Business Director data set

Suggest edit Updated on March 11, 2021

Aggregation is an internal feature in the Visual Business Director (VBD) data set to reduce the number of records that the VBD data set needs to store on its partitions. The size of a partition is determined by the time granularity setting that you select when you create a VBD data set instance. When you save the rule instance, you cannot change this setting.

Aggregation happens automatically for each VBD data set when a new partition is allocated in the VBD data set instance and at midnight. Records in older partitions that have not been aggregated, are aggregated.

Note: Aggregation causes the loss of record-level details such as time stamp because all records in the same partition get the time stamp of the first record in the partition.

Example of how aggregation works

A data flow inserts five records into an empty VBD data set. Three records are identical.

ChannelIssueGroupOutcome
C1I1G1Accepted
C1I1G1Accepted
C1I1G1Accepted
C2I1G1Accepted
C1I1G1Rejected

When the records are inserted, they have not been aggregated yet. The number of records is displayed in the # Records column. After the aggregation is started automatically or you click Aggregate in the Data Sources tab, identical records are reduced to one record but their number is tracked.

ChannelIssueGroupOutcomeCount
C1I1G1Accepted3
C2I1G1Accepted1
C1I1G1Rejected1

As a result, five records in the VBD data set were reduced to three by adding an internal Count field to them, and using it to tally records with identical field values. The same happens with subsequent aggregations.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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