Recently in LiveCycle Category

I have performed a few ES to ES2 Migrations and there isn't too much information out there on what is involved in the process. Here is an outline based on my personal experience:

The following link gives you the ability to step over the first few manual steps to the migration process: Adobe Labs

Have a look at the following blog post as well as the captivate video that gives an overview of the migration process if its done from scratch :  LiveCycle Expresso

This should serve as a starting point to your migration process.A few things to look out for: 

1. XfaForm variables are no longer supported in ES2. However, you will be able to run such processes in deprecated mode but not for too long. 
2. The concept of application based projects has been introduced in ES2. 
3. The concept of a repository is no longer there in ES2. The applications refer to their own local resources in the applications or you can create an application that contains all the resources/ Assets etc. You must export all your assets from the repository manually and import them into a new application in ES2. 
4. You must configure all the paths to the assets in the repository to the application containing your artifacts. 
5. If you have an assembler service in your process, you must re-configure it to use a document variable instead of a string (this has not been document anywhere and is a bug).
6. If you have any custom components, you must export them manually from the ES server and import them into ES2 before you migrate the processes. 
7. Finally, you must remove all the deprecated services and replace them with the ES2 versions. 
8. I won't recommend the approach of creating an ES LCA and importing into ES2. This has caused a lot of issues for me in the past. 

Thats just my 2 cents. If you have any questions, or require assistance, please leave a comment on my blog.

Now all you LiveCycle documentation hunters can look at a single location to find all LiveCycle related information....on your desktop...thats right...and its actually true.

Adobe released Tour De LiveCycle yesterday, a comprehensive AIR app that locks all aspects of LiveCycle documentation on your desktop. It will remind you of Flex explorer in its look and feel but encompasses videos, presentations, tutorials and hands on examples on all aspects of livecycle (Data services, BAM, Workbench etc) .

It can be downloaded here:

I have been struggling with data manipulation with rich text fields for a while. For those who aren't familiar with rich text fields in LiveCycle, they are simple text fields with the data format = XHTML.

This allows the text field (text area) to work like Microsoft word. The end user is able to edit the text, make it bold, underline it, hyperlink web addresses etc etc.

In my case, i had to concatenate 2 pieces of rich text fields into a rich text area. The usual rawValue and formattedValue XFA properties loose the formatting if used for rich text areas.

I have attached a sample XDP that shows you how to do it  "properly".

Armaghan.
RichTextCopyExample.xdp

Time to bust a myth. I'll call it LiveCycle Myth 101.1

While working on a process orchestration today in a truly team oriented setup, we were working on a single version of a process in bits and pieces. Great progress was made, happy hour came early to work today but then someone saved had an older copy of the process open on their computer...and they decided to save it........the horror....the pain......but wait, this is livecycle we are talking about....its smart...its fancy....it must have stored the previous copy we were working with in the database...it must have...

So we went ahead with our quest for the old process, tore apart the database....and found the table that contains the process orchestrations. We found our process....the jubilant team roared, the happy hour was back....and then we diffed the copy from the database with an exported copy of the process....and it went quiet in the room....it was the same process XML.

Moral of the story:
Keep a backup of the current version, LiveCycle will not save the day everyday, sometimes it takes regular good old common sense. Export a copy of your work and save it in the SVN or better yet, create a new version of the process everytime you reach a milestone. This way, the database will save each version of the process!

Share what you learn...and Happy Coding :)