Expand my Community achievements bar.

SOLVED

PDF Forms, JavaScript / FormCalc and Security

Avatar

Former Community Member

Hello!

A client wants to use PDF forms (around 2000  forms) in their company, most of them using JavaScript or FormCalc scripts, but today their employees (thousands) are not  allowed to activate JavaScript in their computers. Obviously this will  have to be changed.

They say their security people are afraid this could open security breaches...

Please, is there a way this can be solved using LC Rights Management?  Or any other solution?

Thank you very much for any ideas!

Marcos

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Marcos

Enabling or disabling JavaScript is a "global" (it's either on for all documents or off for all documents) setting at the application (Reader or Acrobat) level.   Protecting a document with Rights Management will have no affect on this setting.

Regards

Steve

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Marcos

Enabling or disabling JavaScript is a "global" (it's either on for all documents or off for all documents) setting at the application (Reader or Acrobat) level.   Protecting a document with Rights Management will have no affect on this setting.

Regards

Steve

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