Adobe has announced release of Adobe® LiveCycle® Enterprise Suite 3 (ES3) software on March 13 2012. Here is the link to press release
Document and DataServices capabilities of Adobe Digital Enterprise Platform (ADEP) are not part of Adobe LiveCycle ES3
Click here to access Online help documentation for ES3 is available
A link will be provided soon with details to download a trial for those who would like to try the new features of Adobe LiveCycle.
There are lot of new features in various document services of Adobe LiveCycle ES3 and it’s Correspondence Management Solution.
Each letter in Correspondence Management can be associated with a post-process. A post-process is nothing but a LiveCycle orchestration with a specific requirement on the input/output parameters.
Sometimes one may wonder that the orchestration that one has created on LiveCycle does not appear in the drop-down of Letter Editor
If the orchestration has two input parameters i.e inPDFDoc , inXMLDoc & one output parameter i.e redirectURL then it will appear in the Letter Editor drop-down.
LiveCycle Correspondence Management Post-Process
The above picture shows a sample post-process , The variables highlighted in a red rectangle are mandatory and are minimum requirements for Correspondence Management to recognise the orchestration as the one which is intended to be used with Correspondence Management Solution
One can add additional variables depending up on the logic and operations the orchestration does.
Fore more details on creating post-process visit our online help docs
Correspondence Management DataDitionary provides a representation of the underlying data structure of a complex backend enterprise system in a simple and user-friendly manner which business users can easily understand.
In any enterprise implementation of Correspondence Management usually middle ware developers work on creation of data dictionary.
We get requests from our customers to understand the best practices for creation of DataDictionary.
The answer is try to Keep It Simple.
- Do not try to create a single Data Dictionary with tens of thousands of elements to cater to the needs of all the correspondences
- If there is a possibility to create multiple data dictionaries by logically separating the correspondences based on business units / business needs , prefer to create multiple data dictionaries.
- If a single complex data dictionary is created (even if there isn’t a real need) , there would be some trade-off in the form of performance for some operations like Publishing the datadictionary and preview of letters that use this data dictionary.
- Do not try to over complicate the data dictionary by creating too many levels down the hierachy and do not even use a DD which is completely flat.
In case of any confusion or more queries , feel free to post your queries on Adobe LiveCycle forums