Expand my Community achievements bar.

SOLVED

Help with creating a new document

Avatar

Level 2

Hi,

I will have to work on creating a new document from scratch which will serve as a billing statement to a customer.

I have to construct it and I am really confused on how to structure my forms and subforms.

Can any of you please point me to a right place where I can get a good design guidelines?? Or is there anything like a good design for this.

Will the form structuring impact performance. This document can run really long based on the number of transactions.

I am using castor and object to xml mapping and using the data file to dynamically load the data on to pdf.

Since I am going to start this fresh, I want to get the structure and design correct.

Appreciate your time and help.

Thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member
2 Replies

Avatar

Correct answer by
Former Community Member

A document was produced for Designer 7.1 and the principles still apply.

http://partners.adobe.com/public/developer/en/pdf/lc_designer_perf_guidelines.pdf

You can poke around here as well....

http://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm

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