J
Jamesy
Hi folks,
I am currently working on a travel request form. I've got a bunch of
data-sources populating this that and the other based upon various pieces of
input. The part that I'm stuck on though is the routing of the request.
The idea is that the user submits the travel request. The request is then
routed to the approver who either approves or rejects. If it's a rejection,
then a "Reason why" needs to go back to the submitter. If it's an approval,
then the whole whing - with a few extra fields filled in by the Approver -
needs to be routed to the travel folks.
Sounds so easy doesn't it! But I am totally stumped. Any help would be very
gratefully received.
TIA
I am currently working on a travel request form. I've got a bunch of
data-sources populating this that and the other based upon various pieces of
input. The part that I'm stuck on though is the routing of the request.
The idea is that the user submits the travel request. The request is then
routed to the approver who either approves or rejects. If it's a rejection,
then a "Reason why" needs to go back to the submitter. If it's an approval,
then the whole whing - with a few extra fields filled in by the Approver -
needs to be routed to the travel folks.
Sounds so easy doesn't it! But I am totally stumped. Any help would be very
gratefully received.
TIA