Correspondence Management: Adding custom asset action buttons

The Correspondence Management solution lets you add new actions to the Manage Assets UI for a particular asset type. The following broad steps are involved in this process:

  1. Modify the asset FML
  2. Extend the asset handler
  3. Register the modified asset handler
  4. Rebuild and redeploy the solution template

Details, including code snippets, are available here.

Correspondence Management: Move active assets betwixt systems

Correspondence Management 9.5 now lets you conveniently move active assets from one system to another. You can export the selected assets from the source system as a ZIP package and import the ZIP package into the target system.

This functionality is useful in several scenarios; for example, when you’re moving assets from a development environment to a production environment.

Some important considerations to keep in mind:

  • Only active assets can be exported. Further, all the assets to be exported must be on the same Correspondence Management system.
  • For optimal performance, select a maximum of 100 letters for export and ensure that the exported ZIP package size does not exceed 50 MB.
  • The export operation fails if one or more dependent assets for a selected asset are in the archived state. To resolve this issue, refer to the log and modify the selected asset such that it is dependent on the active version of the offending asset instead of the archived version.

You can access the documentation for this new feature here.

Author-instance clustering for Correspondence Management

We’ve added a brand new section to the Installing the Correspondence Management Developer’s Guide explaining how you can set up author-instance clustering for Correspondence Management.

When the Correspondence Management solution is deployed, the author instance runs on the same server as LiveCycle ES3. However, setting up the LiveCycle cluster doesn’t automatically configure the Correspondence Management author-instance cluster. You must set up this cluster manually.

Author-instance clustering has no dependency on LiveCycle clustering. The LiveCycle cluster acts as a backend system for author instance clustering when LiveCycle is integrated with the Correspondence Management solution. The shared nothing mode of clustering is supported for Correspondence Management.

You can read the full technical article here.

Adobe LiveCycle ES3 is here!

Adobe has just announced the release of LiveCycle ES3. Dave Welch, Senior Director – LiveCycle, writes about the new release on the Adobe LiveCycle Blog:

LiveCycle ES3 contains the document and data services capabilities, including electronic forms and business processes, which were formerly part of the Adobe Digital Enterprise Platform (ADEP), a brand that is being retired.

The new LiveCycle ES3 release incorporates:

  • Document services capabilities available with ADEP and the recent ADEP Document Services service pack 1
  • LiveCycle Data Services 4.6.1
  • Updates to LiveCycle Connectors for Microsoft® SharePoint® and IBM® FileNet

LiveCycle offers a number of components that help extend the value of existing back-end systems by better engaging users, streamlining processes, managing correspondence, and strengthening security. These components are:

  • Modules: Reader Extensions, Forms, Output, Digital Signatures, Rights Management, Process Management, PDF Generation
  • Tools: Workbench, Designer
  • Solutions: Correspondence Management
  • ECM Connectors: SharePoint, IBM Filenet, Documentum, IBM CM
  • Advanced Offerings: Data Services

The FAQ capturing more details about LiveCycle ES3 and ADEP is here.