Bank Challan

Application

Hall Ticket

Example 1:

Receives payment before application.
Target is to collect maximum funds and spend minimum online resources.
1. Day1: Basic registration is done.
1A. Day1 Eve: Admin uploads registration data to Bank website.
2. Day2: Candidate goes to Bank and makes payment
2A. Day2 Eve: Admin downloads transaction list from bank.
3. Day3: Candidate can begin application

It has provision to log back and make corrections.

This method has some limitations:
Method was primitive, though at one end it appears to facilitate, but at the other end, it is more challenging for certain group to login and navigate, so it has had scope for issues.
If a mistake is made after payment, then the edit possibility keeps ambiguity and uncertainity till the last date.
1. the user can login and correct, so most users postpone it.
2. If the system assumes any applcation as final, without user pressing the final submit button, then it is possible on the last day, many uneditted and not final applications are also accepted, which will finally lead to rejection after some excercise.
3. In order to avoid autosubmission, we have to expect the user to press the final submit. Most users postpone it and do it at the last day. This creates accute load on the server and associated issues.
4. If there has been mistake in any basic parameter like dob/mobile etc, then the user has to waste another 3 days to repay and re-initiate application.

https://server1.server1.onlineecas.com/ecas/UserLogin.aspx?ClientID=11700
UserName: admin@admengroup.com
Password: addmen