Configuring Recruitment Manager Preferences

Last updated
Save as PDF

The RM Preferences tab allows users to enable or disable various triggers and to restrict which record types some of them act upon. For additional information, see Recruitment Manager Triggers.

To access RM Preferences:

Navigate to the RM Preferences tab.
Assign the appropriate value to each setting described below.

Setting	Description
Auto-Update EH Name	When checked, the Enrollment History Name in the Enrollment History record will be updated with the School value.
Auto-Update Test Type	When checked, the Record Type field in the Test record will be updated with the value in the Test picklist during insert or update.
Auto-Update Test Name	When checked, the Test Name field in the Test record will be updated with the value in the Test picklist during insert or update. When unchecked, the Test Name field in the Test record will instead be updated with the Record ID.
Automatic School Matching	This trigger updates the "School Name" field on the Student record to the appropriate School based on a CEEB code value. If enabled, you can populate the CEEB Code field, on the Student record, during creation of that record. The trigger will query the Schools Object to find a School that matches the CEEB Code. If a match is found, the "School Name" field is populated with the name of the School. If no match, the "School Name" field is populated with the "Unknown School".
Automatic School Matching (EH)	This trigger updates Enrollment History Account Name based on CEEB code. Uses 0 to pad 5 digit CEEB codes to 6 digits and shorter CEEB codes to 4 digits.
Batch Rollup Object and Batch Rollup Context	These fields allow you to run a batch job on the selected object that will update all records in your CRM and roll up the master object data to the Contact.
Batch rollup Object	Select the object to run the batch rollup. The batch rollup job can be performed on one object at a time. Please wait for the confirmation email that batch rollup has completed before running batch rollup on another object. The Run Rollup button runs a batch job to perform a rollup on the selected object in the "Batch Rollup Object" field. Note: Update Related Contacts Async in Base Custom Settings needs to be disabled to run the batch roll up. It can be re-enabled once the batch is completed.
Batch rollup Context	Select "Process All" to run rollup on all records. Select "Process Tracked" to run rollup on all records with values in tracked fields.
CEEB Assign All Records	Deprecated functionality.
Checklist functionality	Deprecated functionality to manage status of required items for applications. The Application Requirements Manager package replaces this functionality.
Contact rollup from Application	When ‘Contact rollup from Application’ is checked, the data from Application will be rolled up to the Contact record by Profile Builder.
Contact rollup from Enrollment History	When ‘Contact rollup from Enrollment History’ is checked, the data from Enrollment History will be rolled up to the Contact record by Profile Builder.
Contact rollup from Inquiry	When ‘Contact rollup from Inquiry’ is checked, the data from Inquiry will be rolled up to the Contact record by Profile Builder.
Contact rollup from Merge	If Contact rollup from Merge is checked and a Contact is merged, the After trigger will execute so that the batch class will be executed. Note: If there are multiple objects mapping roll up data to the same field on the Contact, only 1 record data will be added to the field. Currently it is not defined as to which record will win. For Example; If the Application and Inquiry object are mapping to Anticipated Major on the Contact, both records have different source field values, but only one records data will be rolled up to the contact.
Contact rollup from Test	When ‘Contact rollup from Test’ is checked, the data from Test will be rolled up to the Contact record by Profile Builder. Note: Recruitment Manager Settings should only be enabled for objects that have already been setup to use Source to Master.
Contextual triggers apply to	This preference allows the user to apply Recruitment Manager triggers to specific Record Types. This is only used if you are using Record Types in Salesforce. For example, if you use the Recruitment Manager and Advancement modules, you will not want the RM triggers to run against Alumni Contact records.
Default Account ID	This setting will check the CEEB code field on the Contact to see if there is a valid Account match with that CEEB to create the Contact. If there is no CEEB code entered or the CEEB code does not match to any Account, it will use the Default Account ID that you specify here. If the Default Account ID is blank or Invalid, it will default to using the Unknown School. Note: This setting will only be used if the Default Account ID Setting in Base Custom Settings has NOT been enabled. This setting is used when Automatic School Matching is turned on as well.
Duplicate checking	When enabled, this trigger evaluates a newly created contact (student) record using an algorithm that evaluates 14 different combinations of fields including name, email, mailing address. Matching records are then marked as a potential duplicate. Note: This trigger uses baseline Salesforce functionality and is not appropriate for a large set of de-duping.
Enrollment Deposit	Updates the "Student Stage" field, on the Student Object, to "Deposited" when an application deposit is received. Note: This trigger does not update the "Student Stage" if it is already set to "Enrolled."
Excluded Student Statuses	This is a comma-delimited list of statuses that will not set a student's status to 'Applicant' when the Application Status trigger is fired.
Export Sequence	Trigger to sequence records for export by (now deprecated) single flat file Informatica export process. Normally unchecked, should only be checked if using the single flat file export.
Lead Source Preservation	When enabled, this trigger preserves the "Lead Source" value, based on the oldest record, when merging Student records. Note: If you want to remove sources from your picklist, you must temporarily disable this setting. Once your changes are complete, you can reenable this setting.
Prevent Student Stage rollback	Prevents the student from regressing to an earlier stage in the application process based on the picklist order.
Relevant Record Types	If the "Contextual triggers apply to:" field is set to "Specified Record Types Only (choose below)," then you must check the appropriate Record Types in this preference. Once saved, Recruitment Manager triggers will only be evaluated against Contact records with the appropriate Record Type specified in this preference.
Scope of Code	Controls which Contact or parent Contact record types are affected by the PostDeleteContact trigger.
Set App Fee Received Date	When checked, sets the Application Fee Received Date to TODAY when the Application Fee Payment Received is set to TRUE. The trigger only updates Null values so existing data is not overwritten.
Set App Submitted Date	When checked, sets the Application Submit Date to TODAY when the Application Stage field is set to Submitted. The trigger only updates Null values so existing data is not overwritten.
Set Applicant Status	This value determines when the "Student Stage" field on the Student Object is updated to "Applicant". There are three settings: 0 = Trigger is disabled 1 = Student Stage is updated to "Applicant" when the application record is created. 2 = Student Stage is updated to "Applicant" when the "Application Stage" field, on the Application Object, is updated to "Submitted".
Source Field Management	This trigger controls the relationship between the "Lead Source" (picklist) and "Source" (multi-value picklist) fields. If enabled, all Student Source data should be populated into the "Source" field. The trigger will evaluate the Student record to see if the "Lead Source" has been previously populated. If the "Lead Source" is not populated, the "Source" value will be copied to the "Lead Source" field. If the "Lead Source" field has already been populated, the "Lead Source" field will remain unchanged.

Application Requirements Manager Configuration

Setting	Description
Enable Application Requirement Manager	Enables checklist item creation and completion matching.
Create Dynamic Enrollment Requirements	If checked, will automatically create checklist item records for additional enrollment history records associated to the Contact and marked as Applies to Requirement.
Checklist @future Minimum Batch Size	If processing @future, this setting determines at which point batches will run @future. To allow for manual entry without @future, recommended size is 20-30.
Dynamic Enrollment Text	Label that displays in Checklist Items for dynamically created transcripts.
Process Checklist @Future	If checked, checklist completion tests will run @future. It can be used to limit SOQL queries.
Relevant Field	API label of the field used to define an application type.

Yield History

Setting	Description
Yield History Account Lookup	Allows the selection of an additional Account lookup for use with Yield History. The Rate For Account will include the additional Account selected. If you do not select a value the system will continue to look up from Account ID.