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 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 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:
In a community blog post, Marcel van Espen from the Adobe presales team demonstrates how you can use LiveCycle and AIR to build a Twitter solution for your organization.
… you can use LiveCycle to build a process and an AIR application to publish tweets to a corporate Twitter account, where you have control on what’s published or not. Part 1 focuses on building the client with Flash Builder 4 with the LC Service Discovery plugin. In part 2 you will see how to archive all tweets in a PDF/A format within LiveCycle Content Services.