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

Avengers Flows

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

« Previous Version 10 Next »

[TAPSS-60] MS team - Review Flows for Avengers Tickets


[TAPSS-1084] AVE-147 - Ensure Legal Credit Percentage on new Contact

Flow: USYD Update Legal & Gift Recognition Credit Percentage

Recommendation/s:

  1. Get Records: Get Account Type Id For Current Records Account can be removed; it retrieves the Id of Account Record Type: Household, and this checking can be done in Decision: Check Related Account Type.

    1. remove Get Records: Get Account Type Id For Current Records Account

    2. remove Variable: HouseholdAccountRecordTypeId
      note: why was this variable set available as input and output? This is a Record-Triggered Flow, and cannot be referenced as a sub flow in a master flow.

  2. Update condition in Decision: Check Related Account Type to directly reference the Related Account record’s Record Type, i.e.,

    $Record > Account ID > Record Type ID > Record Type Name = Household

Review by Yeng:

  • Rename Flow API Name to USYD_UpdateLegalAndGiftRecognitionCredit

Flow Label

Flow API Name

old

USYD Update Legal & Gift Recognition Credit Percentage

USYD_Update_Legal_Gift_Recognition_Credit_Percentage

new

USYD Update Legal & Gift Recognition Credit Percentage

USYD Update Legal and Gift Recognition Credit

USYD_UpdateLegalAndGiftRecognitionCredit

  • Add description

This Flow updates Contact fields: Legal Credit % and Gift Recognition Credit %


[TAPSS-1125] AVE-254 - Replicate AQ Address Synching for RTS reason field

Flow: Usyd_SyncRTSFromContToAccount**

Recommendation/s: none

Review by Yeng:

  • Rename Flow API Name to USYD_SyncContactToAccountRTSReason

Flow Label

Flow API Name

old

Usyd_SyncRTSFromContToAccount

Usyd_SyncRTSFromContToAccount

new

Usyd_SyncRTSFromContToAccount

USYD_SyncContactToAccountRTSReason

Flow: Usyd_SyncRTSReasonFromAccToContact**

Recommendation/s: none

Review by Yeng:

  • Rename Flow API Name to USYD_SyncAccountToContactRTSReason

Flow Label

Flow API Name

old

Usyd_SyncRTSReasonFromAccToContact

Usyd_SyncRTSReasonFromAccToContact

new

Usyd_SyncRTSReasonFromAccToContact

USYD_SyncAccountToContactRTSReason


** - checked in Avengers sandbox, not found in SIT


[TAP-1635] AVE-258 - Summary Fields about a Contact's Campaigns engagement

Flow: USYD Campaign Summary Fields**

Recommendation/s: none

Review by Yeng:

  • Rename Flow API Name to USYD_SummariseContactCampaignInteraction

Flow Label

Flow API Name

old

USYD Campaign Summary Fields

USYD_Campaign_Summary_Fields

new

USYD Campaign Summary Fields
USYD Summarise Contact Campaign Interaction

USYD_SummariseContactCampaignInteraction


** - checked in Avengers sandbox, not found in SIT


[TAPSS-1126] AVE-284 - Change Flows for when a contact is added to Influential Campaign that creates alert on Contact

Flow: Usyd_UncheckInfluentialFieldContact

Recommendation/s:

  1. In Update Records: Update Influential Field On Contact, filter can be updated to consider checking the current value of the field that will be updated (Is Influential Alumni)

Review by Yeng:

  • Rename Flow API Name to USYD_UntickInfluentialFieldOnContact

Flow Label

Flow API Name

old

Usyd_UncheckInfluentialFieldContact

Usyd_UncheckInfluentialFieldContact

new

Usyd_UncheckInfluentialFieldContact

USYD_UntickInfluentialFieldOnContact

Flow: Usyd_UpdateInfluentialFieldonContact

Recommendation/s:

  1. In Update Records: Update Influential Field On Contact, filter can be updated to consider checking the current value of the field that will be updated (Is Influential Alumni)

Review by Yeng:

  1. Remove the creation of an alert in the Account, this is not necessary

    1. Create Records: CreateAlertonAccount

  2. Instead, add WithAccount = true in the CreateAlertOnContact. This way, the alert will also display on the Account page

    1. Create Records: CreateAlertOnContact

  3. Rename Flow API Name to USYD_TickInfluentialFieldOnContact

Flow Label

Flow API Name

old

Usyd_UpdateInfluentialFieldonContact

Usyd_UpdateInfluentialFieldonContact

new

Usyd_UpdateInfluentialFieldonContact

USYD_TickInfluentialFieldOnContact

  • No labels