Disclaimer - Alliance Digital Repository
Disclaimer - Alliance Digital Repository
Disclaimer - Alliance Digital Repository
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
63<br />
FORGOT_PWD table. In addition, nearly three dozen functions were created along with<br />
11 stored procedures and four packages. Of these objects there are a few of particular<br />
interest, while the others were created to perform supportive functionality of the<br />
application, such as performing tax calculations.<br />
The APP_USER_SECURITY package is of interest because often times user’s<br />
passwords are stored in the databases as clear text which could have security<br />
implications. The APP_USER_SECURITY package contains a function that uses the<br />
DBMS_OBFUSCATION_TOOLKIT.MD5 function to hash a password based on the<br />
input of the user’s username and their password. The package body also contains a<br />
function to check whether or not the user entered a valid password. This is done by<br />
calling the GET_HASH function again and verifying that the hashed password stored in<br />
the table is the same as the result of hashing the password entered.<br />
There were a few stored procedures created to aid in the automatic assignment of<br />
sales leads. The P_LEADASSIGN procedure was developed for automatically assigning<br />
leads that were directly entered into the system through the application’s Web interface<br />
or the XML upload interface. This procedure can take one parameter as input, the ID of<br />
the lead (LID). Based on this LID, and through the use of other functions that were<br />
developed, the procedure determines what sales staff is available to take over that lead for<br />
the geographic area the lead is located in. The procedure identifies if the lead is Spanish<br />
speaking and if it is then priority is given to bilingual sales staff. If there are multiple<br />
salespeople available to take the lead then the procedure uses a round robin approach to<br />
determine whom the lead should go to. The round robin approach is based on the time<br />
the salesperson last received a lead. The salesperson that has the longest time span