Problem is that a form that uses the signature widget gets updated and saved every time you press save.
A rule like this: IF Cust.Signature WAS CHANGED then pissOff
will fire EVERY time the Cust Form is saved IF THAT SIG FIELD IS ON IT
AND FROM MY TESTING JUST NOW,
it appears that once you've entered something in a Signature field, then
EVERY TIME you save ANY form of that BO, the rule will fire cause it thinks Signature was changed (even if you're on a form that doesn't even touch Signature).
(I know, thats odd)
I've seen the logger indicate the rule is firing because it thinks Signature was changed.
BUSINESS CASE:
I want to have an object get timestamped/e-signed - like a Delivery receipt.
QUESTION:
If I bring up a form (based on a button click) to record the delivery, then even if I don't physically sign the signature pad, it will still save.
Of course, I need to timestamp this event. So now I have a DateDelivered field populated because the rule will fire "Signature was changed".
I can't use "IS NEW" cause the signature is just 1 field of a delivery record - the record is not "New".
So what happens if a user makes an error - and doesn't really sign it, but presses OK.
Normally, you wouldn't allow someone to re-sign it at a later date, so you wouldn't be able to 'deliver it again' to bring up the signature pad a 2nd time.
--> See, there's no way to really see if the thing "got signed" or just left empty.
Anyone else had issues with doing signatures in Aware?
