In createAccount.xhtml, the accountType drop down is populated with the first account type. The list should start empty and request that the user select an account type.
Refining this request: The createAccount.xhtml page should ONLY ask which type of account should be created. Upon selection and clicking a Next button, the user should be directed to a new page called createAccountDetails.xhtml. This new page will contain the balance of the fields formerly in createAccount.xhtml should do a facelets include with the page coming from the AccountType entity (createAccountPage attribute). The new pages, one for echr and one for ephr should contain the account-type specific text from the existing createAccount.xhtml page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The effect of this change will be that only appropriate questions are asked for each account type. Further, instructions can be targeted to the individual type of application user.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=924283
Originator: YES
Refining this request: The createAccount.xhtml page should ONLY ask which type of account should be created. Upon selection and clicking a Next button, the user should be directed to a new page called createAccountDetails.xhtml. This new page will contain the balance of the fields formerly in createAccount.xhtml should do a facelets include with the page coming from the AccountType entity (createAccountPage attribute). The new pages, one for echr and one for ephr should contain the account-type specific text from the existing createAccount.xhtml page.
Logged In: YES
user_id=924283
Originator: YES
The effect of this change will be that only appropriate questions are asked for each account type. Further, instructions can be targeted to the individual type of application user.