Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What are the technical implications of the migration to LiveCycle Output ES?

0
Posted

What are the technical implications of the migration to LiveCycle Output ES?

0

Document templates need to be converted and new methods are needed to integrate into enterprise systems. LiveCycle Output ES accepts only XML data input, for instance. A template conversion tool is included that converts templates created in Output Designer to LiveCycle Designer ES. Templates created using the standard Output Designer tools typically convert easily and accurately. If you modified the preamble to customize your implementation, however, you will need to rework these aspects manually. Similarly, integration points previously handled by the Job Management Database will need to be migrated to the LiveCycle J2EE environment.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.