LiveCycle Enterprise Suite

POST data size limit

A generic Mobile Form workflow involves rendering a form, filling up fields and then submit it for further processing. Mobile Form submits data to server on HTTP POST. If the form is very big or it is merged with large size data, sometimes there is chance that the submission payload exceeds the default limit of the server. In this case, you might see HTTP 500 error on form submission. If you inspect the server logs, you will see this exception – “Template is not specified”.

Read the complete post here.

Cache is king

Cache plays a very important role in the performance of Mobile Form or for that matter any component. Mobile Form caches all the intermediate objects required to process (rendition or submission) a form on first request. It doesn’t cache the objects dependent on the data as they are very likely to change.

To know more about Cache in Mobile Forms, read the complete post here.

Rendering a Chart in Mobile Forms

In this article we will use JQPlot charting capabilities to draw a pie chart.To Learn more about JQPlot- click here The charts data will be coming from the table which is designed using the LiveCycle Designer. We will also be exploring the FormBridge API’s to access the Table’s data to feed into the JQPlot chart.

Read the complete post here.

Adobe LiveCycle Blog 2013-06-24 22:11:48

A lot of times you have a need to extract or import the data from Excel file into LiveCycle form in a programmatic manner. To accomplish this I have written a simple component. This component makes use of Apache POI classes to extract data from the Excel file. The sample component is not generic for all Excel files, but it was written for extracting data from a specific Excel file. With little modifications you can get this code to work with any Excel file. The code creates a map of xml documents where each xml document corresponds to a row in the excel document. You can deploy this component using workbench and use it as part of your process.

For the instructions, read this blog post.

The Adobe LiveCycle Portable Protection Library: an SDK to Manage your Rights Management Server

First, a little background information about Adobe LiveCycle

Adobe LiveCycle is an enterprise suite of server based software products that are meant to help structure business processes. One of its key features is the ability to protect a document (of the following types PDF, Microsoft Word, Microsoft Excel, Microsoft PowerPoint, text, and more!) with a policy to restrict access to a subset of users. Adobe LiveCycle offers this ability through one of its components called, Rights Management.

After a certain point large organizations or organizations that have been using Adobe LiveCycle for an extended period of time may accumulate a significant number of policies and documents, these can become tiresome to manage through the web interface for the Rights Management component of LiveCycle. Users of LiveCycle can also fall into performing the same action over and over, such as protecting documents with the same policy again and again. What if there was a programmatic way to apply these policies to new documents? What if there was a programmatic way to use a policy from one document in another? What if there was a programmatic way to manage these?



Read the complete post here.

Form Manager API

LiveCycle ES4 saw the (re)introduction of Form Manager. In simple terms Form Manager simplifies the process of managing forms. The official documentation for Form Manager can be found here. Once you have your required forms in Form Manager, you can start to build and manage Forms Portal.

To know about both the ways to build forms portal, read the complete post here.

Task Summary Page

Workspace in LiveCycle ES4 now shows a new tab called the “Summary” tab. As the name indicates this tab can be used to summarize the current task details. By default the “Summary” tab does not have any content in it. The process developer can create the content of the “Summary” tab. In general it is used to show some extra information related to the current task- such as Task Summary or display the driving directions specific to the address mentioned in the task.

Read the complete post here .

Understanding reader extensions licensing

We get many questions about reader extensions. That’s not surprising really because there are numerous ways to use reader extensions in an enterprise capacity as well as in a work group or consumer type of way. We also get many questions about the aspects of licensing reader extensions based on the fact that reader extended forms can be created from our Acrobat family of products as well as our LiveCycle family of products. The licensing programs for Acrobat and LiveCycle are designed to serve different uses and organizational needs. They scale from desktop use to enterprise levels

Get to know the licensing model here.

LiveCycle Mobile Forms: bringing all the capabilities of XFA-based forms in HTML5

Browsers like Google Chrome and Mozilla Firefox recently started to provide their own PDF viewers to display PDF documents. These native PDF viewers usually do not match the full capabilities provided by Adobe Reader.

Read the complete post here.

Managing LiveCycle Applications with ant

Adobe LiveCycle ES4 introduces out of the box ant tasks which can help in managing LiveCycle Applications (like import, export, deploy etc). In past, Livecycle client SDK provided following public APIs for managing applications:

Read the complete post here.
Go to Top