Users of Adobe LiveCycle quite regularly interact with PDF documents. Some examples are:
- Rendering customised documents for print purposes
- Creating PDF forms for on- and offline use to collect data for further processing
- Rendering pre-filled PDF forms to send out to customers/users for completion and physical signature etc.
In a lot of cases those PDF documents are what’s called an XFA-based PDF form/template. XFA is Adobe’s XML Forms Architecture and a proprietary technology to describe form information. I spare you the technical details, but essentially quite often those XFA-based forms get wrapped into a PDF document, this is done by rendering the XFA information over a PDF page background.
Read the issue and steps to fix it at this blog.
Read about what is included and find a purchase link in this blog post.
There are numerous end user or administrator user web UIs for LiveCycle Enterprise suite :
- Correspondence Management Solution
- Forms Manager
- Workspace (Flex & HTML)
- Reader Extensions
- 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.Read the complete post at LiveCycle blog
Read the complete post at LiveCycle blog
The ‘DO-NOT-DELETE’ tracking tag that is added to the end of a reply-to-complete email should be hidden from end users if possible.
When an HTML email is sent, the ‘DO-NOT-DELETE’ tag can be easily hidden by using a CSS style sheet to hide that section of the email.
For a detailed explanation, see Khushwant Singh's blog post.
A common question relates to file size when creating PDF forms or any PDF documents. When using Adobe LiveCycle Designer and saving a form as PDF the fonts used are embedded by default in the PDF. This can cause quite heart stopping file sizes even with very simple forms. One way of making a smaller […]
To read the complete post, visit eFormsFactory blog
In Correspondence management we can pass user filled data into a Letter or map the values from the data specified in the template. In a letter template various fields and variables can be added in the form of layout fields ,data dictionary elements and place holders. When the letter is rendered in the create correspondence screen all the user filled editable variables show up on the left side under the data tab. The order of such fields and variables are governed based on these rules..
1. Order of fields, DDEs and PH ( position as in PDF from left to right and then top to bottom)
- In case of text, position of DDE/PH variables are calculated from left to right and then top to bottom.
- In case of Condition, position of DDE/PH variables used in expression comes first (alphabetically sorted ) followed by the variables from resultant modules in order as it appears in the condition.
- In case of layout the position is calculated based of the position of the field in the XDP hierarchy.It is recommended to design the form in such a way such that the hierarchical order of the fields and the target areas is equivalent/similar to their geographical order.
2. Variables appearing from multiple paths.
- When a variable is present in multiple data module, the order of such variable is calculated based on the first module that appears in the content hierarchy.
3. Order of fields and variables in fragment layout.
- As it appears in the form hierarchy.
4. Evaluation of modules in Condition.
- Position of DDE/PH in expression comes first (alphabetically sorted ) ,followed by the variables from resultant modules as it appears in the condition
5. Insertion of data module with variables in List ( library access)
- Position DDE/PH is calculated based on the location of the List module as it appears in the PDF
6. Select/unselect/delete data module from list and target area.
- The order is recalculated on selection/unselection of a module
7. Changing the order of modules in List and Letter.
- Changing the Order of modules in CCR has no change in the variable order . It behaves as per the original position in the target areas.
8. Edit a text module and remove any variable.
- On removal of a variable from the text , order remains the same. It is considered as if the variable is still present in the text.The variable is shown in the data panel even when the variable was used in one text and it no longer exists. It is recommended not to insert/remove variables from a text module in CCR.
PS: The above behavior is observed on the Livecycle version ES4 SP1.
ES4 Service Pack 1 comes bundled with Jboss EAP 5.2 . To configure multiple instances on the same machine we prefer to pass the binding parameters from commanline.
In case of Correspondence management solution, suppose we have to configure Author and Publish instance on a single Jboss installation. Then we need set the port and crx_repository path on the fly.
Jboss 5.2 does not allow to pass the –D arguments from the command line.
This a known jboss issue introduced with the version 5.2 .
There are a number of alternative methods to set the system properties.
- Create a property file publish.properties in jboss/bin directory and add the required parameters in the property file
(eg: C:Adobecrx-repository remember to escape the backslash character)
include the property file on Jboss start up
run -c <jboss_instance> -b 0.0.0.0 -P publish.properties
- Pass the parameters in the run.conf.bat file. If more than one instance needs to be started on the same machine create a separate run.bat and run.conf.bat file for that instance.
To configure Publish instance
copy the run.bat and rename it to run_publish.bat
copy and rename run.conf.bat to run.conf_publish.bat
edit run.bat. Search and replace run.conf.bat to run.conf_publish.bat to point it to the new configuration file.
edit the run.conf_publish.bat file and append the below arguments to JAVA_OPTS
start run_publish.bat from commandline
run_publish -c <Jboss_instance> -b 0.0.0.0
PS: These steps should also work for a linux based Jboss installation. Make similar changes to the startup script run.sh
LiveCycle ES4 SP1 i.e service pack 1 is released and now available for download from Adobe’s Download page It is the first service pack that has been released on top of LiveCycle ES4 which was released in March 2013.
For more details about this release, see Santosh Kumar's blog post.
To know more, read Sudhanshu Singh's blog post on the LiveCycle blog.