This blog post is part of the series on customizing the Adobe Integrated Content Review solution.
Integrated Content Review solution interface is a Flex® application, which is the default implementation. You can customize the default Adobe branding across the solution interface.
As an example, let us change the Adobe logo in the top-left corner of the solution interface. To do so, follow these steps:
- Open the Campaign Portal project in the Package Explorer view, in Flash® Builder®.
- Navigate to the desired skin file and open it. To change the logo, navigate to CampaignPortal > src > main > flex > com.adobe.solutions.icr.common > skins > ApplicationHeaderSkin.mxml.
- Make the requisite modifications. To change the logo, replace the existing path with the path to a custom logo image file, at the location shown in the following screenshot.
Path of ICR logo file
- After making the requisite changes, rebuild and redeploy the solution interface. To do so, refer to Setting up your development environment.
Note: The logo must be 107 x 47 pixels or smaller in size. If it is larger, then use the width and height properties, as shown below, to resize it.
Dimensions of ICR logo file
This page, to know more about ICR solution.
The solution guide to get started with the solution.
The Adobe Managed & Approval Solution Accelerator 9.5 is a wonderful solution for automating reviews for documents in your organization. One of the handy features of the solution is email updates for automated reviews. For example, emails are automatically sent for these scenarios:
- When a reviewer completes a review or review stage.
- When an approver approves a document.
- When reviewers or approvers are added to or removed from a review.
- When a review or review stage completes.
This requirement is necessary for organizations that have regulated review and approval workflows. However, in non-regulated environments, this requirement may be a distraction to users because of the number of emails that can be sent in reviews that involve significant number of people.
Alexandra Phillips has provided an article to describe how to configure the emails that are sent using the Solution Template provided with the Managed Review & Approval Solution Accelerator. Check out the article here.
In LiveCycle Workspace ES2 (version 126.96.36.199), tabs are available for you to start new processes, view tasks that are assigned to you, and track tasks and processes. What if you wanted to add your own tab to enhance it? Check out a new article by Nithiyanandam Dharmadass that describes how to add navigation tabs to Workspace here.
Would you like to learn how to use the Execute Script service to manipulate XML using LiveCycle Workbench ES2? Here is a tutorial provided by one of our Adobe partners, Twin Technologies!
Check out the most excellent tutorial from Deke Smith at here.
Marcel van Espen, over at the Dr Flex and Dr LiveCycle blog, explains how you can create a LiveCycle process to access custom Office properties. His blog post also includes a useful example.
“Within LiveCycle Workbench ES, one of the services in the common category that you can use is ‘Export XMP’. This service will extract all the available metadata from a PDF document. If you have converted a MS-Office document to a PDF document, you will be surprised what metadata is also converted. All these properties now become accessible.”
Read the complete post here.
Do you want to learn how to bind dynamic forms fields to schema in Adobe LiveCycle Designer ES2? Here is a tutorial provided by one of our Adobe partners, Twin Technologies! The article is posted on Adobe DevNet here.
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.”
When Customizing the LiveCycle Workspace ES2 User Interface [link] guide was released, it was before Adobe Flash Builder was available for us to do our certification testing. Technically, it is possible to use Flash Builder provided you use the Flex SDK version 3.4.1, ant-contrib.jar file version 1.0b2, and Ant-plug-in as described in the guide. For more information, see the LiveCycle Product blog for steps in the posting Customize LC Workspace ES2 UI using FB4 Premium on 64-bit O/S
In a future release, we plan to complete certification testing and update the guide with updated instructions, but in the meantime, here are some instructions for you to configure your environment to build Workspace customizations using Flash Builder 4. You must complete the last step in the blog when your development environment is a 64-bit operating system.
When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.
Follow these steps to resolve the issue:
- In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
- In the right pane, click Thread pools under Additional Properties.
- Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
- Click Apply or OK.
- Click Save directly to the master configuration.
- Restart the WebSphere application server.
You can disable content indexing to improve Content Services 9 performance. Disabling indexing also disables text-based search within new content. However, you can still search within already-indexed content.
Follow these steps to disable indexing:
- In the adobe-contentservices.ear file, navigate to LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
- Locate the following line:
- Set the index enabled and tokenized properties to false.
- Change <index enabled=”true”> to <index enabled=”false”>.
- Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.
Disable the conversions required for indexing
To realize additional performance improvements, disable the conversions required for indexing. Follow these steps:
- In adobe-contentservices.ear, browse to contentservices.war\WEB-INF\classes\alfresco\extension.
- Preserve a backup of the custom-metadata-extractors-context file.
- Delete this file from the EAR.