Expand my Community achievements bar.

SOLVED

Submit not locking form

Avatar

Level 2

I have a form that when the submit button is selected, it locks a subform and sends a pdf doc.  However when I open the document it unlocks the form allowing for edits. How do I prevent this from happening?  I'm LC Designer ES 8.2.1

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The state of the form is not being saved by default .....in Designer under the File/Form properties/Defaults in the "Preserve Scripting chnages to form when saved" choose the Automatically option.

Paul

View solution in original post

4 Replies

Avatar

Former Community Member

Did you add script to lock the sub-form upon submission? Field locking is not default behaviour.

If you want the form to be non-editable by users subsequent to the original save, you will either have to flatten the document (make it not interactive basically) or add script to make fields read only.

Steve

Avatar

Level 2

Thanks for the swift reply, greatly appreciated. With my limited amount of knowledge, I put the code there and it works fine on the screen.  It's more than possible that i did not do it right.  I put the following code main.access = "readOnly"; I've tried it on the click and preSubmit events, but same results.  How would i use the flatten feature??  Thanks

Avatar

Correct answer by
Former Community Member

The state of the form is not being saved by default .....in Designer under the File/Form properties/Defaults in the "Preserve Scripting chnages to form when saved" choose the Automatically option.

Paul

Avatar

Level 2

That worked great!.  Steve and Paul thanks for the assistance.

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] ----