Disclaimer - Alliance Digital Repository
Disclaimer - Alliance Digital Repository
Disclaimer - Alliance Digital Repository
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
44<br />
table form, as well as the hierarchy of assigning leads. This issue was resolved by<br />
creating a table with multiple columns; the ID column would contain a unique ID, the<br />
NAME column would hold the logical name of the job role, while the remaining columns<br />
would hold the job role ID’s which the named job role can create (CCx columns)<br />
accounts for, i.e. a Sales and Leasing Agent can only create accounts in the system for<br />
Sales and Leasing Agents and Community Managers, this is depicted in Figure 9.<br />
Figure 9 - Job roles and job role creation hierarchy (Darschewski, 2006)<br />
The method used for the hierarchy of assigning leads is similar to the one used in<br />
the JOB_ROLE_RIGHTS table; this is depicted in table form in Figure 10. The JRRID<br />
column is a foreign key to the JOB_ROLE_RIGHTS table’s ID column. The ALx<br />
(where x is a number from 1 to 10) columns refer to the job roles that the JRRID column<br />
can assign sales leads to.<br />
Figure 10 - Assignment of leads hierarchy represented in table form (Darschewski, 2006)