*Notes for form administrators:
File Extensions - Before files can be processed into J1, allowed file extensions must be made available to the Admissions Candidacy Essay Attachment Use Code in the Make File Extension Available for Attachment window.
Attachment Mapping - Before the form will successfully process into J1, mapping will need to be updated for each of the Candidacy Attachment rows to ensure that the ATTACHMENT_CDE values are valid attachment types and are associated with the AD_CANDCY Use Code in the Attachment Type Definition window in J1 Desktop.
Relationship Mapping - Before the form will successfully process into J1, mapping will need to be updated for each of the Relationship Information rows to ensure that the REL_CDE values are valid relationship codes defined in the Relationship Definition window in J1 Desktop.
Waiver Codes - The waiver code question has been associated with the Waiver Codes data source. The example is a hard coded data source. In a real-world example, it would be best to store these waiver codes in a custom table.
Payment Profile - The payment profile for this form has been associated with the submit button. The transaction code should be updated to a valid AR_CDE defined in the J1 Desktop Receipt Code Control window.
Mapping Information - This form contains default mappings for questions existing on the form. Some client-specific values, like Candidacy Stage and Type, may be desired and can be added by modifying the mapping and entering a custom value for the specified column.