Understanding the 3C Engine
Important! Mass Change is a deprecated product. Support will be maintained for this product, but no new development will be produced for Mass Change. It is strongly recommended that you use Application Engine instead. For more information on PeopleSoft Application Engine, see PeopleTools: Application Engine.
The 3C engine is a rules-based PeopleSoft application engine that you can integrate with functional transactions to automatically insert or update communications, comments, and checklists records as you interact with students, suppliers, and employees. For example, you can eliminate steps required to manually enter 3C information by setting the 3C engine to automatically insert defined checklists, communications, and comments for prospects as you enter new admissions prospects to the system. You can use online business transactions to invoke 3C engine processing or you can use background integration with certain delivered programs.
Note: The PeopleSoft system delivers two background programs predefined and integrated with the 3C engine. PeopleSoft Contributor Relations Gift Acknowledgement process invokes the 3C engine to record results in the 3C engine trigger results table for background processing, and PeopleSoft user profiles management process invokes the 3C engine to record the real-time system communication inserts.
To use the 3C engine, you use administrative functions and detail data to define the rules (called engine events) to identify the sets of communication, checklists, and comments records that you want the engine to enter or update for you. Then, you can either set your own conditions (called triggers) to invoke the action of entering or updating the 3C records or you can use the predefined triggers delivered with your system. You can also use Population Selection, Triggers, Mass Change or any combination thereof to identify the IDs to process for an event.
If your institution licenses and uses PeopleSoft Campus Self Service, you can configure your system to record in real time, the checklists that you want self-service users to be able to view in the To Do's list self-service transaction. For example, when a prospective student logs onto your self-service site to request application information about your school, after saving the request, the system can record the checklist information that you specify in the engine event definition. When the prospective student logs in the next time, he or she can see the specific tasks that they must accomplish to complete your school's application process.