Before we delve into the code and operation of our Add/Modify User functional screen, let's review the reasons we have this screen in the first place. Recall that we added a table in the
HR schema named
t_emp_mobile_nos. We are using that table to store cell phone and pager numbers, and we also store (for convenience) the operating-system user ID of the employee. We need to maintain that data to accomplish both single sign-on and two-factor authentication. Additionally, we use the e-mail address in the
HR.EMPLOYEES table for two-factor authentication, so we want to be able to edit that.
In order to maintain the
HR data, we want a functional screen like our Add/Modify User screen, shown in Figure 12-3. This security ...