Introduction

In the Regent Smart Form Manager Tool, schools with a Regent Fund or Regent Review License can update an existing Smart Form, import an existing Smart Form from a different environment (e.g. QA to Prod), and create a new Smart Form.

Overview

The Smart Form Manager Tool is available in the Regent Tools menu for users with the permission enabled to view or edit the ‘Smart Form Manager Tool’

The Document Assignment Tool is comprised of a top section with selection options for Institution Name and Query Name and a bottom section for the selection of Documents to be assigned.

NOTE: This tool is designed to be used at the Institution level. Only one Campus per Institution should be configured.

Getting Started

Schools will need to:

1. Be on or upgrade to the Regent Award 6.5.0.0 Release or a subsequent Release

2. Update Enterprise Permission

3. Create Smart Form

4. Update Document Tracking Setup

Smart Form Manager Tool

A tree-view menu displays on the left-hand side of the Smart Form Manager tab on the Smart Form Manager screen.

The following options are available in the tree-view menu:

• + Create Smart Form

  • Used to begin the creation of a new smart form.

• + Import Smart Form

  • Used to import/load a Smart Form from one environment to another.

• → Active Smart Forms

  • Used to access an existing 'Active Smart Form. A Smart Form is considered ‘Active’ if today’s date falls within the effective Start Date and End Date defined on the Smart Form Information tab.

• → Inactive Smart Forms

  • Used to access an existing ‘Inactive’ Smart Form. A Smart Form is considered ‘Inactive’ if today’s date does not fall within the effective Start and End Date defined on the Smart Form Information tab.

Creation or Editing of a Smart Form

Information

The Information tab provides basic Smart Form setup information, including the Smart Form Name, Federal Award Year, and valid Effective Start and End Dates.

Document Persistence

Document Persistence allows school users to create rules using regular expressions (see https://www.geeksforgeeks.org/javascript-regexpregular-expression/) to add or update a student document requirement in Regent. Document Requirements are added and updated upon the completion, including signature(s), of the Smart Form. The document requirement is only added or updated if the expression results are true. For example, if a student indicates, ‘I was married at the time of FAFSA completion but am no longer married’ on a Smart Form question response, Document Persistence can be created to add a Divorce Decree document requirement with a status of ‘Needed’ to collect the additional documentation required.

Document Setup must be considered when adding Document Persistence. For example, if a document is configured to ‘Enforce Scope Uniqueness’, a new document will not be added if it already exists, however, the status of an existing document can be updated. Alternatively, if documents are configured to be added automatically via another process (e.g. ISIR Import), the Document Persistence can be used to update the Document Status on an existing document(s).

Student Persistence

Student Persistence updates the Student Portal Authorization fields in Regent based on the Smart Form question response(s). Student Persistence is added and updated upon the completion of the Smart Form, including all required signature(s).

Parent/Spouse Persistence

Parent/Spouse Persistence updates the Parent/Spouse Reference fields in Regent based on the Smart Form question response(s). Parent/Spouse Persistence is added and updated upon the completion of the Smart Form, including all required signature(s).

Sections

Section names are displayed on the Smart Form menu within the Student Portal. Sections are displayed in numerical order from lowest to highest based on the number entered in the Section Sort Order field.

Groups

Groups are used within each Section to categorize questions. Each group is comprised of one or more questions. All questions contained within a group are organized beneath the Group name defined and displayed within each Section. Groups display in numerical order from lowest to highest based on the number entered in the Group Sort Order field.

Questions

Questions are displayed within each Group to categorize questions. Each group is comprised of one or more questions. All questions contained within a group are organized beneath the Group name defined and displayed within each Section. Questions display in numerical order from lowest to highest based within the Group on the number entered in the Question Sort Order field.

Dependencies

Smart Forms can be designed to use conditional logic to tailor each question to an individual applicant and minimize the number of questions an applicant is required to answer by using Dependency logic. Dependencies use dynamic logic for Sections, Groups, and Questions to make Visible or hide based on responses to Questions within the Smart Form. Dependencies also control if a Question is Required when made Visible or not. For example, a Dependency can be created to Hide a Question, make a Question Visible and Required, or make a Question Visible and Not Required.

A Section, Group, or Question can have one or more Dependency groups. Each Dependency group is comprised of one or more Dependency rules. Each Dependency group uses a selected Operator Type of ‘AND’ or ‘OR' when evaluating if the Dependency rule(s) are 'true’.

Dependency Comparison Operator

• The "AND" Compare Operator is used to determine if ALL Dependency Rules are true.

• The "OR" Compare Operator is used to determine if one or more Dependency Rules are true.

Tip: It's recommended that you set a Section/Groups/Questions visibility to a base visibility, and then only create rules which change the visibility. This way you do not have conflicting dependencies or dependency rules (one rule which makes it hidden, and another rule which makes it visible). If both rules evaluate to true, then it can be more complicated to determine which rules visibility applies. For instance, perhaps you set a Section's visibility to hidden, and then only create dependencies/dependency rules that make it visible. See the "Competing Dependencies Example" in Examples section below.

Dependency Rules

• Rules can be a two types: question based or expression based

  • Question based rules are the rules that makes target object dependant of the value of another question in the application.

  • Expression based rules are the rules that are evaluated using an expression provided by the user. This expression is based on the javascript language. A single rule expression can be build on one or more dependent questions using various logical and mathematical operations. Question values are referenced by using the following notation {questionCode}

• The individual rules have the flags for visible and required. When different rules in the same dependency have different values for those flags, the first rule that is evaluated will trigger, and all subsequent rules in the dependency will be ignored.

• The dependency rules are evaluated in the order they were added to the database.

• Every rule has the following information:

  • Comparison operator (=, >, <, >=, <=, !, <>, !=)

    • The symbols "<>" and "!=" are interchangeable operators that mean "not equal".

    • The Exclaimation point means logical not.

  • Dependent question option id

  • Expression

  • Required Flag

  • Visible Flag

• Rules can be a two types: question based or expression based

  • Question based rules are the rules that makes target object dependant of the value of another question in the application.

  • Expression based rules are the rules that are evaluated using an expression provided by the user. This expression is based on the javascript language. A single rule expression can be build on one or more dependent questions using various logical and mathematical operations. Question values are referenced by using the following notation {questionCode}

  • Logical evaluations can be strung together using logical AND (&&) and logical OR (||).  These kind of conditions allow multiple comparisons to determine the ultimate result of the expression.  The words "AND" and "OR" are interchangeable with "&&" and "||", respectively.

    • SnapUtility.EqualOfAny('hi', 'is', 'hi', 'here') && SnapUtility.IsCurrentDateBefore('01/01/2013') - returns false because both conditions must be true for the expression to be true.

    • SnapUtility.IsCurrentDateBefore('01/01/2013') || SnapUtility.EqualOfAny('hi', 'is', 'hi', 'here') - returns true because at least one of the conditions is true.

  • Several Helper functions are provided:

    • UpperCase - returns string - Converts the argument to UPPER CASE. eg: SnapUtility.UpperCase("upper case") returns "UPPER CASE".

    • Trim - returns string - Removes leading and trailing whitespace.  eg: SnapUtility.Trim("   Hello   ") returns "Hello".

    • TrimUpper - returns string - Performs both UpperCase and Trim commands.

    • EqualOfAny - returns boolean - Performs TrimUpper and checks if the first argument is in the list of remaining arguments (this function is case insensitive).  eg: SnapUtility.EqualOfAny("Hi", "Does", "hi", "exist") returns true.

    • IsNumber - returns number - Checks to see if the first argument is a number.  If it is not, the second argument is returned.  eg: SnapUtility.IsNumber("Dog", -1) returns -1.

    • CheckNumber

    • CompareDate - returns number - Checks to see how two dates compare.  If the first date is after the second date, the function will return a positive number.  If the second date is after the first one, the function will return a negative number.  If the dates are the same, the function will return 0.  If the arguments cannot be resolved to dates, the function returns NaN.  eg: SnapUtility.CompareDate('07/19/2013', '08/01/2013') returns -1.

    • IsCurrentDateBetween - returns boolean - Checks to see if the current date falls in a range (non-inclusive).  eg: SnapUtility.IsCurrentDateBetween('01/01/2013', '01/01/3000') returns true.

    • IsCurrentDateAfter - returns boolean - Checks if the current date falls after a specified date.  eg: SnapUtility.IsCurrentDateAfter('01/01/2013') returns true.

    • IsCurrentDateBefore - returns boolean - Checks if the current date falls before a specified date.  eg: SnapUtility.IsCurrentDateBefore('01/01/2013') returns false.

    • AddDaysToDate - returns Date - Adds a specified number of days to the specified date.  eg: SnapUtility.AddDaysToDate('01/01/2013', 9) returns '01/10/2013'.

  • If a dependant question is hidden (visibleFlag = 0) then the dependency rule is not evaluated and always returns false.

  • For the expression based rules, by placing “@” symbol before the question code in expression points the application to evaluate this question even if it is hidden. (@{studentsMaritalStatus})

  • If one of the dependant questions (in case of an expression based rule) is hidden then the whole expression will not be evaluated.

  • Because visibility / required flags are set on the Rule level it is possible to have one rule which sets something to hidden and another rule which sets something to visible in the same dependency.

    • For AND dependencies, the visibility / required flag of the last rule will be used

    • For OR dependencies, the visibility / reguired flag of the first triggered rule (rule with conditions met) will be used. 

• If there are multiple Dependencies, each with its own set of Dependency Rules then the following evaluation process will take place:

  • All dependencies and its dependency rules are read from the database in the order they were added.

  • Application starts to evaluate dependency rules

  • Application checks the current rule’s dependant question’s status. If a dependant question is hidden then the rule is ignored.

  • In case of an expression based rule, application checks every question’s status that is met in the expression. If one of the questions is hidden and does not have status ignoring symbol then the whole expression is ignored.

Dependency Examples

1. /wiki/spaces/SNAP/pages/8716538

Validations

https://velocity.apache.org/engine/1.7/user-guide.html

https://www.geeksforgeeks.org/javascript-regexpregular-expression/

Document Requirement Persistence

1. Condition (expression) -> an optional javascript expression, similar to dependency / complex validator expressions which can be set. If it's set, the doc req will only attempt to persist if the expression results in true. Will handle {questionCode} formatting. No special logic for whether questions are hidden, visible, etc.

Will handle {questionCode} formatting.

Examples

Example 1

1. Student starts a Verification Worksheet smart form application.

2. Student indicates No, I have already filed a tax return SNAP smart form questionnaire.

3. Student completes and signs their Verification Worksheet.

4. A 2015 Student Filing Extension Granted by the IRS document requirement is created for the student.

5. Student starts a Verification Worksheet - Change smart form application.

6. Student indicates No, I have already filed a tax return.

7. Student completes and signs their Verification Worksheet.

8. A 2015 Student Filing Extension Granted by the IRS document requirement does not get created for the student.

Example 2

Given:

1. Verification Worksheet for FAY

   1. W-2 document, scope uniqueness is turned off in REM

   2. Student selects "Will Not File"

   3. Student indicates that they received a W-2 from Employer 1 and provides information for Employer 1

   4. Student indicates that they received a W-2 from Employer 2 and provides information for Employer 2

When:

1. Student completes and signs the Verification Worksheet - Change smart form for same FAY

   1. Student selects "Will Note File"

   2. Student indicates that they received a W-2 from Employer 1 and provides information for Employer 1 (Employer A)

   3. Student indicates that they received a W-2 from Employer 2 and provides information for Employer 2 (Employer B)

   4. Student indicates that they received a W-2 from Employer 3 and provides information for Employer 3 (Employer C)

Then:

1. A new, needed, W-2 document is created in REM, with the reason set to the name of Employer 3 (Employer C)

Example 3

Given:

1. Verification Worksheet for FAY

   1. W-2 document, scope uniqueness is turned off in REM

   2. Student selects "Will Not File"

   3. Student indicates that they received a W-2 from Employer 1 and provides information for Employer 1 (Employer A)

   4. Student indicates that they received a W-2 from Employer 2 and provides information for Employer 2 (Employer B)

When:

1. Student completes and signs the Verification Worksheet - Change smart form for same FAY

   1. Student selects "Will Note File"

   2. Student updates the information for Employer 1 to Employer B

   3. Student updates the information for Employer 2 to Employer C

   4. Student deletes the information for Employer 3

Then:

1. The W-2 for Employer A is waived

2. The W-2 for Employer B remains unchanged

3. The W-2 for Employer C is created with a needed status

Example 4

Given:

1. Verification Worksheet for FAY

   1. W-2 document, scope uniqueness is turned off in REM

   2. Student selects "Will Not File"

   3. Student indicates that they received a W-2 from Employer 1 and provides information for Employer 1 (Employer A)

   4. Student indicates that they received a W-2 from Employer 2 and provides information for Employer 2 (Employer B)

When:

1. User changes W-2 for Employer A to satisfied in REM

2. Student completes and signs the Verification Worksheet - Change smart form for same FAY

   1. Student selects "Will Note File"

   2. Student updates the information for Employer 1 to Employer B

   3. Student updates the information for Employer 2 to Employer C

   4. Student deletes the information for Employer 3

   5. REM

Then:

1. The W-2 for Employer A is unchanged

2. The W-2 for Employer B remains unchanged

3. The W-2 for Employer C is created with a needed status

Technical Details

1. Condition (expression) -> an optional javascript expression, similar to dependency / complex validator expressions which can be set. If it's set, the doc req will only attempt to persist if the expression results in true. Will handle {questionCode} formatting. No special logic for whether questions are hidden, visible, etc.

2. Match configuration - Capability to create, update, or do nothing if a matched document for the student already exists based on the existing doc requirement status. User can select multiple statuses for update vs create. Status selection will be mutually exclusive (a doc status can only exist in one of the following items):

3. Update On Match Statuses: (selected document statuses)

4. Create On Match Statuses: (selected document statuses)

5. Otherwise ignore

6. Can configure to create the document if there is no match

7. Scope: STUDENT or FEDERALAWARDYEAR

8. Status: NEEDED,SATISFIED,UNSATISFIED,RECEIVED,INCOMPLETE,WAIVED

9. Status doc will be saved as if the questionnaire is not an esign questionnaire, or it is an esign questionnaire but user did not esign (they paper signed instead)

10. ESignedStatus: NEEDED,SATISFIED,UNSATISFIED,RECEIVED,INCOMPLETE,WAIVED

11. Document will be created or updated with this status if it's an ESIGN questionnaire and the user did choose to E-sign

12. FEDERALAWARDYEAR will be set to Federal Award Year of questionnaire

13. Supported entry types: AddressRelated, AwardRelated, AuditRelated, COARelated, CODRelated, DisbursementRelated, DocumentRelated, EnrollmentRelated, ISIRRelated, NeedRelated, PLUSRelated, PJRelated, QARelated, ResourceRelated, R2T4Related, SAPRelated, SBLLoad, ServiceRelated, VerificationRelated, CommunicationRelated, Other, ESTRelated, WorkStudyRelated

14. Attachment Type: None, PdfTemplate, FAFSA

15. None - no attachment stored in REM

16. PdfTemplate - Indicates a PDF attachment will be created based on the value of Attachment Template

17. FAFSA - The standard Dept. Of Ed. FAFSA (that matches fed award year of questionnaire) will be pre-populated from the SNAP questionnaire.

10. Attachment File Name: string of file name as stored in REM

11. Attachment Template - string field which will take a named velocity template. Note - this velocity template MUST exist in the theme the questionnaire is processed with, otherwise an "Template 'templatename' does not exist." error will be thrown at time of application processing.

1. Notes about fields which are not configurable

2. Letter correspondence date -> ignored by snap

3. Email correspondence date -> ignored by snap

4. Activity Source Type - STUDENTACTION always used

5. Message - will use the message as set up in REM document setup

6. Reason - will use the reason as set up in REM document setup

7. Received Date - Will rely on REM services automatically setting to current datetime if existing received date is null (or we are creating doc) and status is RECEIVED or SATISFIED

8. Reviewed Date - Will rely on REM services automatically setting to current datetime if existing reviewed date is null (or we are creating doc) and status is SATISFIED

9. This configuration will be included in when a questionnaire is copied, exported, or imported.

10. EFAFSA:

11. Will persist as the current EnableEFAFSAPersistence configuration setting dictates (which can be scoped for the whole snap instance, or scoped to questionnaire which takes precedence)

12. Student demographic fields: These will be handled in another JIRA issue to facilitate testing

13. Management screens in SNAP admin pages (Persistence link/button on questionnaire detail page).

Related Tickets

SNAP-2899 - SNAP questionnaires can be configured to persist document requirements to REM upon app completion

Student Portal: Create new function for Document Requirement Persistence (DRP) Reason Expression

If changes are made, the client should use extreme caution by first making a copy and updating the Document configuration Smart Form Type/Code to use the school-created Smart Form. Any changes made directly to a Regent maintained Smart Form will be overridden upon a new release if enhancements or changes are made. Regent will not make changes to or maintain a ‘copy of’ a Regent-maintained Smart Form.

Expressions

When configuring a DRP, the ‘Name’ must match the name of the document configured in Document Setup. Use caution when Document Names have special characters such as an apostrophe or dash that it is using the identical Document Name and has not been updated by the editor. If no match is found to an existing Document Name configured when executing the DRP expression, an error message is displayed, ‘Document name of <Document Name> is not found'.

Shortkeys:

When configuring a DRP, the ‘Name’ must match the name of the document configured in Document Setup. Use caution when Document Names have special characters such as an apostrophe or dash that it is using the identical Document Name and has not been updated by the editor. If no match is found to an existing Document Name configured when executing the DRP expression, an error message is displayed, ‘Document name of <Document Name> is not found'.

Logical operators, such as, AND (&&), and OR (||) may be used in combination with built-in expressions, such as, SnapUtility.EqualOfAny, and SnapUtility.ReasonEqualToAny. The SnapUtility.ReasonEqualToAny is a special function that can not be used in combination with other expressions and will perform the requested action on existing, student documents where the document reason matches any of the values provided to the function.

Shortkeys: