As an Adobe LiveCycle ES user, you have encountered the term LiveCycle ES application; and if you have not, you will. Well, what exactly is a LiveCycle ES application? Is it a process developed in Adobe LiveCycle Workbench ES that uses some forms and form data and allows users to interact with it using Adobe LiveCycle Workspace ES? Is it watched folder solution that enables users to place PDF documents in a folder where they are encrypted by a process created in Workbench ES. Or is it a client application written is Java, web services, or Adobe Flex that invokes LiveCycle ES. Well, the answer may surprise you. The answer is all of the above and much more.
LiveCycle ES is a development platform that lets you develop enterprise solutions to automate business processes. Some companies spend time and effort to process information the old fashion way; that is, by using paper-based forms only. And by doing so, information is lost or a lot of cost is involved processing the paper-based forms. As a LiveCycle ES user, you can use its functionality to develop a LiveCycle ES application to automate business processes. You can use Workbench ES, the LiveCycle ES SDK, or a combination of both. The LiveCycle ES SDK is provided to enable you to create client applications that can invoke LiveCycle ES services.
One type of use case is using both the Workbench ES and the LiveCycle ES SDK. That is, you use Workbench ES to create a process that automates your business processes. Then you can use the LiveCycle ES SDK to create a client application written in Flex, Java, or a development environment that supports web services. The client application is used to invoke the process created in Workbench ES.
For example, if you belong to a company that develops in Java, you can invoke a process from a Java client application. It does not matter if the Java application is an EJB bean, a Java Swing application, a Java servlet, or a console application.
When using the LiveCycle ES SDK, you do not have to create a process using Workbench ES. For example, you can develop a web application that directly invokes a service, such as the Forms service. In this situation, the web application is able to render interactive forms to users in a web browser. To develop this type of data capture application, you use the Forms service Java API. This LiveCycle ES application is created without using Workbench ES. Most LiveCycle ES services have a Java API that enables you to directly invoke the service.
On the other hand, you do not have to develop a client application using the LiveCycle ES SDK either. Instead, you can develop a process by using Workbench ES and then have users interact with the process using Workspace ES. This approach enables a LiveCycle ES application to be developed without any programming involved.
As you can see, when creating LiveCycle ES applications, you have many choices. This is what makes LiveCycle ES a very powerful development platform. Before you start developing an application, it is important to plan your application and have a clear understanding of what you want it to do and how you want users to interact with it.
So in conclusion – the next time you encounter the term LiveCycle ES application, know that it can mean many different types of solutions. This is just a tip that hopefully makes your experience with LiveCycle ES a positive one.