Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Read-only Fields Become Unlocked When PDF is Re-Opened

Avatar

Level 2

I created a quote form which is has multiple buttons on it.  The buttons perform numerous actions such as adding/removing rows, adding/removing columns, etc.  There is a 'Finalize' button at the bottom of the form that locks all text fields and hides all buttons so that they cannot be edited by the customer when the quote is sent to them.

The problem occurs when the form is finalized, saved, then re-opened.  All of the buttons become visible again and text fields become editable when the PDF is reopened.  Is there a way to keep buttons hidden and text fields as read-only?

Thanks.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The "state" of the form is not being saved automatically. Under the File/Form Properties/Defaults make sure that the "Preserve scripting changes to form when saved" radio button is set to automatically.

paul

View solution in original post

3 Replies

Avatar

Correct answer by
Former Community Member

The "state" of the form is not being saved automatically. Under the File/Form Properties/Defaults make sure that the "Preserve scripting changes to form when saved" radio button is set to automatically.

paul

Avatar

Level 10

Hi,

In the File > Form Properties menu opens the dialog window. Go to the Defaults tab and check that the "Save script changes" is set to 'Automatic'. This will make sure that changes to the form from script changes will be saved with the form and honored when the form is reopened.

Niall

...snap...

Avatar

Level 2

That did the trick.  Thanks to both of you...& thanks for the quick response.

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