Candidacy

The candidacy contains information specifically related to a particular year, term, program, division, location, department, and type for a candidate. Each candidate can have one or more candidacies; and, while only one is current, all are valid for the appropriate year and term.  For example, Anne Smith might have a candidacy that was deferred from acceptance last year and another candidacy in an acceptance stage for this year.

Prior to making candidate/candidacy entries, the following must be completed:

·       Candidate must exist in the Name Master table.

·       Source code must exist in Source Definition table.

·       Territory configuration must be defined in the Territory Configuration table for counselors to be automatically assigned. However, counselors can be assigned manually.

·       Organization(s) the candidate is associated with must be entered in the Organization Master table.

·       Year and term must be defined in the Year/Term table.

·       If using Program Control, programs must be defined in the Program Configuration table and Year/Term Program Control table.

·       Stage configuration must be defined in the Stage Configuration table.

·       Tests must be defined in the Test Definition table.

·       Requirements must be defined in the Requirement Definition table.

·       Department codes must be defined in the Department table.