H
HanSolo
I am building a recruiting transactional database where I need to be
able to control the types of recruiting transactions that can occur,
based on the stage of the process the recruiter (recruiter being the
user) is in.
For example, a recruiter must first enter a transaction of "activate a
job requisition" prior to entering a transaction of "interview a
candidate" or "inactivate a job requisition". I've set up my
transaction action and reason table so that there are over 60
transactions that could occur, and have assigned a numerical value to
each transaction as I'm thinking that there must be someway to
manipulate this for my purposes (e.g. "activate a job requisition" has
a numerical value of 1, "interview a candidate" and "inactivate a job
requisition" have numerical values of 30, as such I'd like to be able
to say that you can't enter a transaction with a numerical value less
than the last transaction). Hopefully I'm on the right track and that
this makes sense, nonetheless I'm stumped. Please help!!
able to control the types of recruiting transactions that can occur,
based on the stage of the process the recruiter (recruiter being the
user) is in.
For example, a recruiter must first enter a transaction of "activate a
job requisition" prior to entering a transaction of "interview a
candidate" or "inactivate a job requisition". I've set up my
transaction action and reason table so that there are over 60
transactions that could occur, and have assigned a numerical value to
each transaction as I'm thinking that there must be someway to
manipulate this for my purposes (e.g. "activate a job requisition" has
a numerical value of 1, "interview a candidate" and "inactivate a job
requisition" have numerical values of 30, as such I'd like to be able
to say that you can't enter a transaction with a numerical value less
than the last transaction). Hopefully I'm on the right track and that
this makes sense, nonetheless I'm stumped. Please help!!