Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Import comments (XFDF) to a PDF document

Avatar

Level 2

Hi all,

I have a LiveCycle ES2 process where I would like to import comments (available as an XFDF String/Document) to an existing PDF File (flat).

I have already tried the FormDataIntegration.importData service, but without success. The comments do not appear on the PDF file.

Could anybody advise how this is possible?

Thanks in advance!

Paul

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Comments are not considered data so importData is not what you want. In the Assembler service you can invoke a DDX set of instructions that will allow the impoort of comments.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Comments are not considered data so importData is not what you want. In the Assembler service you can invoke a DDX set of instructions that will allow the impoort of comments.

Paul

Avatar

Level 2

Yes right this should do it.

Thanks for the response!

Paul

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