...
Provided with your Posi Ed package are unmanaged automations on the Contact/Person account and the student record objects which use the Posi Ed state State settings, define how data will be transferred up or down the latter.
For example, if you wish to populate Posi Ed using student contact data from EdVal, you would set the Posi Ed state State to Subscriber and then use the Publish Students LIASS LISS API call to populate the student record Student Record object with student data. The automations on the student record Student Record object will then create and/or update contact Contact records for each of these students.
Alternatively, if Posi Ed is the master source of data and you wish to push data to an external application, then set the Posi Ed state State to Publisher. In this case any relevant changes of data on the Contact record e.g. updating a name, phone number or email will be pushed by an automation to the Student recordRecord. From here they will be picked up by the LISS Get Students API call.
...
You may need to modify the translation of year level values if there is a discrepancy between the external system and Posi Ed. For example one system may say Grade 7 and the other might say Year 7. This is generally handled through a field on the Grade Level sequence Sequence object (this object has not been included in the package and we may use a different approach – this doco may need to be updated). Or it might require a manual translation through these automations
Here is some information on the automations:
...
https://alphasys.atlassian.net/browse/E2-830
...
:
...