Submit Application

After a user completes the application, the user interface should present a Submit Application option. Also, at submission time, the interface can present any number of disclaimer pages to the user. Generally, after a user submits the application, the user cannot update the application and the user interface would need to enforce this rule using the application status value. The user interface can retrieve this value using the SAD_GETAPPLS service operation.

A typical self-service, online-application user interface might perform the following actions:

• Present a Submit button on the final online application page.

• Prompt the user with any required disclaimers.

• Formulate a request message. Note that if a fee is due and the applicant has opted to Pay Later during the Get Fee Configuration step, then this intent must be indicated in the request message.

• Submit the request message to the SAD_SUBMITAPPL service operation.

• Receive and process a response from AAWS. There are three alternative responses that the user interface needs to cater for:

  • A Success response and fee payment is not required:

    Present the user with a confirmation page. The confirmation page confirms that the application has been submitted.

    Take the user back to the Get Application Summary page.

    Log out the user from the online application.

  • A Success response and fee payment is required:

    Extract the fee amount and currency code from the response.

    Proceed to the Present Fee Options page.

  • An Error response:

    Based on the error codes that AAWS returns, position the user at an appropriate page of the user interface to allow data correction.

    Present validation error messages to the user.

    Present system error messages to the user.