Content Comparison

Processes/Sub-flows

• USYD Automate task for GA for Pledge (subflow)

• USYD AQC Donor Contact Type Auto-Updater (subflow)

• USYD Update Related Gift Implementation

• USYD _ Updates _ pledge _ status _ if _ gift_/pledge _ recordtype _ is _ Pledge _ and _ Pledge _ Status is Active or Paid (subflow)

• USYD Update Credited Contacts and GRC Rollup (subflow)

• USYD Update Text Area Description (subflow)

• USYD Pledge is due to be Paid Out (subflow)

...

Anchor
USYD-Automate-task-for-GA-for-Pledge-(subflow) USYD-Automate-task-for-GA-for-Pledge-(subflow)

USYD Automate task for GA for Pledge (subflow)

...

• Found that changes will be made even if change on field is not exactly changed.

Fix/Change:

Specific testing on this flow’s added criteria to check if Usyd_Gift_Driver_Derivation__c = false can only be done through debug of the flow as this is set to false when flow execution gets to USYD Gift Driver Derivation (subflow).

Unit testing:

1. Open a gift record and set Usyd_Gift_Driver_Derivation__c to false through anonymous apex.

...

1. Open a GIft Implementation record and make sure Stage is not 5. GI - Kick Off and Gift Pledge field is NOT populated with a GIft record.

2. Navigate to the related Opportunity record and open any of its related Gift record.

3. Do an update on the Gift record on any fields and save.

4. Check the Gift Implementation record that the Stage is updated to 5. GI - Kick Off and Gift/Pledge field is populated.

   

...

Anchor
USYD-Update-Pledge-Status-(subflow) USYD-Update-Pledge-Status-(subflow)

USYD

...

Updates

...

pledge

...

status

...

if

...

gift

...

/pledge

...

recordtype

...

is

...

Pledge

...

and

...

Pledge

...

Status is Active or Paid (subflow)

Background of issue:

• Logic is in a containing flow and must be subdivided for a more clear view of its function.

...

Gift >: Gift Type is Pledge OR
Gift > Recordtype       Record Type is Pledge or Matching Gift
Gift >: Balance Due is 0
Gift >: Payments is greater than 0
Gift >: Pledge Status is Active
Gift >: Recurring Gift Link is null 

Gift >: Gift Type is Pledge OR 
      Gift >Record RecordtypeType is Pledge or Matching Gift
Gift >: Balance Due is 0
Gift >: Payments is greater than 0
Gift >: Pledge Status is Active
Gift >: Recurring Gift Link is notNOT null
Gift >: Recurring Gift >Link Date Ended is not null
Gift > Recurring Gift > Date Ended is lessNOT that or equal to current date

null, Current/Past Date

Gift >: Gift Type is Pledge OR Gift > Recordtype
       Record Type is Pledge or Matching Gift
Gift >: Balance Due is 0
Gift >: Payments is greater than 0
Gift >: Pledge Status is Active
Gift >: Recurring Gift Link is notNOT null
Gift >: Recurring Gift > Date Ended is null
Gift > Recurring Gift > Link Type is Continuity Pledge with End Date

Gift : >Gift Type is Pledge OR
 Gift > Recordtype      Record Type is Pledge or Matching Gift
Gift >: Balance Due is greater than 0
Gift >: Pledge Status is Paid

Gift >: Gift Type is Pledge OR
Gift > Recordtype       Record Type is Pledge or Matching Gift
Gift >: Balance Due is greater than 0
Gift >: Pledge Status is null

...

1. Open an existing Gift record and update its Description field.

   

2. Check to see that Text Area Description field is updated(field may not be on page layout).

   

...

USYD Pledge is due to be Paid out (subflow)

Background of issue:

• Re-implemented as a subflow.

Fix/Change:

• Translated in its own flow(subflow).

Unit testing - Organization/Corporation Account recordtype:

1. Create a Pledge from Smart Batch for an Organization/Corporation Account

2. Set single payment due date 90 days from Today.

3. Pledge transaction should be linked to an opportunity.

4. After Closing the batch, expect a single notification for the Transaction created.

Unit testing - Household Account recordtype:

1. Create a Pledge from Smart Batch for an Organization/Corporation Account

2. Set single payment due date 90 days from Today.

3. After Closing the batch, expect a single notification for the Transaction created.