TAP-902: MS Team - To check the logic and any bad code practice for the list of flows mentioned and merge if required

Description:

Persona + Need + Purpose

As a System admin

I want to make sure there are no issues with existing flows

So that Batch processing gift/pledge creation & updates/transactions run smoothly without CPU limit errors or SOQL 201 errors.

Batch closing is one of the scenario that created the gift/pledge and transactions at the backend and there are lot of process builders and flows that are being called

Business Area:

Batch Processing/GA

Business Value:

Best code practice

Implementation:

To avoid hitting governor limits on a single synchronous transaction(DML limit of 150, SOQL limit of 200) and avoid the unwanted recursion of flow calls because of roll-up summary fields not related to the flows’s logic, the team has implemented the following:

• A parent flow is created for each triggering sObject.

  • Gift

  • Gift Implementation

  • Transaction

• Flows are then translated to sub-flows. This is created with considerations to the original Flow Trigger order of each object.

• Roll-up summary fields changes on Gift object is filtered to avoid recurring run of subflows triggered on Gift sObject.

Metadata Components and Changes:

* Items in red are deactivated