Employee Role - User/Account/Contact Record Automations
...
By default Posi Ed provides automation to support the latter and these automations use similar rules to the student record/account automations. Please refer to the appropriate section.
- Insert MDoms documentation on these automations
following:
- https://posimente.atlassian.net/wiki/spaces/~641d437d407493675d47acc3/pages/29786202/Flows+-+PosiEd#Automations-to-populate-Staff-from-Employee-Role-Record-and-vice-versa
- https://posimente.atlassian.net/wiki/spaces/~641d437d407493675d47acc3/pages/29786202/Flows+-+PosiEd#Automation-when-Person-Account-is-Updated-(unmanaged)
Note that these automations have been provided as unmanaged code to allow the client to customise and meet their own requirements. For example, your school might have different standards with regards to fields such as third name, nickname and legal name etc. Posi Ed allows you to define these fields for yourself on the contact/account objects and extend the automations to ensure they are populated to and from the student record as required.