Learn about adding a new program selection to an existing application and ensuring all programs are ranked.
If your application process includes the option of adding or removing program choices on a previously-submitted application, the Adding or Removing Choices modal ensures that the newly selected programs are always ranked and that any required fields for a newly selected program are highlighted for completion.
When the guardian (or admin) enters the application to make additional program selections or remove a prior selection...
a modal will surface that requires the user to rank all choices (old and new) against each other. When the new rankings are updated, the user will be taken to the choice ranking step of the application where the updated rankings are displayed.
If the newly selected program has required fields to be completed in the application form, the related step will be highlighted in red, and the application for that program will be reverted to a status of Not Submitted until the required information is provided.
The application's eligibility will remain, even when the application is reverted back to Not Submitted status.
- Example: an eligible application is modified by the family to add another program choice. The new program choice has required fields to be completed in the form. Even though the application is now considered
Not Submitted, it still retains itsEligiblestatus.
Known issue: if the required field that is added in a highlighted step uses the setting “Disable After Submit”, currently the system does not allow the user to complete the required field. This issue will be resolved through our maintenance release process.
Note: The Guardian is NOT notified in the message center or via email/text that the application is now in a Not Submitted status.
To ensure that families are reminded that there are required fields to be completed on the application, we recommend that a Workflow Notification is created to notify the guardian that their application submission status has been changed.
- Using the
Has Changedcondition, set the custom trigger for the workflow. This trigger will be based on the fieldapplication.submittedchanging.
Comments
0 comments
Article is closed for comments.