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:
- Modify the asset FML
- Extend the asset handler
- Register the modified asset handler
- Rebuild and redeploy the solution template
Details, including code snippets, are available here.
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.
Sometimes, you may want to create Correspondence Management solution assets that contain special characters in their names. To do so, you must first define the list of special characters that you want to use in the tbxeditor-config XML file.
Follow these steps:
- Log in to the CRX console at http://<servername>:<port>/crx/de/index.jsp as an admin. The default admin credentials are admin/admin.
- Edit the content/cm/tbxeditor-config.xml file.
- Enter the special characters within the customAssetNameCharset tag. For example, to enable the French character set, enter the special characters À, Î , Ù, etc within the tag.
- Save the XML file.
- Now, to use any character in the Editor Properties dialog, enter Alt + <ASCII value of the special character>.
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.
The LiveCycle Cookbook, a community resource for developers, has a recent recipe and sample artifact by Arjun V: Toggling between two fields in a dynamic form.
The Cookbook homepage is here: http://cookbooks.adobe.com/livecycle. Check out the available recipes and contribute your own.
If you’re a LiveCycle user or consultant, you may have found it difficult at times to follow all those great blogs and resources out there in the community. That’s why we’ve brought you The LiveCycle Post, a human-moderated aggregator of the best user-assistance content from the community.
How does it work? Well, it’s simple. We read through a bunch of machine-aggregated blog posts every now and then and moderate the ones that LiveCycle users would find useful. These blog posts are authored by LiveCycle users, Adobe partners, customers, and Adobe employees.
And yes, if you have a LiveCycle resource that you’d want us to track, simply leave its RSS feed URL as a comment to this blog post. All rights for your content remain yours. We’ll also make sure we include your name and a link to your blog in the aggregated posts.
Here’s the link again: http://blogs.adobe.com/livecyclepost/.
The campaign is the highest layer in the Integrated Content Review object hierarchy. The project is the second layer in the object hierarchy and the asset is the third layer. In fact, an asset is the basic unit of work — a work item — in the Integrated Content Review workflow.
Multiple levels of project nesting are supported.
Assets are actively managed through review cycles and drive all statuses in the campaign. For example, if an asset is late, the status of the parent campaign automatically becomes red. If all the constituent assets of a campaign are on time or green, the status of the campaign is green. Therefore, the status of a campaign is derived bottom-up instead of top-down.
Team member inheritance
Teams are built in a bottom-up fashion. Team members at any level in the campaign hierarchy include team members from lower levels. In other words, a campaign includes all members of a project. A project, in turn, includes all members of the assets within it.
Additionally, at any level in the campaign, a new member can be added directly to the team list. These new members have no responsibilities towards the campaign, but they receive notifications when statuses change. They also get access to the solution interface so that they can proactively see how the campaign is progressing.
For background information, you can refer to the Integrated Content Review Solution Guide.
The Integrated Content Review solution ships with a solution interface and building blocks that you can customize as per your organization’s requirements. Before you set out to customize these components, you must first set up your development environment. Setting up the ICR development environment involves the following broad steps:
- Set up prerequisites
- Locate the solution interface and required dependencies
- Understand available projects
- Set up available projects in Flash Builder
- Set up Java projects in Eclipse
- Build and deploy the solution interface
The Integrated Content Review solution enables enterprises to streamline the planning, creation, review, approval, and archiving of assets used in digital marketing campaigns. The solution includes a solution interface and the Adobe Creative Suite Task List Extension for Integrated Content Review.
Using the solution interface, you can manage assets through creation, review, and approval workflows. The Creative Suite Task List extension lets creative professionals submit artifacts for review and receive comments and approval from right within Adobe Illustrator, InDesign, and Photoshop.
The infographic below captures the ICR workflow and user scenarios, together with the roles/personas involved at each step. (Click the image to view it full-size).
For descriptions of ICR roles/personas and user scenarios, see this chapter in the Integrated Content Review 10.0 Solution Guide.
For further information, you can refer to the following resources: