This is a follow-up for my other thread titled "Making attachments become part of the form." Since I'm forced to use regular attachments, I'd like to know if there's a way of locking all attachments when you sign the main form. I've looked around online but haven't found anything yet. Is this possible?
No the attachments are treated as separate entities. The signature will include the attachments so if the user changes an attachment the signature will show a red X indicating that something has changed in the form (attachment or main form).
Well, let's say I have my main form (Dynamic) and three other PDFs (Dynamic.) Is it possible to sign the main form and make it impossible to change fields in the attachments?
No the attachments are treated as separate entities. The signature will include the attachments so if the user changes an attachment the signature will show a red X indicating that something has changed in the form (attachment or main form).
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]
----
