Job Title and Employer Fields

Overview

In Veracross, the fields Job Title and Employer are stored in two places: the person record and the organization relationship record. Triggers and syncing are built into the system to ensure that data are accurately maintained in both places.

Job Title

The Job Title field on the person table includes a trigger such that when its value is updated, the primary Organization Relationship record’s Job Title field will also be updated.

Note that if there is more than one primary organization relationship record, no sync will occur.

A trigger is on the Organization Relationship so that if the job title is updated on this end, the field on the Person table will also be updated.

No syncing will impact staff/faculty records. The best practice is that staff/faculty should have their Job Title tracked via the field on the Person record, and any change is made to the Person Organization record via the HPU or otherwise will not impact the value entered on the HR or General tab of the person.

Employer

The Employer field is read-only on the Person record. Updates should be made on the Organization Relationship record. When updates are made on the Organization Relationship records, the read-only field on the Person record will be automatically updated.

No syncing will impact staff/faculty records. The best practice is that employer data should not be maintained for staff/faculty since by definition their employer is the school. If the HPU is used to add employers, this additional data will not overwrite what is on the Person record.

The absence of an Organization Relationship record means it is not possible to change the Employer field on the Person record unless an Organization Relationship record has been added.

Employer and job title information on the General tab of the person record is removed when the organization relationship is changed to “Former Employer.”

Recommended Use

The primary use case for Job Title on the Person record is for school employees. The Job Title field on Organization Relationship should be used for all other constituencies like Parents, Alumni, Donors etc. Storing an Employer value for school Employees is redundant; however, Organization Relationship records should be used for all other groups.

The syncing scripts that run in the nightly processes will not sync these data for staff/faculty.