Enhanced Penny Perfect Pricing V2 for Batch Runs

Considerations

To make sure data consistency and avoid processing errors, it isn't possible to modify pricing conditions, stage conditions, scale stage conditions, key types, or pricing templates during an active batch run.

Benefits of using the enhanced version of the Penny Perfect Pricing V2:

• Uses Bulk API instead of REST API to extract or integrate data faster.
• Reads the Last Successful Run datetime field from the Batch Last Successful Run object to identify the latest time the process ran successfully. If there are errors, the Last Successful Run datetime isn’t updated. The time in the Last Successful Run datetime field is used in delta mode execution to extract the latest changed conditions.
• Runs in full or delta mode. Full mode overwrites all conditions, and LastModifiedDate is updated even when the condition doesn’t change. The full mode can have an impact on sync performance. Delta mode updates the merged conditions only when the staged condition values are updated. This runs faster when compared with ‌full mode, as only a subset of conditions are considered.
  

  Note We recommend scheduling the batch in both full and delta mode executions. Schedule the batch in full mode once a week during initial integration or in exceptional cases (for example, cleanup) and in delta mode once a day (preferably at night so that the updated conditions are available to the field users during their morning sync). Specify the execution type by updating the Run Mode attribute from the Batch Process Configuration records for Penny Perfect Pricing V2 to “delta” or “full.” Batch Process Configuration is relevant only when you trigger the process by using the cgcloud.Scheduler class.
• Runs for all or single sales org. When the batch process runs for all sales organizations, the system creates one single batch run status record per sales org, and each sales org is run via an independent process, making it easier to read and understand Key Performance Indicators (KPIs) for the sales org.
• Enables soft deletion of pricing conditions. The JSON in the Content field is emptied. The process never hard deletes condition records. The process recreates the merged condition even when all stage conditions to be merged are deleted and don’t exist in Salesforce.