Expand my Community achievements bar.

SOLVED

Digital Signature prevents submit via email and print

Avatar

Former Community Member

A form works perfectly well until I insert a digital signature into a digital signature box.  So if the digital signature box is empty the buttons still work but sign the wrecked thing and nothing works anymore.  I have created new signatures but nothing seems to work.  Can you shed any light on this?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The problem is that the "Lock Fields After Signing" property is enabled (see attached screen shot).  Buttons are considered fields, therefore when the signature is applied, the buttons are locked and can no longer be clicked.  To fix this you can disable the property, or better yet create a field collection and select the specific fields that you want to lock if a signature is applied.

Regards

Steve

View solution in original post

4 Replies

Avatar

Former Community Member

Can you post the form that is causing the problem?

Thanks

Steve

Avatar

Former Community Member

Thanks.  I am in a large corporation and I am beginning to think it may have something to do with where the signatures are stored. 

Avatar

Correct answer by
Former Community Member

The problem is that the "Lock Fields After Signing" property is enabled (see attached screen shot).  Buttons are considered fields, therefore when the signature is applied, the buttons are locked and can no longer be clicked.  To fix this you can disable the property, or better yet create a field collection and select the specific fields that you want to lock if a signature is applied.

Regards

Steve

Avatar

Former Community Member

"Ker--clink"  The sound of pennies dropping.  Thank you.  I should have known that.  I very much appreciate your help

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----