In the theme of rapid application development. I am going to put LiveCycle Enterprise Suite 2 (ES2) up against the ‘Slap Chop’, with a series of blog posts over the next month (check out the category ‘ES2 Highlights’). I think you will see that we are far superior. Here is the competition:
Archive for the ‘General’ Category
Hey there LiveCycle developers,
You might have noticed that I recently re-branded my blog. Adobe recently launched the Adobe LiveCycle Cookbook on the Adobe Devloper Connection portal — So I have re-branded my blog so that is does not conflict.
At the bottom right of most activities, you will see a lightning bolt icon, simply make a new route off of the icon and choose the target exception you would like to handle. If the operation fails the exception route will be followed.
As an example we will catch an error that may occur during the application of Reader Extensions Usage Rights. This same technique can be used for all LiveCycle activities that have the potential to raise errors.
Here is a completed example with LCA: catchexception
Cooking instructions for creating a fault route:
- Identify the activity in your process that you would like to provide a fault route for
- Click on the lightning bolt icon at the bottom right of the target activity, then drag to create the fault route.
- When prompted select the exception that you will like to handle
Adobe is now offering developers subscribed to the Adobe Enterprise Developer Program access to their own virtual instance of LiveCycle ES through LiveCycle ES Developer Express: LiveCycle ES Developer Express
This is a hosted version of LiveCycle offered through Amazon’s cloud computing system.
There are two primary submit types that work out of the box in LiveCycle Designer 8.x, Email and HTTP submit.
If you don’t want to use an email client to submit form data, HTTP is a good alternative. Typically a servlet, or jsp is used to receive the submission. This is a straight forward process and there are numerous examples posted on the web.
SOAP: It is possible to submit the form data via SOAP but it is involved. A simple alternative is to submit the data via HTTP to a web server and have the web server make a SOAP call on your behalf.
Here is an excellent article on how to implement a solution using Cold Fusion and HTTP submit: http://www.adobe.com/devnet/livecycle/articles/designer_coldfusion.html
The Adobe Reader Team would like to know what all of you want most in the next versions of Adobe Reader. Faster? Smaller? Easier to use? Feature additions? OK the way it is?
Please complete the following survey to contribute to the future of Adobe Reader:
Click Here to take the Adobe Reader Survey
The survey should take 5 minutes or less to complete. The survey will run until January 31, 2009.
Please ask your friends and colleagues to take the survey too.