Nonprofit Coordinate Gift Commitment Processing Flow (CnGiftCmtProcessing) Changes

Prior to Summer '26 (Legacy Flow Behavior)

The original CnGiftCmtProcessing Flow invoked three separate legacy batch job definitions in sequence:

1. UpdateCmtmtOnNxtTxn

2. UpdateCmtmtOnSchChange

3. UpdateCmtmtOnTxnStatus

These three jobs run serially only. Even if NextGen Commitment Processing is enabled in the org, the original Flow does not take advantage of parallel processing. Customers who are already running the original scheduled Flow on or after the Summer '26 release will continue to use this serial execution path with no performance benefit from parallelization.

Summer '26 (New Flow Behavior)

The updated CnGiftCmtProcessing Flow shipped in Summer '26 replaces the three legacy batch job invocations with a single call to the new NextGen Commitment Batch Processing job (frops_flow__NextGenCmtBatchProc). This new job supports parallel execution as described earlier in this document.

Important: To take advantage of parallel processing, organizations must clone and schedule the new version of the Coordinate Gift Commitment Processing Flow. The existing scheduled CnGiftCmtProcessing flow that was cloned and scheduled prior to Summer '26 will continue to run using the legacy serial batch jobs and will not automatically gain the performance improvements of NextGen processing.