Versions Compared

Old Version 5

changes.mady.by.user Angela Jann

Saved on

compared with

New Version 6

changes.mady.by.user Angela Jann

Saved on

Key

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

Managed Flows

Flow Name

Object

Automation

Trigger Condition

DML

Cohort: Create a Record-Triggered Flow

Cohort Automation Update

Cohort

Record Triggered flow

(before create/update)

  • If Subject Offering != null AND

  • If Timetable Structure = null

  • If Timetable Term = null

  • If Department = null

  • If Primary Grade Level = null

  • If Cohort Type = null

  • If Mark Roll = null

  • If Description = null

  • If Timetable != null AND

  • If Start Date = null

  • If End Date = null

  • If Cohort Number = null

  • If Primary Location = null

  • If Primary Staff Member = null

  • If Cohort Size = null

  • If Capactity = null

  • Timetable Structure = Subject Offering’s Timetable Structure

  • Timetable Term = Subject Offering’s Timetable Term

  • Department = Subject Offering’s Department

  • Primary Grade Level = Subject Offering’s Grade Levels (take 1st value of multipicklist)

  • Cohort Type = Subject Offering’s Subject Type

  • Mark Roll = Subject Offering’s Mark Roll

  • Description = Subject Offering’s Description else Name

  • Start Date = Timetable’s Start Date

  • End Date = Timetable’s End Date

  • Cohort Number = number or value at the end of the Cohort Name

  • Primary Location =  child Cohort Schedule > Primary Location (first value found)

  • Primary Staff = child Cohort Schedule > Primary Staff Member (first value found)

  • Cohort Size = count of the Cohort Member records that have a Record Type of Students and a Status of Current.

  • Capacity = Primary Location’s Capacity

Cohort Member: Create a Record-Triggered Flow

Cohort Member

Record Triggered flow

(before create/update)

  • If Start Date = null

  • If End Date = null

  • Start Date = Cohort’s Start Date

  • End Date = Cohort’s End Date

Cohort Schedule: Create a record-triggered Flow

Cohort Schedule Automation Update (Bell Time)

Cohort Schedule

Record Triggered flow

(before create/update)

  • If Bell Time != null AND

  • If Start Time = null

  • If End Time = null

  • If Start Date = null

  • If End Date = null

  • Start Time = Bell Time’s Start Time

  • End Time = Bell Time’s End Time

  • Start Date = Cohort’s Start Date

  • End Date = Cohort’s End Date

  • Day = Bell Time’s Day

  • Week = Bell Time’s Week

  • Period = Bell Time’s Period

Cohort Schedule Connection - Start Time and End Time Defaults

Cohort Schedule Connection

Record Triggered flow (after insert/update)

  • If Start Time = null

  • If End Time = null

  • Start Time = Cohort Schedule’s Start Time

  • End Time = Cohort Schedule’s End Time

Cohort Schedule Connection

Cohort Schedule Connection

Record Triggered flow (before create/update)

  • If Start Date = null

  • If End Date = null

  • Start Date= Cohort Schedule’s Start Date

  • End Date = Cohort Schedule’s End Date

Subject Offering: Create a record-triggered flow

Subject Offering Update

Subject Offering

Record Triggered flow

(before create/update)

  • If Subject != null AND

  • If Department = null

  • If Educational Institution = null

  • If Grade Levels = null

  • If Mark Roll = null

  • If Description = null

  • If Timetable Structure != null

  • Department = Subject’s Department

  • Educational Institution = Subject’s Educational Institution

  • Grade Levels = Subject’s Grade Levels

  • Mark Roll = Subject’s Mark Roll

  • Description = Subject’s Description, else Subject Offering Name

  • If true, Name = (Subject) Subject Id + (Timetable Structure) Academic Year

    • example: 08MAT 2023

  • If false, Name =(Subject) Subject Id

Unmanaged Flows

Tickethttps://alphasys.atlassian.net/browse/E2-222
https://alphasys.atlassian.net/browse/E2-1304

Flow Name

Object

Automation

Trigger Condition

DML

Create/Update Student Records Automation

Student Record

Record Triggered flow

(before create/update)

If Student Record is created

If Student Record is updated

  • Contact is created where

    • First Name = Student Record’s First Name

    • Last Name = Student Record’s Last Name 

    • Phone = Student Record’s Phone

    • Preferred Name = Student Record’s Preferred Name 

    • Gender = PosiEd Value (based on PosiEd Value Mapping custom setting)

    • Email = Student Record’s Email 

  • Student Record is linked to the new Contact.

  • If has Contact,

    • Contact is updated with same values as above.

  • If has no Contact,

    • Contact is created with same values as above.

  • Student Record is linked to the new Contact.

Update Contact Automation

https://alphasys.atlassian.net/browse/E2-223

Contact

Record Triggered flow

(before update)

If Contact is updated

  • Update the all related Student Records

    • First Name = Contact’s First Name

    • Last Name = Contact’s Last Name 

    • Phone = Contact’s Phone

    • Preferred Name = Contact’s Preferred Name 

    • Gender = PosiEd Value (based on PosiEd Value Mapping custom setting)

    • Email = Contact’s Email

Automations to populate Staff from Employee Role Record and vice versa

https://alphasys.atlassian.net/browse/E2-113

Employee Role

Record Triggered flow

(before create/before update)

If Employee Role is created

If Employee Role is updated

Automation when Person Account is Updated (unmanaged)

Account (Person Account)

Record Triggered flow

If Account (Person Account) is updated