Posts in Category "Documentation"

LiveCycle Home

There are numerous end user or administrator user web UIs for LiveCycle Enterprise suite  :

  • Correspondence Management Solution
  • Forms Manager
  • Workspace (Flex & HTML)
  • Reader Extensions
  • PDFG
  • Rights Management
  • Process Reporting

An administrator works with many of these web UIs and it is little difficult for administrator to remember the URLs for all these applications and prior to ES4 SP1 there was no single place for a specific user to see what all LC applications that particular user has access to.

In LiveCycle ES4 SP1 we have introduced LiveCycle Home or LiveCycle landing page – which is a single page that displays all the applications that any specific logged in user has access to and can launch those applications from that landing page, SSO is integrated so that the user is not challenged to provide username/password after the first login.

LiveCycle Home sample image :

LiveCycle Home

LiveCycle Home

One can log on to LiveCycle Home by hitting any of the following URLs :

  • http://servernameoripaddress:serverport/lc
  • http://servernameoripaddress:serverport/lc/home
  •  http://servernameoripaddress:serverport/lc/welcome

 

This page can also be customized to add URLs to any other applications that are integrated with LiveCycle

 

There are some self service options for learning (links to help resources) , LiveCycle Communities (Forums & blogs) , TroubleShooting (System Info Service) and link to support (to raise any product issues or contact support for help)

Note : This functionality will be available to only those users of LiveCycle who use CRX based components like Forms Manager or Correspondence Manager.

 

For more information about LiveCycle Home go through documentation on Adobe’s help

 

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

ADEP CM : Documentation

 

Adobe® Digital Enterprise Platform (ADEP) offers an integrated set of capabilities and technologies that enable organizations to create Customer Experience Management solutions.

ADEP comprises of two servers :

  1. Document Server :  All the services related to documents and process (of earlier LiveCycle) are now part of ADEP Document Server
  2. Experience Server : All Solutions (applications) and content are part of Experience Server [ Solutions like CM & ICR used Alfresco based Content Services to store all the content in earlier versions , now they use Day’s [now part of Adobe] CRX content repository to store all the content]

 

Architecture diagram :

For more information on understanding ADEP architecture refer documentation

 

 

Installation :

Installation of Experience server is as simple as a double click.

Refer to installation document for Experience Server for system requirements and installation steps and steps to configure Experience Server to work with Document server

You can watch following video for the same

 

Release Notes :

Before getting started with the ADEP CM , please spend sometime to go through Release Notes for known issues

 

API Reference Documentation :

What CM includes?
The following picture explains what CM includes :
Solution Guide :
The Correspondence Management Solution Guide provides guidelines to implement correspondence management solutions.
Developer Guide :
For developers who wants to extend the OOTB CM solution to add some new capabilities , they can go through Developer guide
Correspondence Management solution comprises of following three building blocks :
Click on above links for Technical guides of the CM building blocks