Reach more clients and launch better forms faster

Like many governments, financial service organizations, or other regulated industries, you’re using Adobe LiveCycle to improve productivity and deliver online self-service to clients and employees. We’ve already given you five great reasons to upgrade from LiveCycle to Experience Manager Forms. The latest release of Experience Manager Forms further improves organizational productivity and customer experiences by helping solve two of the most common challenges associated with complex forms.

Challenge #1: Your clients and employees are online with their mobile devices every day—how are your forms keeping up?

If you are providing static, non-responsive forms to clients and employees, you are losing clients and the opportunity to use a low-cost channel instead of expensive phone or in-person channels. In a 2014 survey, Pew Research reported that 57% of Americans had used their smartphone to do online banking, while 40% had looked up government services. That number has only increased, and this mobility is also changing how individuals work. IDC predicts almost three quarters of the US workforce will be mobilized by 2020. What’s even more interesting is that most people use multiple devices. In the UK, 60% of online adults use at least two devices every day, and 40% start an activity on one device and finish it on another.

Experience Manager Forms helps organizations build forms and documents that offer consistent, responsive and dynamic experiences across devices. You can author forms once and ensure they engage smartphone, tablet, and laptop users. You can preview forms to see how they will look on a variety of devices and screen sizes. New integration with Experience Manager Mobile lets you seamlessly embed forms and documents in mobile apps, allowing clients to interact with them anytime and anywhere.

Challenge #2: Launching and managing forms and integrating them into other digital experiences takes too much time and effort.

For many organizations, it takes months and an army to create and launch a new form. A form designer creates the form structure and content. Copywriters and graphic designers ensure the form matches branding and style guidelines. The line of business reviews the design and copy, as does the legal team. IT gets involved connecting form inputs to other systems. The web team integrates the form into websites. Lengthy testing refines the user experience on several devices. Forms may also be sent for translation if necessary.

New features in Experience Manager Forms cut that process down dramatically, enabling you to launch new forms in weeks and update them quickly. Experience Manager Forms comes with several form templates, giving non-technical users a basis for creating a form that is already optimized for a range of devices and screens. Editable style themes allow business users to swap in organizational colors, logos, fonts, and more, without the help of graphic designers. Content fragments ensure forms always use the same, consistent, approved language, making copy reviews smoother. Business users can electronically send forms for review. Reviewers can experience the forms as users do and electronically annotate any changes needed. Experience Manager Forms includes standard connectors to machine-based translation services, helping you reach a broader audience with forms that are localized quickly.

Once you’ve launched your form, it’s easy to ensure it becomes a seamless part of your online service and marketing strategy. Experience Manager Forms is part of a digital experience platform that offers a centralized way to productively manage all digital experiences, including websites, apps, rich media, images, and videos. And as part of the Adobe Marketing Cloud, you can measure interactions via Adobe Analytics, optimize and personalize form and document experiences using Adobe Target, and integrate forms and documents into multi-channel marketing campaigns with Adobe Campaign.

Take a look at what’s new in Experience Manager Forms 6.2 to find out how you can get better forms in the hands of clients faster, and reach more clients on more devices.

Posted in Adobe LiveCycle ES3 | Comments Off on Reach more clients and launch better forms faster

Enabling JMX on Jboss 6.2

Open jconsole.bat/sh from jboss/bin directory

Try to connect using URL-  service:jmx:remoting-jmx://<hostname>:4447

Hope this will help

Posted in Adobe LiveCycle ES3 | Comments Off on Enabling JMX on Jboss 6.2

Five reasons to upgrade from LiveCycle to Experience Manager Forms

5reason_upgrade_2xThousands of governments, financial institutions, and other enterprises use Adobe LiveCycle to enroll clients in services, streamline form and document processes, and generate professional documents efficiently. Adobe continues to invest in this technology with Adobe Experience Manager Forms, part of Adobe Experience Cloud. If you’re a LiveCycle customer, all your existing forms and applications will still work with Experience Manager Forms. Read on for five more great reasons to upgrade to Experience Manager Forms.

#1 – Offer excellent experiences to mobile users. With many people using smartphones as their primary way to access the Internet, it’s becoming crucial to offer digital experiences that serve mobile users. Experience Manager Forms lets you leverage existing LiveCycle templates and extend them into engaging forms and documents designed for smartphone and tablet users. Users don’t have to install special software or browser plugins, and they can take advantage of device features to fill in forms using fewer keystrokes.

#2 – Access more features. All the features you’ve come to rely on in LiveCycle are available in Experience Manager Forms, and we’ve added many more over the last two years. Experience Manager Forms licenses also include all features (except document security, available as an add-on), in contrast to the very modular LiveCycle licenses. You don’t have to decide upfront which features you may use in the future, simplifying the decision-making and licensing process.

#3 – Leverage Adobe Experience Cloud. Experience Manager Forms takes advantage of other capabilities in Adobe Experience Cloud to measure and continually improve digital form and document experiences. For example, Forms works with Adobe Analytics to measure client interactions. Using the insight gained from visual reports, business users can easily test and continually improve forms and documents with Adobe Target, reducing the chance of form abandonment or calls to client support.

#4 – Upgrade without a forklift. Retain existing data, processes, and assets while upgrading to Experience Manager Forms. LiveCycle ES4 customers can upgrade to AEM Forms, while earlier LiveCycle versions must first upgrade to ES4.

#5 – It’s the way of the future. Clients are demanding more integrated digital experiences and less paper. For forms and documents, Adobe is answering that need with Experience Manager Forms. While core support for LiveCycle ES4 ends in 2018, Experience Manager Forms is the focus of our investment. Now is the time to think about upgrading.

For more information on why upgrading to Experience Manager Forms is essential:

Posted in AEM forms, Upgrade, Adobe LiveCycle ES | Tagged , , , , | Comments Off on Five reasons to upgrade from LiveCycle to Experience Manager Forms

Adobe Central Pro Output Server and Adobe Web Output Customers: Migration Coming Soon

While batch and on demand printing capabilities have matured, many organizations find themselves facing new challenges serving an increasingly mobile and Web-centric world. Consumers and citizens want the same engaging experience in their business transactions that they get in their day-to-day E-commerce Web activity. As the market leader in Web Experience Management and Digital Marketing, Adobe clearly has the necessary tools to address these new challenges.

As an Adobe Central Pro Output Server or Adobe Web Output Pak owner, your product family support is scheduled to end on June 30, 2016. We have been getting a lot of questions from Central Pro Output and Web Output Pak customers as to what their future looks like with Adobe. You can be assured that we are working out the final details of a migration plan that we will share at the beginning of 2015.

Migration details coming soon: If you would like more details when they become available or have additional questions about the upcoming migration, you can email us directly at

For more information on how you can create, publish, and manage digital forms and document collections to multiple channels with Adobe Experience Manager forms, go to:

Posted in General Interest | Comments Off on Adobe Central Pro Output Server and Adobe Web Output Customers: Migration Coming Soon

Designing forms for higher performance on Mobile devices

Mobile forms in Adobe Experience Manager forms offers rendering of XFA form templates in HTML5 format. This capability enables the rendering of forms on mobile devices and desktop browsers on which XFA-based PDF is not supported.
As the rendition of forms is targeted for devices which have limited processing capabilities / network bandwidth, a few considerations should be kept in mind while designing the forms. Most of these suggestions are applicable even for XFA forms which as accessed through HTML Workspace on a desktop, but due to limited resources on the tablet/mobile device, a special focus is required for such devices.

  • Reducing the number of nodes in the form: HTML forms generates Model and HTML DOM elements for the various elements of an XFA form. Each of these elements contain various properties to control the view and behaviour, thereby increasing the overall DOM structure. Following approaches are suggested to reduce the number of elements:
    • For a field the label should be provided through the caption and not through a separate text object (apart from performance it also helps in managing the form and avoid any layout issues).
    • Draw elements do not participate in information capture, and are required more for the readability and appearance. Design should ensure that where possible multiple draw texts should be merged into single draw text element.
  • Resource optimization and compression: Following approach should be evaluated for compression of resources:
    • Images embedded/referred in the form should be compressed to reduce the overall form size. Also, the form design should be approached as a web form to be filled on the mobile device, and not a paper form. In many scenarios a logo image may not be required on all the pages.
    • JavaScript and CSS files can be compressed using the minify option in Configuration Manager (Day CQ HTML Library Manager). For details on minify please refer to the documentation at:
    • Web Server compression should be enabled to perform compression of request/response, thereby reducing the network bandwidth. For details on compression please refer to the documentation at:
  • Handling large forms: There are instances when the form need to capture large amounts of data resulting in hundreds of fields in the form. The following points should be kept in mind while designing the form:
    • From a usability perspective filling multiple small forms is more convenient than filling a large form. So one should evaluate splitting the large forms.
    • For a form which has multiple sections, each section may be divided into a separate page which loads when the user moves to the next page (Mobile Forms by default loads the next page on user interaction for page scroll).
    • Conditional sections/sub-sections may be hidden by default and made visible only when the required condition is met.
    • A tabbed navigation may be introduced to have only a section of the form visible at a time (this also assists in resolving usability issues in large forms).
  • Handling tabular data:
    • Avoid columns which are not actually required to be filled-in by the user.
    • In case certain read-only columns (which do not capture the information, but are required to describe the information in the rows) are required – evaluate if such columns can be merged into a single column.
    • On a mobile device a user would be able to view only a subset of tables having large number of rows. In such a scenario introduce a paged navigation where the data is populated from a hidden data table into a visible view table having limited number of rows and columns.

Note: For special cases where the XFA forms contain large sections of elements which are not required during form filling (and are required only for Document of Record), a more aggressive approach to reduce the number of nodes can be to maintain different copies of XFA forms – one for form filling, and one for generating Document of Record on the server. This approach involves maintaining two copies of the same form and the performance gain needs to be evaluated keeping in mind the maintenance overhead.

Posted in Adobe LiveCycle ES3 | Tagged , | Comments Off on Designing forms for higher performance on Mobile devices

Moving Over to AEM Forms – It’s Easier Than You Think

Adobe is well known for its PDF forms capabilities and the LiveCycle platform that’s made it possible to deliver and integrate enterprise forms and document solutions with our customer’s back-end systems.  While PDF form capabilities and LiveCycle have matured, many organizations find themselves facing new challenges serving an increasing mobile and web-centric world. Consumers and citizens want the same engaging experience in their business transactions that they get in their day to day e-commerce web activity.

  1. How do you seamlessly enable citizens, customers and employees to interact and transact with your organization across a huge array of devices in the market today?
  2. How do you gather and analyze data on how users access your website and forms and determine ways to better optimize that experience?
  3. How do you reduce operational costs while at the same time converting prospects and retaining existing customers?

As a market leader in Web Experience Management and Digital Marketing, Adobe clearly has the tools to address these new challenges.   Earlier this year, we released Adobe Experience Manager forms (AEM forms).   AEM forms leverages the web content management capabilities of Adobe Experience Manager and the analytics of the Adobe Marketing Cloud to help organizations easily develop, publish and manage enterprise forms and documents for desktop and mobile web.   We have had a very positive response from customers about these new capabilities — but a little bit of confusion on how they can leverage it in their own existing LiveCycle infrastructure. Do our customers have to do an expensive and time consuming technical migration from LiveCycle to AEM forms?  No, a lengthy technical migration isn’t required to take advantage of the new rich features in AEM forms.

AEM forms encompasses all of the capabilities of the LiveCycle platform and more.  Existing LiveCycle customers can seamlessly upgrade their existing applications and can start developing customized forms for web and mobile.   All of the powerful and mature capabilities of the LiveCycle platform are available to AEM forms customers.   So if you are excited about the possibilities of AEM forms (as we are), but are worried about what it will take to get there – don’t be.

Check out AEM forms

Contact us on how to upgrade to AEM forms today!





Posted in Adobe LiveCycle ES3 | Comments Off on Moving Over to AEM Forms – It’s Easier Than You Think

“Purge completed records after” not editable

Issue: You are trying to change the purge options on the LiveCycle AdminUI > Health Monitor > Job Purge Scheduler but you can’t edit the field “Purge completed records after” because when clicking into this field it doesn’t get the focus. There is no cursor blinking and you can’t type into the field.

Solution: Tab into the field using the tabulator key on your keyboard. Note that the tab order is so that you have to place the cursor into the field “Recur every” and then press the tab key four times.

Background: An invisible object seems to be overlaying the field.

Issue occurs since LiveCycle ES3 and is still reproducible with ES3 SP2 and ES4 SP1.

Posted in Adobe LiveCycle ES4, Adobe LiveCycle ES3 | Tagged , | Comments Off on “Purge completed records after” not editable

LC Designer: Wrong variable getting deleted

If you are working on a form in LiveCycle Designer which has not just form variables but also object collections and/or script objects all those will be listed on the Hierarchy tab under Variables.

Issue: If you delete a form variable from the Form Properties dialog (File > Form Properties > Variables) the wrong one will get deleted if the variables are not sorted.

Background: On the Hierarchy tab you see all three types of variables: form variables, object collections, and script objects. On the Form Properties dialog you only see the form variables. Designer seems to internally number the variables top to bottom. This will cause a form variable on the Hierarchy tab to have a different internal number than the same form variable on the Form Properties dialog if the three kinds of variables are not sorted.

Example: In the screenshot below the variable “v8_form_variable” is the eighth item in the list.


If you open the Form Properties dialog to look at the form variables the same variable is now the third item in the list, see screenshot below.


If you now delete that variable, close the Form Properties dialog, and look at the Hierarchy tab, you’ll notice that instead of “v8_form_variable” the item “v3_script_object” got deleted. You deleted the third item in the list on the Form Properties dialog but Designer deleted the third item in the list on the Hierarchy tab.

Solution: You can either sort your variables on the Hierarchy tab in the way that form variables appear at the top of the list, see screenshot below. Or you can simply not delete form variables form the Form Properties dialog but directly from the Hierarchy tab instead (right click > Delete).


Reproducible with the following LiveCycle Designer versions: ES2, ADEP, ES3, ES4

Posted in Adobe LiveCycle ES4, Adobe LiveCycle ES3, Adobe LiveCycle ES2 (9.0.x), ADEP | Tagged , | Comments Off on LC Designer: Wrong variable getting deleted

Adobe Reader Mobile and XFA forms from LiveCycle Designer

As the world becomes increasingly more mobile, we hear a lot of questions about dynamic PDF forms created in the LiveCycle Designer and mobile devices.  These forms use an underlying XML structure called XFA (XML Forms Architecture).   This XML structure is pretty powerful and allows the form to grow and shrink based on data or user actions.  It also provides a scripting model that lets you do some amazing things and interact with objects on the page through code.   Many enterprises require this kind of capability for their complex forms.

Along with the changes in the world where more and more people connect to the internet with mobile devices comes a variety of operating systems and browsers.  Some of these operating systems place restrictions on what can be done on the device and most of the browsers now provide their own PDF viewers which are not as capable as the Adobe Reader on the desktop.   This makes it very difficult (impossible actually) to provide the same dynamic PDF experience you expect on the desktop across all mobile devices using PDF.  As a result, Adobe Reader Mobile does not support XFA based PDF’s created in the LiveCycle Designer and it will not provide this support in the future.

Fortunately the XFA structure also allows a single form definition to be transformed into a number of different targets besides interactive PDF.  To target mobile devices and ensure a consistent experience across devices (and on the desktop too!) we’ve created a Mobile Forms capability that renders the same template design for PDF to HTML5 and preserves the layout, scripting and dynamic capabilities.  Given the nature of HTML and the web, this is not a single file like a PDF that can be routed around in email.   It’s an online experience rendered by a server.   Using a server platform there are a lot of other capabilities that come into play such as prefilling forms with data, form management, forms workflow and document generation.  For more information on AEM forms please see our web page.

Posted in Adobe LiveCycle ES4, General Interest | 5 Comments

Watermarks of dynamic length

This article explains why a watermark might exceed the boundaries of a page or appear at different positions whenever its length changes.

By default, when adding a watermark using LiveCycle Assembler invoking a DDX, it is placed in the centre of the page with no rotation. The watermark can be rotated and positioned using the following attributes:


Note: These values are examples. For full details of the syntax and a description of additional attributes to use with watermarks please see the latest Assembler Service and DDX Reference

There are two things to keep in mind when adjusting a watermark:
(1) The watermark will be positioned first and rotated after, regardless of the order in which the attributes are listed.
(2) When applying rotation, the centre of the watermark’s bounding box is used as a fixed centre of rotation. Imagine your watermark without rotation and with a frame around it. This frame represents the bounding box. The centre of that box is the fixed point for its rotation.

For example, if you want your watermark to appear at the left border of your page and rotated by 90 degrees, set the horizontal anchor to “left”, rotation to “90”, and use the horizontal and vertical offset to fine-tune its position.

With a watermark of a fixed length, the fine-tuning is done with fixed values.

Watermarks with dynamic length, however, require the offsets to be calculated dynamically as well because of points (1) and (2) above.

The graphic below demonstrates why. When working with watermarks of dynamic length you’ll have shorter watermarks and longer watermarks. For a shorter watermark the fix point for the rotation is further left than for a longer watermark.


After rotation your watermark might exceed the page boundary. In the sample below you need to adjust the vertical offset to move it further down. Notice that you need a greater vertical offset for the longer watermark and a lesser vertical offset for the shorter one. The longer watermark appears further right than the shorter one. Use the horizontal offset to adjust that. Notice that if you want both watermarks to appear at closer to the left border of the page you need a lower horizontal offset for the shorter one than for the longer one.


To avoid the dynamic calculation of offsets when working with watermarks of dynamic length, keep them at the centre of the page.

Posted in Adobe LiveCycle ES4, Adobe LiveCycle ES3, Adobe LiveCycle ES2 (9.0.x), ADEP | Tagged | Comments Off on Watermarks of dynamic length