Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Persona + Need + Purpose

As a GA user

I want to update the batch logic by turning off the existing flow “Batch - On Update - After Save” and rewrite the logic as below:

...

So that I am alerted when I need to review a change to a batch

Acceptance Criteria

At Batch Item when Link to Opportunity is updated (Created/Update) and check if Batch Review status NE Ready for Review update GIN stage = GA- entry

...

[GIN stage of GI - Kickoff is now being managed by flow USYD Update Related Gift Implementation. See TAP-902 (Jira ticket, confluence page) ]

Business Area

GA

Business Value

Ability to track changes to batch for review

Table of Contents
minLevel1
maxLevel3
outlinefalse
styledecimal
typelist
printablefalse

Implementation:

COMPONENTS ADDED/MODIFIED

Label

API Name

Type

Type - Description

sObject

New/Update

Description/Change

Batch Item Pledge Payment changes Notify Gift Implementation

Batch_Item_Pledge_Payment_changes_Notify_Gift_Implementation

PB

process builder

Batch Item

Deactivated

translated to subflow(auto-launched flow), USYD_NotifyGiftImplementationGroup

Tax Amount Update from Total Amount Field

Tax_Amount_Update_from_Total_Amount_Field

PB

process builder

Batch Item

Deactivated

logic is now part of before save flow: USYD_BatchItemBeforeSave

Pledge Reminder Owner Auto-populate

Pledge_Reminder_Owner_Auto_populate

PB

process builder

Batch Item

Deactivated

translated to subflow(auto-launched flow), USYD_PopulatePledgeReminderOwner; logic about setting the Text Area Description is now part of before save flow: USYD_BatchItemBeforeSave

Usyd Update the Gift/Pledge number at Batch item task level when batch closed

Usyd_Update_the_Gift_Pledge_number_at_Batch_item_task_level_when_batch_closed

Flow

record-triggered flow

Batch Item

Deactivated

translated to subflow(auto-launched flow), USYD_UpdateBatchItemTasks

Batch On Update After Save

Batch_On_Update_After_Save

Flow

record-triggered flow

Batch

Deactivated

Translated to a subflow: Batch Update Related Gift Implementation, and referenced it in Batch After Save

Populate Pledge Reminder Owner

USYD_PopulatePledgeReminderOwner_subflow

Flow

auto-launched flow

Batch Item

New

translated from process builder; subflow of USYD_BatchItemAfterSave

Notify Gift Implementation Group

USYD_NotifyGiftImplementationGroup_subflow

Flow

auto-launched flow

Batch Item

New

translated from process builder; scheduled; subflow of USYD_BatchItemAfterSave

Update Batch Item Tasks

USYD_UpdateBatchItemTasks_subflow

Flow

auto-launched flow

Batch Item

New

translated from record-triggered flow; subflow of USYD_BatchItemAfterSave

Update Related Gift Implementation

USYD_UpdateRelatedGiftImplementation_subflow

Flow

auto-launched flow

Batch Item

New

subflow of USYD_BatchItemAfterSave

Batch Update Related Gift Implementation

USYD_BatchUpdateRelatedGiftImplementation_subflow

Flow

auto-launched flow

Batch

New

sublflow of USYD_BatchAfterSave

Batch Item After Save

USYD_BatchItemAfterSave

Flow

record-triggered flow

Batch Item

New

after save, parent flow, Main triggering after-save flow for Batch Item object.

Batch Item Before Save

USYD_BatchItemBeforeSave

Flow

record-triggered flow

Batch Item

New

before save; Caters fast-field updates for batch item object.

Batch After Save

USYD_BatchAfterSave

Flow

record-triggered flow

Batch

New

after save, parent flow, Main triggering after-save flow for Batch object

  1. Create a new flow Batch Item After Save.

    • record-triggered, when a record is created or updated; After Save.

    • Triggering object: Batch Item.

    • Create fault paths to document errors.

      • flow chart:

...

Batch Item After Save

...

A. Translate the following processes (process builders) to flows as subflows and reference them in Batch Item After Save:

...

  • Set a Scheduled Path: gets triggered 1 hour after creation of batch item.

...

Notify Gift Implementation Group

...

  • Set Entry Conditions. This restricts the subflow to only process batch item records with a record type of pledge write off.

...

i. new name: Populate Pledge Reminder Owner.

...

Populate Pledge Reminder Owner

...

  • Set Entry condition. This restricts the subflow to process only those batch item records with a pledge reminder owner field populated.

...

a. new name: Update Batch Item Tasks.

...

...

Update Batch Item Tasks

...

  • Set Entry Conditions. This restricts the subflow to only process batch item records with new/updated gift/pledge number, or signator, or campaign appeal.

...

  • Set values for Tasks and updateTasksCounter variables, which then get passed to the parent flow for field updates.

...

Update Related Gift Implementation

C. Create a new subflow Update Related Gift Implementation and have this referenced in Batch Item After Save.

...

  • Set Entry Condition. This restricts the subflow to only process batch item records with their Link to Opportunity updated. If Link to Opportunity is updated from blank to something, the Update GIN of Current Opportunity outcome gets satisfied. Else, e.g. Link to Opportunity is updated from one opportunity to another, the Update GIN of Current and Prior Opportunity outcome gets satisfied.

...

Update GIN of Current Opportunity outcome

...

  • Fetch all child GINs of Link to Opportunity.

...

  • Loop through all the fetched child GINs of Link to Opportunity.

...

  • Set the GIN Stage of on all fetched child GINs of Prior Link to Opportunity accordingly. Set GIN Stage to “3. GA-Entry” when Batch Review Status Not “Ready for Review”; Set to “4. GA-Approval” when Batch Review Status is Ready for Review. Update a toggle field in GIN object to signify that its the flow that will make the field update.

...

  • Set GINs and udpateGINCounter variables, which will then get passed to parent flow for field updates.

...

Update GIN of Current and Prior Opportunity outcome

...

  • Fetch the latest batch item record associated to Prior Link to Opportunity.

...

  • Set the GIN Stage on all fetched child GINs of Prior Link to Opportunity accordingly. Set GIN Stage to “3. GA-Entry” when Batch Review Status Not “Ready for Review”; Set to “4. GA-Approval” when Batch Review Status is Ready for Review. Update a toggle field in GIN object to signify that its the flow that will make the field update.

...

  • Flow to continue with the same process of the Update GIN of Current Opportunity outcome.

2. Optimize and translate flow Batch_On_Update_After_Save to a subflow Batch Update Related Gift Implementation and reference it in Batch After Save.

Batch After Save

...

Batch Update Related Gift Implementation

...

  • Set Entry Condition. This restricts the subflow to only process batch records when its Review Status is updated to another status.

...

  • Fetch child batch items of the triggering batch record.

...

  • Loop through all the child batch items of the batch record.

...

  • Set values for linkToOpportunityIds. This variable stores fetched Link to Opportunities for each of the child batch items.

...

  • Fetch the child GINs of captured Link to Opportunities.

...

  • Check if any child GINs are fetched.

...

  • Loop through all the fetched child GINs.

...

  • Set the GIN Stage of child GINs accordingly. Set GIN Stage to “3. GA-Entry” when Batch Review Status Not “Ready for Review”; Set to “4. GA-Approval” when Batch Review Status is Ready for Review. Update a toggle field in GIN object to signify that its the flow that will make the field update.

...

  • Set values for GINs and udpateGINCounter variables, which will then get passed to the parent flow for field updates.

...