Often interactions, activities, statuses, decisions reasons, and actual decisions are combined into decision codes. This is an opportunity to consolidate and organize decision codes to be more sustainable by adopting the Slate standard decision names and codes. Adopting these standards from the start will make the rest of the decision process cleaner and easier to understand.

Standard Decision Codes

We recommend using the following decision codes in Slate:

Adding a Decision Code

1. Select Database on the top navigation bar and select Decision Codes.

2. Select Insert.

3. Enter the following User configurations in the dialog box:

   • Status: Set to Active.

   • Name: Name the decision code. We recommend using Slate standard decision names described above.

   • Code: Provide a code. We recommend using Slate standard codes described above.

   • Export Key: Provide an export key for codes that will need to be used in data exports to other systems.

   • Export Key 2: Provide additional export codes when multiple systems are using different codes.

   • Export 3: Provide additional export codes when multiple systems are using different codes.

   • Decision Label (optional): We recommend leaving this setting blank for now. This setting is typically used for financial aid decisions, which is discussed later in the documentation.

   • Priority (optional): If multiple decisions are being released at exactly the same time (for example, an Admit decision and a Financial Aid decision), organize the order in which those decisions will appear to the student. Priority 1 will appear first, priority two will be next, and so on.

   • Prerequisite #1: Some decisions should only be available for release if another decision has been previously added (for example, Deposit Pending). Provide a prerequisite code when applicable.

   • Prerequisite #2: Set additional prerequisite decisions if needed. Important: Slate treats these prerequisite settings as logical ORs, not ANDs.

   • Prerequisite #3: Set additional prerequisite decisions if needed. Important: Slate treats these prerequisite settings as logical ORs, not ANDs.

   • Opt Out: Configure a Deny decision to set the Opt Out tag automatically. Setting this will ensure that those students no longer receive marketing communications.

   • Type: Leave this at Decision.

   • Admitted Student SSO: Leave this at Do not enable.

   • Printable: This allows the Query module to export a letter associated with the decision as a Word document to be used for mail merge.

   • Hide Checklist: Choose Hide checklist when released to no longer display the checklist on the applicant status page for a person once the decision has been released. 

     For example, the applicant status page might normally appear like this:
     But when this decision is released, the applicant status page could look like this:

     🔔 Important:

     This setting also hides the financial aid checklist. It does not hide the forms section of the checklist.

   • Hide Forms - Rules will be created to add required items to the applicant status page for applicants with certain decisions. For example, the reply to offer of admission form may appear as a required form for applicants who have been admitted.
     
     The Hide forms if not yet viewed setting would prevent a required form from appearing on the applicant status page until the applicant has viewed the letter associated with the decision.

     For example, the applicant status page may look like this when a decision has been released:
     After the applicant has viewed the letter, the applicant status page will appear like this:

   Click the Slate Scholar Lightbulb    in the top left corner for a complete listing of all setting descriptions.