Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au

Skip to end of banner
Go to start of banner

TAP-902: Flows Optimization

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

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 none 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

Developer Name

Type

Description

USYD_Automate_task_for_GA_for_Pledge_subflow
Flow

auto-launched flow

USYD_AQC_Donor_Contact_Type_Auto_Updater_subflow
Flow

auto-launched flow

USYD_Gift_Pledge_On_Create_After_Save_subflow
Flow

auto-launched flow

USYD_Gift_Pledge_Update_subflow
Flow

auto-launched flow

USYD_Gift_Derivation_subflow
Flow

auto-launched flow

Gift_Main_Flow
Flow

record-triggered flow

USYD_GIN_Stage_based_Update_Before_Save_subflow
Flow

auto-launched flow

USYD_Usyd_Update_Gift_Implementation_Status_subflow
Flow

auto-launched flow

Gift_Implementation_Main_Flow
Flow

record-triggered flow

USYD_Populate_Chart_of_Accounts_in_Transaction_subflow
Flow

auto-launched flow

USYD_Transaction_Roll_up_to_Gift_Pledge_fields_subflow
Flow

auto-launched flow

USYD_Campaign_member_status_update_when_new_transaction_created_subflow
Flow

auto-launched flow

USYD_Pledge_is_Due_To_Be_Paid_Out_subflow
Flow

auto-launched flow

USYD_Description_HOLD_RECEIPT_subflow
Flow

auto-launched flow

USYD_Transaction_Update_subflow
Flow

auto-launched flow

Transaction_Main_Flow
Flow

record-triggered flow

CUSTOM_NOTIFICATION_TYPE_ID_SYDNEY_STANDARD_NOTIFICATION
CustomLabel

custom label

Automate_task_for_GA_for_Pledge
PB

process builder

USYD_Populate_Chart_of_Accounts_in_Transaction
PB

process builder

Usyd_Transaction_surface_up_Pledge_WO_Notation_to_Gift
PB

process builder

pledge_is_due_to_paid_out
PB

process builder

Description_HOLD_RECEIPT
PB

process builder

AQC_Donor_Contact_Type_Auto_Updater
Flow

record-triggered flow

Gift_Pledge_On_Create_After_Save
Flow

record-triggered flow

USYD_Gift_Pledge_Update
Flow

record-triggered flow

Usyd_Gift_Driver_Derivation
Flow

record-triggered flow

GIN_Stage_based_Update_Before_Save
Flow

record-triggered flow

Usyd_Update_Gift_Implementation_Status
Flow

record-triggered flow

Usyd_Campaign_member_status_update_when_new_transaction_created
Flow

record-triggered flow

USYD_Transaction_Update
Flow

record-triggered flow

  • No labels