Event-Based Trigger Integration
Event-driven integration enables near real-time synchronization between your PeopleSoft Campus Solutions systems and the external system. For example, if a student successfully enrolls in a course in PeopleSoft Student Administration, and a corresponding course site exists in your external system, that student is added in near real time as a valid participant in the course site.
Event-based triggers are embedded within PeopleSoft Campus Solutions where key enterprise data (groups, persons, courses, and enrollments) can be created, updated, or deleted. The PeopleSoft Campus Solutions system publishes data object messages as events occur that change the relevant data. A subscription handler invokes the appropriate external system web service. The target system receives the messages and processes the event transactions.
The existence of an event-driven interface does not eliminate the need for the snapshot interface. Changes to hierarchical structure—such as the addition of a new term or new session—will bring the courses or classes from the new term into scope if you have included them in scope. However, a snapshot is required to initiate integration of the new courses and their sections. The new courses and class sections that are associated with the newly scoped term or session are not transmitted through the event-driven interface. The enrollments and other changes as noted below will be transmitted through events after the snapshot has been completed. Further, an event-driven interface is not tolerant of missed transactions; you may want to use the snapshot interface at regular intervals to resynchronize the data in the target system with that of your PeopleSoft Campus Solutions system. You can use the SAIP Event Message Monitor to track and monitor errors that might occur as part of the SAIP event-based integration.
Note: Running the event-driven model is not required. If you choose not to engage event-driven integration, you can use full and incremental snapshots to keep data synchronized. However, changes to data in the PeopleSoft Campus Solutions system will not be reflected in the external system until the next time the incremental snapshot is requested or run.
Embedded event-based triggers include, but may not be limited to, the following processes:
Foundational:
When an institution, term, or academic organization is removed from scope or details of those entities are modified.
Courses:
When a class section is scheduled or canceled.
When a class rollover process automatically schedules new term-based instances of course offerings.
When a meeting pattern for a class is changed.
Enrollments:
When a student adds, drops, or swaps a class.
When a student enrolls in a class, is withdrawn from a class, of removed from a waitlist.
When a student drops a class due to class cancellation.
When a student withdraws from all classes.
When an instructor is assigned to a class section.
Grades:
When an instructor imports final grades from an LMS or external source.
Persons:
When biographical or demographic data is updated for enrolled students and assigned instructors.
Warning! Changing the embedded triggers or creating new ones requires coding and may have significant negative administrative impact.
See SAIP Implementation Guide (Doc ID 1357846.1) in My Oracle Support.