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>.
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.
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.
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
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:
Adobe Customer Experience Solutions help create, manage, and deliver high-impact, personalized interactions that captivate customers and extend brand values across digital channels. Powered by the Adobe Digital Enterprise Platform (ADEP), these solutions include rich enterprise applications and friendly user interfaces.
To understand Adobe’s Customer Experience Management philosophy and roadmap, view this great interview by Ben Watson, Adobe’s principal customer experience strategist.
Ben talks about Customer Experience Solutions as being integral to the manage part of Adobe’s becoming a make, manage, and measure brand.
So ultimately, we are becoming the make, manage and measure brand, as I think about it, in the enterprise. While we are probably still best known for ‘make’, in terms of Photoshop, Illustrator – our design tools – Acrobat for making documents, Flash for making multimedia presentations on the web or for delivering and making applications, and delivering an actual interactive application. I would argue that in the web space we are pretty well known from a measuring perspective as well. The acquisition of Omniture a few years has grown into the Adobe Online Marketing Suite, and we have a strong set of tools there around, not just measurement of web activity, but now measurement of social activity analytics that are relative to the communities you might be forming at an enterprise, or also your work that you do with third party communities, like the major social networks, etc.
Here in the middle are these set of technologies that I am focused on which are ultimately the management. By management I mean web content management, business process management and rolling all of this up under the umbrella of customer experience management.