Transaction Unit Testing

Processes/Subflows

• USYD Campaign member status update when new transaction created (subflow)

• USYD Transaction Update (Subflow)

USYD Campaign member status update when new transaction created (subflow)

Background of issue:

• Update Records elements can be merged into one

Unit testing:

1. When a Transaction record is created, all of the following conditions must be met:

   1. Transaction > Campaign Appeal is not null

   2. Transaction > Related to Void is false

   3. Transaction > Write Off? is false

   4. Transaction has a related Account

2. Related Account has a Primary Contact

   1. All Campaign Members related to the Primary Contact with Status not equal to ‘Donated’ will be updated:

      1. Start Date equals Transaction > Transaction Date

      2. Stop Date equals Transaction > Transaction Date

      3. Status equals 'Donated'

3. Related Account has a Secondary Contact

   1. All Campaign Members related to the Secondary Contact with Status not equal to ‘Donated’ will be updated:

      1. Start Date equals Transaction > Transaction Date

      2. Stop Date equals Transaction > Transaction Date

      3. Status equals 'Donated'

USYD Transaction Update (Subflow)

Background of issue:

• Re-implemented as a subflow, and added a field update as an Assignment element.

Unit testing:

1. When a Transaction record is created or updated, the following fields are updated (as flags):

   1. Send Pledge Reminder

   2. Funds Raised Flag Static

   3. Funds Received Flag Static

   4. Special Category Flag

   5. If Transaction > Originating Soft Credit Transaction is not null and Third Party Payoff equals true:

      1. Update Transaction > Third Party Pledge equals Transaction > Gift/Pledge Number