LiveCycle Enterprise Suite

Mobile Form upscaling

Mobile Form rendition of an XFA form is almost similar to PDF Form rendition in terms of behavior and appearance. Some of the dissimilarities are discussed in Mobile Form Vs PDF Form post. In this post, I’ll discuss one key difference that a form designer should take care while designing the XFA Template and that is where it is so critical to preview your templates from the designer itself.



Read the complete post here.

Built-in profiler in LiveCycle ES4 for performance analysis

New LiveCycle ES4 features like Forms Manager, HTML Workspace etc. require CQ repository as part of the installation. This embedded Adobe CQ, comes with a built in threads profiler. More information about this can be found at this CQ article. This profiler, being part of same container in which LiveCycle is running, collects thread data for LiveCycle classes and services as well.

Read the complete post here.

Mobile Workspace offline internals

With LiveCycle ES4, Mobile Workspace has enabled working without network connection. Offline support has mainly been achieved by caching and storing the data locally on the device. From the offset, the application assumes to be in offline mode. This has following major advantages:

Read the complete post here.

Tags in Forms Manager

One of the features provided by Forms Manager is a support to add CQ tags to Forms as a meta data. This blog post showcases how we can add CQ tags to the Form and use them to search Forms.  

Read the complete post here.

Hide template reference

In this post I will describe how one can you pass template reference without using request parameter. The default profile of Mobile Form takes all the parameters like template reference, data reference etc through HTTP request parameter. If Mobile Form is deployed to serve the forms on internet then you might not like to expose such URLs on public forums. That is probably because it would expose the internal repository structure to the end user.

Read the complete post here .

Page 0 support for protected documents in LiveCycle Rights Management ES4

Adobe LiveCycle Rights Management ES4 introduces Page 0 (Wrapper Document) support for Policy protected documents in Adobe LiveCycle ES4 release. In case of most of the non-Adobe PDF viewers, on opening LCRM protected documents a blank screen appears or the application aborts. With Page 0 support, for RM Policy protected PDFs, Cover Page or Page0 is displayed instead of the previewer displaying a blank screen or being completely aborted when viewed in non-Adobe PDF viewers.

Read the complete post here.

An introduction to Forms Manager

Adobe® LiveCycle® ES4 is offering a new component – Forms Manager – that simplifies form management. Forms Manager exposes most common form management operations through an HTML based user interface helping non-IT users to easily upload, download, preview, configure, activate...

Read the complete post here.

LiveCycle ES4 now Available

In an earlier blog post we announced the upcoming release of LiveCycle ES4. The LiveCycle team is very pleased to inform you that LiveCycle ES4 is now generally available. ES4 makes it easier to create, manage, and publish large numbers of forms on websites and allows mobile clients and workers to actively participate in business processes, improving engagement and productivity. See LiveCycle ES4 in action and find out more about what’s new in the ES4 documentation.

Read the complete annoucement here.

Mobile Workspace in offline mode

With the release of ES4, Mobile Workspace introduces offlining of tasks that have been assigned to a user. This helps the customer to work even when they are out of the network area. The users can perform actions associated with the tasks namely open the task, update and even complete the task while the application is offline. Once the user goes online, the application can be synced to the LiveCycle server. With this implementation, application provides a great user experience and no delay since everything works as if its on the device. The time consuming actions and tasks are done in background to enable the user best experience in the form of a mobile app.

Read the complete post here.
Go to Top