Versions Compared

Key

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

...

Update Contact Automation

Flow Name

Object

Automation

Trigger Condition

DML

Create/Update Student Records Automation

Student Record

Record Triggered flow

(before create/update)

If Educational Institution’s PosiEd State = Subscriber,

  • If Student Record is created

  • If Student Record is updated

  • Contact


If Educational Institution’s PosiEd State = Publisher,

  • If create,

    • A Person Account 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
      • Student Record’s Gender (using 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.

      • Id = Student Record’s Student Id

      • Student Status = Student Record’s Status

      • House = Student Record’s House

      • Current Grade Level = Student Record’s Current Grade Level

      • Primary Educational Institution = Student Record’s Educational Institution

    • Update the Student Record where

      • Current Grade Level = Student Record’s Form

      • Student = new Person Account’s Contact

      • Primary = true

  • If update,

    • If Student is empty,

      • Create a Person Account 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 = Student Record’s Gender (using PosiEd Value Mapping)

        • Email = Student Record’s Email

        • Student Id = Student Record’s Student Id

        • Student Status = Student Record’s Status

        • House = Student Record’s House

        • Current Grade Level = Student Record’s Current Grade Level

        • Primary Educational Institution = Student Record’s Educational Institution

      • Update the Student Record where

        • Current Grade Level = Student Record’s Form

        • Student = new Person Account’s Contact

        • Primary = true

    • If Student is populated and Primary = true,

      • Update the Student’s Person Account where

        • Student Id = Student Record’s Student Id

        • Student Status = Student Record’s Status

        • House = Student Record’s House

        • Current Grade Level = Student Record’s Current Grade Level

        • Primary Educational Institution = Student Record’s Educational Institution

      • Update the Student Record where

        • Current Grade Level = Student Record’s Form


  • Student Record’s Form = Student Record’s Current Grade Level

  • If Primary = true,

    • Person Account’s Current Grade Level = Student Record’s Current Grade Level

Update Contact Automation

Contact Automation Update (PosiEd State)

Contact

Record Triggered flow

(before update)

If Contact is updated

  • Update the all related Student Records where Educational Institution’s PosiEd State = Publisher where

    • 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

Employee Role

Record Triggered flow

(before create/before update)

If EducationalPosiEdState Educational Institution’s PosiEd State = Subscriber,

  1. If Employee Role is created

  2. If Employee Role is updated


If Educational Institution’s PosiEd State = Publisher,

  • Employee Role is updated where Employee is populated and Primary =true

  • If create,

    • A new User is created where

      • First Name = Employee Role’s First Name

      • Last Name = Employee Role’s Last Name

      • Phone = Employee Role’s Phone

      • Email = Employee Role’s Email

      • Alias = Employee Role’s Display Name

      • Username = Employee Role’s Email

      • Nickname = Employee Role’s Preferred Name

      • Title = Employee Role’s Salutation

      • User License = Chatter Free

      • Profile = Chatter Free User

    • Update Employee Role’s User = new User

    • A new Person Account is created where

      • First Name = Employee Role’s First Name

      • Last Name = Employee Role’s Last Name

      • Phone = Employee Role’s Phone

      • Preferred Name = Employee Role’s

      • Gender = Employee Role’s Gender (using PosiEd Value Mapping)

      • Email = Employee Role’s Email

      • Primary Educational Institution

      • Staff Status = Employee Role’s Status

      • Staff Id = Employee Role’s Staff Id

    • Update Employee Role’s Employee = new Person Account’s Contact

    • Update Employee Role’s Primary = True

  • If update,

    • If Employee Role’s User is populated and Primary = true,

      • User is updated where

        • First Name = Employee Role’s First Name

        • Last Name = Employee Role’s Last Name

        • Phone = Employee Role’s Phone

        • Email = Employee Role’s Email

        • Alias = Employee Role’s Display Name

        • Username = Employee Role’s Email

        • Nickname = Employee Role’s Preferred Name

        • Title = Employee Role’s Salutation

    • If Employee Role’s User is empty,

      • A new User is created where

        • First Name = Employee Role’s First Name

        • Last Name = Employee Role’s Last Name

        • Phone = Employee Role’s Phone

        • Email = Employee Role’s Email

        • Alias = Employee Role’s Display Name

        • Username = Employee Role’s Email

        • Nickname = Employee Role’s Preferred Name

        • Title = Employee Role’s Salutation

        • User License = Chatter Free

        • Profile = Chatter Free User

      • Update Employee Role’s User = new User

    • If Employee Role’s Employee field is populated and Primary = true,

      • Employee Role’s Person Account is updated where

        • Staff Id = Employee Role’s Staff ID

        • Staff Status = Employee Role’s Status

        • Primary Educational Institution = Employee Role’s Educational Institution


Based from Employee Role’s Employee, update Person account where

  • Staff Id = Employee Role’s Staff Id

  • Staff Status = Employee Role’s Staff Status

Automation when Person Account is Updated

Account (Person Account)

Record Triggered flow

If Account (Person Account) is updated

All related Employee Roles where Educational Institution’s PosiEd State = Publisher are updated where

  • First Name = Person Account’s First Name

  • Last Name = Person Account’s Last Name

  • Phone = Person Account’s Phone

  • Preferred Name = Person Account’s Preffered Name

  • Gender = Gender (using PosiEd Value Mapping)

  • Email = Person Account’s Email

  • Educational Institution = Primary Educational Institution