Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Adobe LiveCycle (Archived)

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Read More & Register today!

SOLVED

Adding Attachments From Designer

I was wonder if it is possible to attach a document to my PDF inside LiveCycle Designer. I've tried attaching via Acrobat Pro, but as soon as I reopen and save in LiveCycle Designer the attached document gets deleted. To be clear, I want this document pre-packaged with my PDF. It's not for users to attach something.

Thanks.

659

1

1 Accepted Solution

Correct answer by

Designer will not allow you to add an attachment. You can save the PDF out of Designer then add the attachmnet in Acrobat, hen distribute from there.

Paul

View solution in original post

323

0

Jump to reply

1 Reply

Correct answer by

Designer will not allow you to add an attachment. You can save the PDF out of Designer then add the attachmnet in Acrobat, hen distribute from there.

Paul

324

0

Jump to reply

Related Conversations

Lifecycle Designer, add instanses to table Solved

Solved

1.4K

0

3

How to keep time from constantly updating Solved

Solved

1.1K

0

2

I want to create a field that includes information from 2 other fields Solved

Solved

1.5K

0

6

Populate a large paragraph from a drop-down selection Solved

Solved

717

0

1

How to create Rows dynamically from Code without binding

1.0K

0

1

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