When Customizing the LiveCycle Workspace ES2 User Interface [link] guide was released, it was before Adobe Flash Builder was available for us to do our certification testing. Technically, it is possible to use Flash Builder provided you use the Flex SDK version 3.4.1, ant-contrib.jar file version 1.0b2, and Ant-plug-in as described in the guide. For more information, see the LiveCycle Product blog for steps in the posting Customize LC Workspace ES2 UI using FB4 Premium on 64-bit O/S
In a future release, we plan to complete certification testing and update the guide with updated instructions, but in the meantime, here are some instructions for you to configure your environment to build Workspace customizations using Flash Builder 4. You must complete the last step in the blog when your development environment is a 64-bit operating system.
Beginning with LiveCycle ES2 Service Pack 2 (188.8.131.52), LiveCycle ES2 supports just-in-time provisioning of users that don’t yet exist in User Management. Just-in-time (JIT) provisioning creates new users dynamically in User Management once an authentication provider has successfully authenticated their credentials. Additionally, relevant roles and groups are assigned on-the-fly to the new user.
We have published a new TechNote that you can read to understand and implement this feature. This TechNote discusses the following:
- The need for JIT user provisioning
- How to implement JIT user provisioning
- JIT user provisioning: Behind the scenes
You can disable content indexing to improve Content Services ES2 performance. However, keep in mind that disabling indexing will also disable text-based search within new content. To disable indexing:
- In the adobe-contentservices.ear file, navigate to
LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
- Locate the following line:
- Set the index enabled and tokenized properties to false.
- Change <index enabled=”true”> to <index enabled=”false”>.
- Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.
For additional performance improvements, you can disable the conversions required for indexing. To disable these conversions:
- In adobe-contentservices.ear, browse to
- Preserve a backup of the custom-metadata-extractors-context file.
- Delete this file from the EAR.
Available on Adobe labs is the prerelease of a Component Development tool that you may find useful when you create custom components for LiveCycle ES and LiveCycle ES2. In a nutshell, the tool simplifies the workflow to create the component.xml file and build the JAR file to deploy to LiveCycle ES2. Check out the tool here.
What are custom components you ask? Custom components consist of Java code that you expose as reusable components in LiveCycle ES2. For example, you can create a custom component that provides custom email capabilities to extend LiveCycle ES2. You can reuse the component in business processes you want to automate using LiveCycle Workbench ES2.
For more information about developing custom components, see Programming with LiveCycle ES2 Help. For information about creating processes, see Application Development Using Livecycle Workbench ES2 Help.
Please feel free to comment on the tool here.
I learned a little trick from the LiveCycle software verification team regarding a neat way to validate the data users enter into objects on a Guide. If you are interested, you can check out the information in Adobe Cookbooks.
See the Guides section of the cookbook.
Have a nice day.
Applications developed using Flex for data capture experiences are referred to as Flex applications, and often informally called Flex forms. You create Flex applications for LiveCycle Workspace ES2 for interesting data capture experiences; or simply because you require an alternative to PDF forms and HTML forms. Check out the walkthrough in the Creating Flex Applications Enabled for LiveCycle Workspace ES2 guide here.
The Administering LiveCycle Content Services ES2 guide is now available. The guide discusses the following administration activities, besides others:
- Configuring the inbound and outbound email service
- Monitoring Content Services ES2 using the Java Management Extension (JMX)
- Estimating how many servers to use for running Content Services ES2
View this new guide here.
Also check out the following related Help:
In Livecycle Workspace ES, a user can request access to another user’s (say Alex Pink’s) task queue. This initiates a queue sharing process and a Share Queue Request form appears in the Alex’s To Do list. The Share Queue Request form is a Flex application provided with LiveCycle Process Management ES and is available in LiveCycle Workbench ES in the queuesharing.swf file.
In earlier releases of LiveCycle ES, the source code for the Share Queue Request form was not provided with the rest of the LiveCycle Workspace ES source code, therefore, if you localized Workspace ES to another language, such as Spanish, the Share Queue Request form would still appear in English. In LiveCycle ES Update 1 SP 1 (184.108.40.206), the source code for the Share Queue Request form is now available in the LiveCycle ES SDK so that you can localize it. However, before you can localize the for, you you must configure your development environment for customizing Workspace ES as described in Customizing the LiveCycle Workspace ES User Interface and complete the localization customization.