Skip navigation
Phoenix_Guru
Currently Being Moderated

Best Design approach for reusability

Apr 5, 2012 7:05 AM

Tags: #design #large_files #xdp #reusability

Hi Folks,

 

I have around 80 Forms to design, which are simple letters. The only thing that changes in those forms is the body of the letters.
The Logo, salutation, Address Line and footer remain the same.

 

I am trying to figure out the best way to design these forms. Following are the approaches I have considered:

 

1. Having 1 XDP and just making the body text Dynamic - One major con would be that I would not be able to retain the bullets, numbering and formatting of the body text. Unless someone suggest a way to do that.

 

2. Having 80 XDPs and create fragments for the repeating fields. - Would need effort to do 80 XDPs.

 

3. Having 1 giant XDP with 80 pages and hide the pages that I don't need. - Would be too bulky and inefficient I guess.

 

Which one would be the best way to proceed? Are there any other approaches that I might want to consider?

 

Is there a way to make the body part dynamix and still retain the Formatting properties of the text?

 

 

Thanks,

Phoenix

 
Replies
  • Currently Being Moderated
    Apr 5, 2012 8:40 AM   in reply to Phoenix_Guru

    See if one read only text box set as readonly, multiline entry, rich text formatting will work with option 1.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 5, 2012 1:51 PM   in reply to Phoenix_Guru

    I created a form with text field as I described. I went into Word and created a bullet list with two rows. I copied that and pasted into the default value for the text field. I clicked on the field then the XML Source tab. This is what I see for the value:

     

               <value>
                  <exData maxLength="2000" contentType="text/html">
                     <body xmlns="http://www.w3.org/1999/xhtml" xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/"><p>•<span style="xfa-tab-count:1">         </span>Line 1<br/>•<span style="xfa-tab-count:1">         </span>Line 2<br/><br/><br/></p></body>
                  </exData>
               </value>

     

     

    Looks kind of like HTML. Try saving one of the documents as HTML and see what happens if you bind that. You could start with your option 3 except you just need separate text boxes. Write some script to loop through the text boes and save off the rawValue to bind to the final single form. I am assuming the raw value with contain what I see on the XML Source tab.

     

    You probably want you final text box to be auto height and allow page breaks.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 10, 2012 8:31 AM   in reply to Phoenix_Guru

    I don't know if this will help or not but I've seen talk about getting xhtml into LiveCycle. If you do a search on the forums here you should find a few hits.

     

    Here's a couple of quick links that I found:

    http://blogs.4point.com/armaghan.chaudhary/2009/05/working-with-rich-t ext-fields-in-livecycle-es.html

    http://blogs.4point.com/rob.mcdougall/2009/01/sending-rich-text-to-liv ecycle-es.html

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points