K
krozar
Right now we're sending e-mails from person A--> B --> C --> D where A
submits, B & C approve, D processes. This seems quite hectic/inefficient.
Here's how I'd like to do it (we use microsoft exchange server):
Person A submits to general Mailbox
Persons B and C -- who have permission to the Mailbox folder -- sign off
Person D then processes.
The problems:
-Person C & D would have to know when the message is ready for them to sign
off
-The final message user D prints out, would have to print out some sort of
verification where the e-mail of the user is recorded by the system, i.e.,
proof that that user signed off
-There should only be one total e-mail. When I open that folder, I only
want one message/e-mail per submission from person A.
I've looked at voting & tracking, I've looked at posting to a folder, but I
keep coming up empty. I want a clean, low-volume final product that would
qualify under S/OX as proof of verification by B & C.
Help!
submits, B & C approve, D processes. This seems quite hectic/inefficient.
Here's how I'd like to do it (we use microsoft exchange server):
Person A submits to general Mailbox
Persons B and C -- who have permission to the Mailbox folder -- sign off
Person D then processes.
The problems:
-Person C & D would have to know when the message is ready for them to sign
off
-The final message user D prints out, would have to print out some sort of
verification where the e-mail of the user is recorded by the system, i.e.,
proof that that user signed off
-There should only be one total e-mail. When I open that folder, I only
want one message/e-mail per submission from person A.
I've looked at voting & tracking, I've looked at posting to a folder, but I
keep coming up empty. I want a clean, low-volume final product that would
qualify under S/OX as proof of verification by B & C.
Help!