This chapter provides an overview of the 3C engine and discusses how to:
Define 3C engine events.
Define 3C engine triggers.
Set 3C engine security.
View 3C triggers results.
Run the 3C Engine process.
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 Enterprise 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 Enterprise 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.
See Also
Using Self-Service Checklists Data
This section discusses how to define 3C engine events and discusses how to:
Define 3C engine events.
Select joint rules compare fields.
View communication keys.
View comments.
View checklists.
Define 3C engine events to set rules by which the system identifies the sets of communications, checklists, and comments records for the 3C engine to enter or update.
Before using the 3C engine, you must set up communications, checklists, and comments. If you are going to use communication speed keys (Comm Keys), set those up first, too.
See Also
Defining Communication Speed Keys
Page Name |
Object Name |
Navigation |
Usage |
EVNT_3CS_SETUP |
Campus Community, 3C Engine, Set Up 3C Engine, Event Definition |
Define 3C engine events to identify or review the communications, comments, or checklists for the 3C engine to assign or update. |
|
EVNT_JRULES_AF |
Click the Variable Data Joint Rules link on the Engine Event Definition page. |
Select joint rules compare fields to identify variable data for the 3C engine to compare in determining and assigning joint communications. |
|
EVNT_3CS_COMM_SEC |
Click the Details link in the Communications area of the Engine Event Definition page. |
View Communication Keys to determine or modify data for the communication to assign. |
|
EVNT_3CS_CMNT_SEC |
Click the Details link in the Comments area of the Engine Event Definition page. |
View or modify the text of the comment to assign. |
|
EVNT_3CS_CHK_SEC |
Click the Details link in the Checklists area of the Engine Event Definition page. |
View or modify the parameters of the checklist to assign. |
Access the Engine Event Definition page.
Event Detail
Function |
Enter the functional area for this 3C engine event. |
User Selection |
Select this check box to enable users to select the communication, comment, and checklist to assign to transactions for this 3C engine event definition. When selected, the engine assigns only the communication, comment, and checklist specified by the user. For example, if you license and use the Request Information self-service transaction in PeopleSoft Enterprise Campus Self Service, you would select the User Selection option when defining a 3C engine event for the web prospects. That way, the prospects can select the communications that they want to receive. See Setting Up Recruiting and Admissions Self Service. When not selected, the engine assigns all communications, checklists, and comments identified in this 3C engine event. |
Variable Data Joint Rules |
Click this link to access the Joint Rules Compare Fields page, where you can select the variable data fields that you want the system to compare to determine and assign joint communications. |
Communications
Comm Key |
Enter the Comm Key to specify the communication to assign as part of this 3C engine event. |
Detail |
Click this link to access the Event Communication Detail page, where you can view or edit the details of the specified Comm Key. |
Comments
Comment Category |
Enter the comment category for the comment to assign as part of this 3C engine event. |
Detail |
Click this link to access the Event Comment Detail page, where you can view or edit the details of the specific comment category. |
Checklists
Checklist Code |
Enter the checklist code for the checklist to assign as part of this 3C engine event. |
Update Status |
Select this check box for the 3C engine to update each checklist item to the specified status. For example, you might include an item on the prospects checklist to require the assignment of a recruiter to each new prospect. You can create a 3C engine event definition to have the system automatically update that checklist item when you enter the new prospect into the database and assign the recruiter. |
Sequence |
The system automatically enters the next sequential number for each checklist item that you add. You can override the number manually to reorder the list of checklist items to be assigned as part of this 3C engine event. |
Item Code |
Enter the checklist item code for the checklist item to assign as part of this 3C engine event. Available item codes are from the Checklist Item Functions page. |
Responsible ID |
Enter the ID of the individual at your institution who is responsible for this checklist item. |
Item Status |
Select the status of the checklist items to assign as part of this 3C engine event. |
Due Days |
Enter the number of due days associated with the checklist items to assign as part of this 3C engine event. |
Due Date |
Enter the due date associated with the checklist item to assign as part of this 3C engine event. |
Comm Key |
The Comm Key of the checklist to be assigned as part of this 3C engine event. If the checklist to assign is of the default type that is set on the Installation Table - SA Options page (Communications List is the delivered default value), the system displays the Comm Key field. You can override this to select a different Comm Key. |
Access the Joint Rules Compare Fields page.
Compare Field |
If you use joint communications, select the data fields to compare for any two related IDs that are set on the Relationships page to enable joint communications. When the compare finds the same variable data in these fields for both IDs, the condition triggers the assignment of a joint communication for the primary ID. |
See Also
Understanding Joint Communications
Access the Comm Key Detail page.
Data on this page comes from the Communication Speed Key page. You can accept the default data or you can change it. Changing the data here modifies what the 3C engine assigns to individuals or organizations for the Comm Key that you specify. It does not change the data on the Communication Speed Key page.
For example, you might use a particular Comm Key to manually assign communications. You can also use that Comm Key on the 3C event definition, and if you want to make changes that affect only the individuals or organizations to whom the 3C engine assigns communications, you can. Perhaps you have a special condition that occurs and you want to include a special comment on the communication record for those recipients. When you add that comment here, only the communications assigned by this event definition will have that comment. The original Comm Key data remains unchanged.
Access the Comments Detail page.
You can enter a comment for the 3C engine to assign to all of the IDs processed by the engine event. Entering a comment here does not change any comments entered on the Comment Entry page for those IDs.
Access the Checklist Detail page.
You can use the default data or modify it. You can enter a comment for the 3C engine to assign to all of the IDs that will be assigned to this checklist by the engine event. Changing data and entering a comment here does not change data or any comments entered on the Checklist Management page for those IDs.
This section provides an overview of 3C engine triggers and discusses how to:
Map trigger prompts.
Identify trigger conditions.
Online triggers are conditions that you define to indicate when to invoke 3C engine processing. You can define triggers to occur in real time or to store in a trigger table for background processing later. Triggers are table specific. They identify record or field level conditions and associate the 3C engine event definition to use when the trigger conditions are met by creating, changing, or deleting data in the system.
The 3C engine online triggers are integrated with the system by using a PeopleCode function. The function evaluates certain key variable information provided in the PeopleCode placed in the transactional locations. You must define certain variable assignment values when you place this PeopleCode in other records or components. The following PeopleCode example identifies and describes these variables.
For example, the Trigger3CEngine function call placed on the ADM_APPL_DATA record in your system has these variable assignments.
Declare Function Trigger3CEngine PeopleCode FUNCLIB_CS.EVENT_3CS_ID FieldFormula; PanelGroup string &ID, &RECNAME, &ACTION, &OVERRIDE, &VAR_DATA, &INSTITUTION; &ID = "EMPLID"; &RECNAME = "ADM_APPL_DATA"; &ACTION = "N"; &OVERRIDE = "N"; &VAR_DATA = ?Y?; &INSTITUTION = ADM_APPL_DATA.INSTITUTION; Trigger3CEngine();
The PeopleSoft system delivers some predefined 3C engine PeopleCode function calls. You can use the EmplID (SavePostChange) field on these records:
ADM_APPL_DATA
ADM_APPL_PROG
ADM_PRSPCT_CAR
ADM_PRSPCT_PROG
ADM_WEB_PRS_CAR
You can configure your system to provide 3C engine integration in other areas by placing the PeopleCode function call in the appropriate records or components in these ways:
Place the Trigger3CEngine function call in any record or component-record location.
Place the Trigger3CEngine function call only in the SavePostChange PeopleCode event.
Place the Trigger3CEngine function call only in locations where a person ID (EMPLID or similar field) or organization ID (EXT_ORG_ID or similar field) is included in the component.
After you identify and place the appropriate Trigger3CEngine function, you must define the online triggers.
You can view 3C engine triggers in the Trigger Result table before running the 3C engine trigger background process. You can also add individuals or organizations to the trigger table before initiating the background assignments.
Trigger definitions set to process assignments in background add rows to the Trigger Result page as users perform the business transactions that meet the trigger conditions. For example, you can define a trigger to invoke the 3C engine when a new applicant is added. If you set the process mode to batch for the trigger, each time a new applicant is added to the database, the 3C engine inserts a row on the Trigger Result page for the new applicant.
Note. Trigger definitions set to system mode do not add rows to the Trigger Result table as business transactions are performed.
Page Name |
Object Name |
Navigation |
Usage |
TRGR_PROMPT_TBL |
Campus Community, 3C Engine, Set Up 3C Engine, Trigger Prompt Table |
Map trigger prompts identifying the edit table to use with the trigger fields. |
|
TRGR_3CS_ON_SETUP |
Campus Community, 3C Engine, Set Up 3C Engine, Trigger Definition |
Identify trigger conditions to invoke the 3C Engine. |
Access the Trigger Prompt Table page.
Edit Table |
Enter the source record that contains the field conditions to use on the Engine Trigger Definition page. Mapping to an edit table is optional. For example, to make academic career (ACAD_CAREER) values available from the Engine Trigger Definition page, map to the Academic Career Table (ACAD_CAR_TBL). |
Access the Trigger Definition page.
Trigger Action |
The system displays the action (New (add), Change, or Delete) that you selected. The action must occur as described on this page to invoke the 3C engine. Note. The SavePostChange PeopleCode must use the same add, change, or delete action that you define here. |
Trigger Level |
Select the level at which this action must occur to invoke the 3C engine. Record: The specified trigger action on the row invokes the 3C engine process, regardless of field. You must specify the 3C engine Event ID to process for a record level trigger. Field: The specified trigger action on the field invokes the 3C engine process. You must specify the Event ID to process and the fields on which the specified action occurs, to invoke the 3C engine. |
Function |
Enter the functional area (administrative function) for this event trigger. |
Trigger Assignment
System |
Select this check box to insert or update in real time, the communications, comments, and checklists specified in the 3C engine event ID. |
Batch Process |
Select this check box to indicate that when the specified action occurs to the record or field, the system should insert a row on the Engine Trigger Results page for use by 3C engine background processing later. |
Override Parameters
Override |
Select this check box to prevent the 3C engine from using the field or record conditions identified on this page, and, instead, use the logic configured around the Function Trigger3CEngine PeopleCode on the record or component location. If you select the Override option, you must specify the overriding 3C engine event ID to use. |
Override Event ID |
Enter the 3C engine event to process when the Override option is selected. |
Duplication Communication Check
Check Duplicate Communication |
Enter the 3C engine event to use to determine if a communication is a duplicate and to assign or prevent assignment according to the defined conditions. |
Duplicate Checklist Check
Check Duplicate Checklist |
The 3C engine event that determines if a checklist is a duplicate and assigns or prevents assignment according to defined conditions. |
Record Level
Event ID |
Enter the 3C engine event to process when the trigger level is Record. |
Field Level
Field Combination |
The system displays the next sequential field combination for each field level event ID that you add. |
Event ID |
Enter the 3C engine event to process when the trigger level is Field and the specified field conditions are met. |
Field Conditions
You can define multiple field combination conditions. When the specified trigger action meets any of the conditions, the 3C engine processes the specified field level 3C engine event.
Field Name |
Enter the name of the field on the specified record that, when this trigger action is performed, must meet the specified condition to invoke the 3C engine. |
Operator |
Enter the conditional operator for this field condition and the value that it modifies—for example, the admission term field (ADMIT_TERM) must be greater than or equal to 0390 (March 1990). Values for this field are delivered with the system as translate values. You can modify these translate values: < Less than. <= Less than or equal to. <> Not equal. = Equal to. > Greater than. >= Greater than or equal to. IN: In. |
This section provides an overview of 3C engine security and discusses how to assign engine event 3C groups.
You use 3C groups to set security for 3C engine events just as you do to set security for communications, checklists, and comments outside of the scope of the 3C engine. A user can then trigger only the events within the 3C group to which he or she is assigned. When the trigger is invoked online, the PeopleCode function assigns only those engine events for which that user has inquiry or update access. If the user does not have security access for the engine event, the system ignores the assignment. 3C group security applies to online event assignment only.
See Also
Page Name |
Object Name |
Navigation |
Usage |
EVNT_GRP_3C_TABLE |
Campus Community, 3C Engine, Set Up 3C Engine, Event 3C Groups |
Assign engine event 3C groups to assign security to 3C engine event definitions. |
Access the Event 3C Groups page.
Add the groups that should have security access to this event ID.
See Setting Up 3C Group Security.
This section provides an overview of trigger results and discusses how to:
View 3C trigger results.
View additional trigger result details.
You can review the 3C engine triggers on the 3C Engine Trigger Results page before running the 3C engine trigger background process to assign the communications, checklists, and comments in batch. You can also add individuals or organizations to the trigger table before initiating the batch assignments.
Trigger definitions that are set to process assignments in batch add rows to the 3C Engine Trigger Results page as users perform the business transactions that meet the trigger conditions. For example, you can define a trigger to invoke the 3C engine when a new applicant is added. If you set the process mode to batch for this trigger, each time a new applicant is added to the database, the 3C engine inserts a row for the applicant on the Trigger Result page.
Page Name |
Object Name |
Navigation |
Usage |
TRGR_3CS_TABLE |
|
View trigger results to determine the individuals or organizations to which the 3C engine background process assigns the communications, comments, or checklists. |
|
TRGR_PROS_SEC |
Click the Variable Data link on the Trigger Result page, Trigger Detail 1 tab. |
View or change the variable data for the targeted individual or organization. |
Access the 3C Engine Trigger Results page.
Trigger Detail 1 tab
ID Type |
Specify the type of ID, either Person or Organization. |
ID |
The system displays the ID of the person or organization for the 3C engine to process. |
Trigger Status |
Select the status of the trigger process to use for the specified individual or organization. By default, when the 3C engine adds a row in the trigger table, it sets the trigger status to Processed. You can override this value. Rows set with the status of Processed are the only rows processed by the 3C engine. To temporarily disable a row from being processed, perhaps to do some investigation, you must set the trigger status to something other than Processed. The other values are: Cancelled, Error, In Process, Suspense, or Unprocessed. These values are delivered with the system as translate values. You should not modify the delivered values, but you can add others. You can reset the trigger status to Processed to include it in the next run of the process. When you run the 3C engine process, the rows set to Processed are deleted, leaving only the rows manually set to a different trigger status. |
Function |
The system displays the administrative functional area of this 3C engine event. |
Variable Data |
Click this link to access the Variable Data page, where you can view or change the variable data associated with this individual or organization. |
Date Added |
Enter the date when this ID is added to the trigger. The default date is the current system date. You can override this value. |
Access the 3C Engine Trigger Results page, Trigger Detail 2 tab.
Trigger Detail 2
Trigger Source |
Select the source to use to determine the individuals or organizations to include in this process. Batch: The system automatically sets the trigger source to this value when the 3C engine background process processes this ID. Online: The system automatically sets the trigger source to this value when a business transaction within the system triggers the 3C engine to process this individual. User: The system automatically sets the trigger source to this value when you click Add to add a row and enter an additional ID on the Trigger Detail 1 tab page. |
User ID |
Enter the ID of the user performing the business transaction that invoked the 3C engine trigger or the ID of the user who initiated the run of the process that resulted in the addition of this row. |
Assign ID |
Enter the ID of the individual responsible for assigning this trigger. |
Print Comment |
Select this check box to include the comments in the Letter Generation data extract process. |
Comments |
The system displays the comments from the Event Definition detail page. You can change the comments and add enter additional comments. |
Process Name |
The 3C Engine does not use this field. You can use this field to process the ID using a different process, for example Manual or Legacy process. |
This section provides an overview of the 3C engine process and discusses how to:
Specify 3C engine process parameters.
Manage duplicate communication assignments.
Use PeopleSoft Process Scheduler to run the 3C engine background process and process 3C events in the background at a future time. You can run the process by selecting the IDs stored in the trigger table results, or by selecting the IDs using mass change definitions or Population Selection, or a combination of the three.
When you run the background process on a selected population, the communications, comments, and checklists identified by the 3C engine event are added or updated for the individuals or organizations identified by the population selection tool that you identify.
When you run the background process on trigger table results, the communications, comments, and checklists identified by the 3C engine event are added or updated for the individuals or organizations that the trigger added to the Trigger Result page.
When you run the background process on mass change groups or definitions, the 3C engine uses the selection criteria definition and certain other mass change definitions to identify the individuals or organizations for which to add or update communications, checklists, and comments.
You can also specify conditions for the 3C engine to prevent assignment of duplicate communications.
Page Name |
Object Name |
Navigation |
Usage |
RUN_CNTL_3CENGINE |
Campus Community, 3C Engine, Run 3C Engine, 3C Engine Parameters page |
Select how, what, and for whom the 3C engine background process is process. |
|
EVNT_3CS_SETUP |
Click the Detail link next to the Event ID field on the 3C Engine Parameters page. |
View details of the event specified for the 3C engine background process to use. |
|
EQUATION_EDITOR |
Click the Create Equation link, which appears beside the Equation Name field on the 3C Engine Parameters page when Process 3C's is set to Population Selection and the selection tool is Equation Engine. |
Select an equation for the 3C engine background process to use for population selection. |
|
SCCFP_PS_FILE |
Click the Create File Mapping link, which appears beside the empty File Mapping field on the 3C Engine Parameters page when Process 3Cs is set to Population Selection and the selection tool is External File. Click the Edit File Mapping link, which appears beside the populated File Mapping field on the 3C Engine Parameters page when Process 3Cs is set to Population Selection and selection tool is External File. |
Create or edit a mapping so that the 3C engine background process can use the uploaded file to identify the desired population. |
|
QRY_SELECT |
Click the Launch Query Manager link, which appears beside the Query Name field on the 3C Engine Parameters page when Process 3Cs is set to Population Selection and the selection tool is PS Query. |
View or create a query for the Population Selection process to use. |
|
MC_DEFN_SA |
Click the Edit link, which appears beside a Mass Change definition on the 3C Engine Parameters page when Process 3Cs is Mass Change. |
View or edit a mass change definition. |
|
Manage Duplicate Assignment |
MANAGE_DUP_ASSIGN |
Campus Community, 3C Engine, Run 3C Engine, Manage Duplicate Assignment |
Specify conditions for preventing duplicate communication and checklist assignment. |
Access the 3C Engine Parameters page.
Process 3Cs
Group boxes and fields appear on this run control page based on the process that you select: Population Selection, Trigger Table, Mass Change, or any combination thereof.
Population Selection |
Select to use the Population Selection process to identify the IDs for the 3C engine to process for the event that you specify. When selected, the Event Selection and Population Selection group boxes become available. Note. The Population Selection check box is not visible if the population selection context for the 3C Engine does not allow this menu navigation to use Population Selection to select the IDs to process. |
Trigger |
Select to have the 3C engine process the rows on the 3C Engine Trigger Results page for the event that you specify When selected, the Event Selection group box becomes available |
Mass Change |
Select to have the 3C engine process the mass change group ID data for the event that you specify When selected, the Mass Change Selection group box becomes available. |
Event Selection
This group box appears when you select Population Selection or Trigger Table., or both.
Academic Institution |
Enter the institution whose data this program should process. |
Administrative Function |
Enter the functional area of the data to process. The field values that appear or become available on the rest of the page are based on the administrative function that you enter. |
Event ID |
Enter the 3C engine event ID to process. |
Detail |
Click to access the Event Definition page for the specified event ID where you can view or update the event definition and determine which communications, checklists, and comments the definition includes. |
Joint Processing
This group box appears for all selections.
No |
Select this option if you do not want to apply joint communication rules to this process. |
Yes, All Joint IDs |
Select this option to apply joint communication rules and include all communications set to enable joint communications. |
Yes, if match exists |
Select this option to apply joint communication rules and include joint communications only when dates in the variable data fields match. |
Communication Key, Checklist Code, and Comment Category
These group boxes appear when you select Population Selection or Trigger Table. or both. They do not appear for Mass Change because the communication key is selected from inside the mass change definition.
The system displays the Comm Key for the checklist code and checklist item and the comment category associated with the event ID that you entered. The 3C engine adds or updates these items for the IDs identified by the processes you selected .
Population Selection
This group box appears when the Population Selection process is selected.
Population selection is a method for selecting the IDs to process for a specific transaction. The Population Selection group box is a standard group box that appears on run control pages when the Population Selection process is available or required for the transaction. Selection tools are available based on the selection tools that your institution selected in the setup of the Population Selection process for the application process and on your user security. Fields in the group box appear based on the selection tool that you select. The fields behave the same way from within the group box on all run control pages and application processes.
If your institution uses a specific delivered selection tool (PS Query, Equation Engine equation, or external file) to identify IDs for a 3C engine transaction, you must use it.
See Using the Population Selection Process.
Mass Change Selection
This group box appears when you select Mass Change.
Mass Change Group ID |
Enter the group ID to process. |
Mass Change Definition |
Displays the mass change definitions that are assigned to the specified Mass Change Group ID. |
Edit |
Click to access the Student Administration page of the Mass Change component where you can view and edit the specific mass change definition. |
See Using Mass Change.
Access the Manage Duplicate Assignment page.
Click the Explain link beside any item to display a message explaining the options and function of that item.
Duplicate Communication Check
Check Duplicate Communication |
Select this check box to require the 3C engine to determine if a communication is a duplicate before assigning it. When this option is selected and no additional conditions are specified, the engine does not assign the duplicate if it finds that a communication of that letter code is already assigned. When this check box is not selected, the engine assigns the communication, whether or not it is a duplicate. |
To evaluate if two communications are the same, the 3C engine compares these fields:
Label Name |
Record Name |
ID Type |
SA_ID_TYPE |
ID |
COMMON_ID |
Institution |
INSTITUTION |
Administrative Function |
ADMIN_FUNCTION |
Communication Category |
COMM_CATEGORY |
Communication Context |
COMM_CONTEXT |
Communication Direction |
COMM_DIRECTION |
Letter Code |
LETTER_CD |
ID Related |
EMPLID_RELATED |
Joint Communication |
JOINT_COMM |
Include Inclosure |
INCLUDE_INCL |
Additional Conditions to Prevent Duplicate Communication
Enter values in this area to specify whether the engine should compare variable data and status to further identify duplicates and prevent assignment.
Variable Data |
Specify the variable data conditions under which duplicates should not be assigned. Match: If a communication matches a previously assigned communication and they have matching variable data, do not assign the communication. Do Not Match: If a communication matches a previously assigned communication and their variable data do not match, do not assign the communication. (Blank): Do not consider variable data. |
Communication Status |
Specify the communication status under which duplicates should not be assigned. Completed: If a communication matches a previously assigned communication for which the status is completed, do not assign the communication. Not Completed: If a communication matches a previously assigned communication for which the status is not completed, do not assign the communication. (Blank): Do not consider communication status. |
Note. If a variable data and a communication status condition are both specified, then both conditions must be met to prevent assignment of the duplicate communication.
Duplicate Checklist Check
Check Duplicate Checklist |
Select this check box to require the 3C engine to determine if a checklist is a duplicate before assigning it. When this option is selected and no additional conditions are specified, the engine does not assign the duplicate if it finds that a similar checklist code is already assigned. When this check box is not selected, the engine assigns the checklist, whether or not it is a duplicate. |
To evaluate if two checklists are the same, the 3C engine compares these fields:
Label Name |
Record Name |
ID Type |
SA_ID_TYPE |
ID |
COMMON_ID |
Checklist Code |
CHECKLIST_CD |
Institution |
INSTITUTION |
Administrative Function |
ADMIN_FUNCTION |