This Blog is moving…

Hi All,
I’m moving this blog to All of the new posts will be published at the new location.

Few reasons why I’m moving:
– I wanted to put few samples as .lca files and account is not allowing me to put these files as attachments.
– Some of the pet projects that i’m working on will need some of my own hosting account so i can publish new things properly. (Stay tuned for this!!!)

Thanks for your support…


November 15, 2009 at 1:22 am Leave a comment

Introducing LC Keywords-Logical Operators– and,or

I was experimenting with xpath expression and found that the ‘and’ and ‘or’ works perfectly as the logical operators.
I’m perosnally so happy to see them working. In few cases it was too hard to configure the conditional routes with just OR/AND joint.

I’ve attached an example to demonstrate a simple usage of ‘and’-‘or’ logical operators. This is the condition that I’ve put in the example.

(normalize-space(/process_data/@Input_Value1)=’555′ or normalize-space(/process_data/@Input_Value1)=’666′) and (normalize-space(/process_data/@Input_Value2)=’777′)

I believe that this is going to make workflow design so much cleaner. Instead of nested conditional routes and 4-5 decision points or set value steps we would be able to do lot more things in few steps now.

I think this is an XPath Explorer feature so is not limited to just route conditions. All of the places where XPath expression is evaluated should be able use these.

Hope this helps to you too!!!

Download the example from here.

July 13, 2009 at 8:09 am 1 comment

Max 2009 Announced

Adobe just announced the details of the MAX 2009. All of the session and lab sessions are also available on the max website.
Few things that I like –

  • Three separate tracks to focus for different type of audience
  • New Livecycle@Max preconference
  • Interesting sessions like – Portal based workspace, How to architect LCES in enterprise, Services.SOA.Cloud roadmap etc…

More details at: Max Blog

June 18, 2009 at 3:52 am Leave a comment

Form Pre-populate via Render service (delayed)

Hi All,

I was suppose to post easy techniques on how to pre-populate forms via LiveCycle’s Render service but unfortunately it is taking longer than what I expected. This is the story so far… Please comment if you are aware of this and enlighten me around the changed behavior.


I used the customized render service till LC 8.0.1 SP2 and what we get in dataDoc variable of the Render service is xdp data which had the whole form specific XML structure. But I’m finding that in LiveCycle 8.2 SP2 the dataDoc contains the xdp data but ONLY the Root element of form data is present.

The issue: This results in stalled operations (exception) as the elements that I want to populate does not exist.

The strange thing:

The most strange thing that I have seen is related to where the ‘caller’ orchestration was developed. So if your orchestration which has xfaForm variable was created on LC 8.0.1 then the dataDoc variable will have the xdp data with the whole and empty form data section in it. BUT….. if you touch that variable or re-create that xfaForm variable on LC 8.2 then you’ll start getting the blank form xml section in xdp data (of dataDoc) variable of render service.

Please let me know if anyone has seen this before and knows if this was intentional in LC 8.2 or it is a reported/unreported bug.

stay tuned for the pre-population.. I’ve decided to post a series of two articles to discuss the strategy that I think can work nicely.

June 10, 2009 at 7:30 am Leave a comment

Styling in Task Instructions

This is really exciting!! I knew that this can be done in LiveCycle 7 but never tried it till now in LiveCycle ES. Ok.. let me describe what it is.

What it is?

I found out that we can add styling to the Task Instructions that apear in Workspace. This means that we can have Red font, Bold statuses/instructions based on the task description that we put in Assign Task step of the orchestration.

Why you need it?

Let’s say for example, A Task is deadlined and you wish to put task status/something else in Instructions field which can stand out form the rest of the text. Having something like ‘Deadlined’ status in red with other instructions can be a BIG step forward for someone who works on workspace interface everyday.

I’ve also noticed that the Task Instructions field on TaskManagerEndpoint also ‘likes’ the styling. This means that the Cards or Grid view of Start Process section will also show pretty colors and styling if needed.


May 25, 2009 at 3:25 am 2 comments

RichText tricks for TextField in Designer

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


May 20, 2009 at 2:35 am 13 comments

Workspace URL parameters

I recently noticed that LiveCycle workspace URL has few parameters which would be really helpful in LC projects.

The format to livecycle workspace URL is something like this:

http://%5Bserver name]:[port]/workspace?[parm]=[value]

  • [server name]is the name of the LiveCycle ES server
  • [port] is the server port used for LiveCycle ES
  • [parm] is the name of the parameter
  • [value] is the value of the parameter

Three possible types of URL that we can use with the help of URL parameters are:

  1. URL pointing to a Task (Work item in To-Do list)
  2. http://localhost:8080/workspace?taskId=100

  3. URL to open workspace with any of the three tabs of workspace –
  4. http://localhost:8080/workspace?startPage=startProcess

  5. URL to open a form from Start Process page to kick off a new process –

http://localhost:8080/workspace?startEndpoint=%5Bservice name].[endpoint name]

The last one is in fact the most interesting one as you can publish the links on company portal and that will straight away open the relevant form so everyone wouldn’t have to find the form in Start Process page.

More details are at LiveDocs

April 23, 2009 at 12:59 pm 1 comment

Older Posts

Recent Tweets

Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Recent Posts


The fine print!!

The views on this blog are my own and don’t necessarily represent my employer's views, strategies or opinions.


July 2018
« Nov