Electronic signatures

Yahoo Archive
1
Its awful and hacky but you could write to a file on the server... since you
are only using it for a second while you verify it should work ok. Just make
sure you have a Unique ID in case more than 1 authorization needs to happen
at a time. Or you can be "real creative" and create a new file per
authorization since you are deleting them when u are done anyways.

*Jose C Gomez*
*Software Engineer*
*
*
*NEED HELP WITH AN EPICOR ISSUE THAT CAN NOT BE SOLVED ON THE LIST?
CHECK OUT MY NEW BLOG <http://www.usdoingstuff.com> OR CONTACT ME DIRECTLY*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Sun, Jun 5, 2011 at 9:48 AM, CarlH <carl.heeder@...> wrote:

>
>
> We're being asked to include electronic signature process in several areas
> of Vantage 8.03
>
> So far, I've been able to store an "authorization" code in each user's
> account and, when needed, asked the user to enter that number in a darkened
> field on a data input form that is linked to a UD field in one of the
> related tt tables, then with a pre-BPM, verify that the input value matches
> the user's "authorization" code and delete the value from the UD field.
>
> This works great and is acceptable to our quality people.
>
> But with PO authorizations, there are no UD fields available nor are there
> any unused data fields that I could borrow.
>
> Does anyone have any ideas other than going to E9?
>
>
>


[Non-text portions of this message have been removed]
2
We're being asked to include electronic signature process in several areas of Vantage 8.03

So far, I've been able to store an "authorization" code in each user's account and, when needed, asked the user to enter that number in a darkened field on a data input form that is linked to a UD field in one of the related tt tables, then with a pre-BPM, verify that the input value matches the user's "authorization" code and delete the value from the UD field.

This works great and is acceptable to our quality people.

But with PO authorizations, there are no UD fields available nor are there any unused data fields that I could borrow.

Does anyone have any ideas other than going to E9?