Roll-up Summary Field Processing
Pulsar has the ability to calculate roll-up summary fields while offline.
You will need to have a minimum release of 2.3.x of the PulsarSettings AppExchange package.
Pulsar Settings Configuration
Follow the pre-processing steps on the Pulsar Settings Manager tab.
Create a Pulsar Setting with key
pulsar.rollup.enableRollUpSummaryFields
and value set toTRUE
Due to processing constraints in mobile offline environments, by default Pulsar will perform roll-up calculations for 2 parent (master) generations. In other words, if a child record is Created/Updated/Deleted, then roll-up summaries are recalculated for the immediate parent (master) records and the grandparent (master master) records. If you wish to change this limit, create a Pulsar Setting with key
pulsar.rollup.rollupParentLimit
and value set to an integer number > 0.Â
Warning: Setting this to a large integer may significantly impact performance of Pulsar mobile app when saving records!
Limitations of offline Roll-up Summary Field processing
Validation rules on master objects are not triggered when performing roll-up calculations.
There is no way to perform a mass recalculation of roll-up summary values in Pulsar. Despite this, Pulsar will pick up new values from a mass recalculation initiated on SFDC servers during the next catch-up sync.