Author Archive: sankumar

LiveCyle Quick Fixes

 

All the latest Quick Fixes of LiveCycle ES2 version and above will be posted regularly on Adobe website.

If you are a LiveCycle customer and encounter any issue , You may reach to QuickFixes page check if the issue is listed here

In case it is listed on the above mentioned QuickFixes page , then contact Adobe LiveCycle support team to provide specific quickfix installer

Announcing LiveCycle ES4

We are proud to announce our next and major release of LiveCycle a.k.a Adobe LiveCycle ES4 with loads and loads of new features.

 

Significant features include :

  1. Mobile forms support
  2. Mobile Workspace application
  3. Forms management capabilities
  4. Integration with Adobe Experience Manager
  5. Extended rights management
  6. Addition of new features in Correspondence Management
  7. Inclusion of new features that are added as CCR on previous releases which will be available for upgrade customers

 

For more information go to official press release of Adobe

Also watch a cool 5 minute video that showcases and explains most of the new features of LiveCycle ES4

 

 

Copy paste of text content from MS-Office applications

LiveCycle Correspondence Management solution users often use text content from MS-Office applications like Word and Excel.

The text content can be copied from MS-Office applications and pasted to Rich Text Editor of Correspondence Management.

Currently the content copying is supported but any rich text formatting applied to the text in external applications like MS-Office applciations will not be retained.

 

If the user copies (to clipboard) below content from MS-Word

 

 

 

 

 

 

and pastes it in CM text content area of Rich Text editor , the text would appear like

 

 

 

 

 

 

Lot of customers are asking us to provide a functionality to copy paste content from MS-Office applications that supports copying of text content along with the formatting. This is currently on the roadmap but there are no fixed timelines when this feature would be available in the product.

stay tuned …….

 

Special characters for Asset Names

 

 

 

 

 

 

 

 

 

LiveCycle Correspondence Management is certified on four different languages (English, French , German & Japanese)

Out-of-the-box deployment of Correspondence Management permits usage of characters of asset names to 0-9 A-Z & a-z via keyboard typing but any language characters can be used in description and comment properties and as part of actual text content as well.

Example :

 

 

 

 

 

 

 

 

 

 

 

 

 

A user can type the characters in description and comment but no in the Name field. An easy way to use such characters for asset names is to type it in description field , copy the word and paste it in Name field but in any customer environment if the organization wants the asset authors to allow usage of such characters for asset names the below steps can be followed to allow users type such characters for asset names.

  1. Log on to CRXDE Lite http://<hostnameOrIPAddress>:<port>/crx/de/index.jsp as administrator
  2. Navigate to content/cm/ and double-click tbxeditor-config.xml on left hand side panel
  3. tbxeditor-config.xml file opens in edit mode on right hand side panel
  4. search for customAssetNameCharset tag
  5. Include the special characters that you would like the users to use for asset names, Eg. If you would like to allow users to use Ф in asset name , then include this character in tbxeditor-config.xml file and save it
  6. In case there is a range of characters that you would like to allow, then specify starting charset and ending charset separated by a hyphen, similar to 0-9

 

 

 

 

 

 

 

 

Now the users are allowed to type new characters that are specified in tbxeditor-config.xml

This blog is just an extension to our online docs about this topic which is 
available at click here

 

In case of any confusion or more questions feel free to post your query on LiveCycle community forums

20 reasons to upgrade to ES3 Correspondence Management solution

 

First version of LiveCycle Correspondence Management solution was delivered along with LiveCycle ES2 service pack 2.

Based on the customer feedback and requirements from various existing and prospective customers lot of new features have been added and existing features have been improved in Correspondence Management solution.

If you are an existing customer of Correspondence Management but are on LiveCycle version earlier to ES3 , Here are the 20 reasons why you should consider upgrading to LiveCycle ES3 Correspondence Management.

If you are a LiveCycle ES or LiveCycle ES2 customer and considering to buy and implement Correspondence Management as well , Here are the same 20 reasons why you should consider upgrading LiveCycle as well in order to make use of latest Correspondence Management solution.

 

(Please click the image to enlarge it and clearly view the content)

 

 

 

 

 

http://about.me/nskumar

LiveCycle ES3 Trial downloads

The trial version of latest LiveCycle release i.e LiveCycle ES3 is available to partners and customers for download at livecycle devnet downloads

The trial download includes

  1. Installer for LiveCycle ES3 & LiveCycle ES3 Data Services
  2. Development tools — Workbench & Designer
  3. Reader Extension test credential
  4. Acrobat X Pro

 

For more information about What’s new in LiveCycle.

LiveCycle ES3 supported platform combinations

Adobe LiveCycle ES3 is supported on around 32 platform combinations (Operating System , Application server , Database , JDBC driver , OS architecture and JDK combinations)

Turnkey install , config and deploy is supported on two Operating Systems viz Microsoft Windows 7 and Microsoft Windows Vista (for evaluation and development purposes)

Full list of supported platforms combinations is available on Adobe LiveCycle help documentation

Adobe announces release of LiveCycle Enterprise Suite 3

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.

 

How to create post-process for Correspondence Management

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

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

Data Dictionary Best Practices

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.

  1. Do not try to create a single Data Dictionary with tens of thousands of elements to cater to the needs of all the correspondences
  2. 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.
  3. 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.
  4. 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.