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.

Just-in-time provisioning of LiveCycle users

Beginning with LiveCycle ES2 Service Pack 2 (9.0.0.2), LiveCycle 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