• If you have found this page while struggling to get something to work in LiveCycle PDF form then you can’t afford to ignore this article .

• If you are thinking of creating more than 2 PDF forms for your organisation then this post has something that can save you days, weeks and lots of coffee (Saves you $$$$) !!!

Anyone who has created PDF forms in Adobe LiveCycle designer can tell that a complex, fully functional, good looking form with lot of fields can be a challenge to get it right in rapid development environment.

Adobe LiveCycle Designer is a powerful tool and has features to create really amazing forms but it has its downside as well. It can be a serious learning curve. This can limit the productivity as only few guys in the IT or development department can do it for business. This doesn’t scale very well in current economic time as well.

Before I introduce what I think is the easiest and  fastest way to create powrful PDF forms, Let me highlight what I think is causing the most pain when we have to create PDF forms that work with LiveCycle ES or any other data capture and processing system.

Reason 1: No Pain, No Gain of form requirements saga

Getting the PDF form specification with details like field validation, mandatory logic, show-hide logic,  tooltip text, look and feel details is a mammoth task. It’s crucial to get it right BUT it is a challenging to pass on the same requirements to developer. (Imagine at least a 5 pager form with minimum of 100 fields and different look and fill for print and online usage)

Reason 2: No direct visibility to business into form development activity

Unless the business analyst or a subject matter expert sits next to the form designer, it is going to be hard to get a decent look and feel in place in the first iteration. Field placement, correct tooltip text, field grouping with correct title on section etc will just take up lot of time before a final version of the form is released. And then comes the small requests like can you change tooltips as per attached document as legal or usability team has amended them!!? So on and so forth….it just happens..right?

Reason 3: Form development in a team

Forms development in team environment with templates and libraries being shared has its own challenges. Thanks to fragments, so we can update every form that uses it by just opening it and saving again in Designer. But what if a library component needs a change and you have used it 100 times in 20 forms?? The answer…..Outsourcing/hire a  housewife or uni student!!!! In short, sharing of library and template components, maintaining them and making sure that forms have the most up to date library components is a big exercise for any development team.

Reason 4: Compliance to standard L&F and bulk update

I think the reason 4 is self explanatory.

And, my list goes on and on and on….. Over the years I’ve seen so many things that I think can be tackled in much more better and cost effective way. Finally I use a tool that helps me to manage these in a more elegant way.

The Solution:

Avoka SmartForm Composer

I’ve been fortunate enough to see this product maturing from its inception. The amazing simplicity this product brings into the SmartForm development is never seen before.

It would be just too long blog post if I had to go through my fav features of this tool. But fortunately Howard and his team has put together videos to introduce the features and SmartForm Composer’s capabilities to give you an idea of this tool. They can be found at here.

I would definitely recommend to watch those videos. It might just change your perception on how easy and quickly you can get a fully functional and yet powerful form without minimal scripting.

Feel free to comment on this post if you want to know all of the reasons why I would prefer this tool over creating a form in designer. I’ll happily post a new blog entry with them.

This post describes a technique to set rich text content into a Textfield of a form that was designed in LiveCycle Designer ES. Thanks to Paul Guerette who helped me out to understand this few months back.

There can be two scenarios in which you might want to set content into a rich text supported Textfield.

1. User types the rich text content into a text field and you wish to copy that to another Textfield.
2. LiveCycle ES server/some other way you wish to set rich text content into a form field. (Form pre-population scenario)

Where is rich text data in a text field?

When user types plain text in a pure Textfield (field format: Plain Text Only) then the data is set/get from rawValue property. BUT if the Textfield is having Rich Text as the field format then the data is store at .value.exData

How to check what the rich text data look like under the covers?

I use email submit button on a simplest form to see the XML that gets created for submission.

If you wish to do this then:

1. Create a simple dynamic PDF form and put a text field with Rich Text format set to it.
2. Drop a Submit button and put mailto:someone@abc.com as submit URL
3. Open this sample form in Preview mode type some text with rich-text formatting (Bold, Italics etc)
4. Hit the email submit button you would be able to see the exData content as the child element of your Textfield.

Now let’s look at above mentioned two scenarios in details:

Scenario 1: User types the rich text into a field and we want to copy that to another field.

How to copy rich text from one Textfield to another Text field?

Steps:

• Get the content out of first text field by this java script

txtInputTextArea.value.exData.saveXML();

• Set that value in the destination Textfield’s exData property.

txtOutput1.value.exData.loadXML(userEnteredRichText,1,1);

Scenario 2: We need to pre-populate the form and the rich text data is not typed in (received from web service call or out of database etc..)

How to set rich text data into a Textfield?

Steps:

• Receive the markup data. eg. Hi <b>John</b>,<br/>Please find application-<i>111</i> details below.
• Have exData ‘envelope’ ready in your form and inject the received markup data. (You may have to replace &lt; &gt; values with < , > if received data is having that)
• set the ‘envelope’ + data into Textfield’s exData element.

txtOutput1.value.exData.loadXML(cleanedValue,1,1);

Note:

What is ‘envelope’ which is mentioned in this example/blog entry?

I mentioned ‘envelope’ in Scenario 2 explanation which is something that allows me to insert markup data in a form that Textfield is expecting for rich text support.

What I have done in my sample (attached/linked below) is to have another Textfield storing this exData section with namespaces in it. This is what gets generated behind the scenes when user types the rich text content in Textfield.

I have a ‘ccc’ string in this whole block where the actual data(markup data) is needed for the Textfield to show that correctly.

So in my form script I use this ‘envelop’ to store the exData block and then via script I replace the ‘ccc’ value with the markup data that I receive. And then I use this merged xml block to set to the Textfield’s exData property.

Download Sample implementation:

Use this PDF file that has both of these scenarios implemented as a sample.

Richtext in Textfield Sample