Posts in Category "Integrated Content Review"

Adding user images in ICR Solution Interface

Posted on November 11, 2011 by Ashish Gupta | Comments (2)

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.

***

Any entity of the Integrated Content Review solution like, a campaign, a project, or an asset, includes many participants or team members. The participants at any level in the campaign hierarchy include participants from lower levels. In other words, a campaign includes all the participants of a project. A project, in turn, includes all the participants of the assets within it. Additionally, at any level in the campaign, a participant can be added directly to the team list.

To view/add team members at any level in a campaign, click an entity in the Gantt chart and then click the Resources tab. A newly added team member may not have an avatar image. An instance is shown below:

Newly added user does not have an avatar

Newly added user does not have an avatar

Understanding the naming convention of the image files

The images display only if the image files are named using the canonicalname_domainname convention. To know the value of domain name and canonical name, follow these steps:

  1. Navigate to http://localhost:4502/crx/index.jsp.
  2. Log in using the credentials of the user whose domain name and canonical name is to be determinded.
  3. The UserID is displayed of the format lcu::domainname::canonicalname. Note the domain and canonical names from the string.

For example, for an administrator the name is displayed as lcu::DefaultDom::SuperAdmin. Hence, the domain name is DefaultDom and canonical name is SuperAdmin.

Adding an image

Let us add an image for a newly-added user named Shashank Kapoor.

  1. Navigate to ICR_SOURCE/integratedcontentreview/package_data/content/icr/assets/user-images.
    Note: ICR_SOURCE folder is the folder where you extract the provided source code of the solution interface. Refer to this help page to read more.
  2. Add an image with the file name shakapoo_DefaultDom.jpg.
    Note: To update an existing image, replace the image file with a new image file. The image file is scaled to 45 x 58 pixels in size. The image filenames are case sensitive.
  3. Create a directory named shakapoo_DefaultDom.jpg.dir.
  4. In this directory create a file named .content.xml. Add the following code to it:
    <?xml version=”1.0″ encoding=”UTF-8″ ?>
    <jcr:root xmlns:jcr=”http://www.jcp.org/jcr/1.0″ xmlns:nt=”http://www.jcp.org/jcr/nt/1.0″ jcr:primaryType=”nt:file”>
    <jcr:content jcr:primaryType=”nt:unstructured” />
    </jcr:root>
  5. Save and deploy the customized solution interface. To know more, refer to this article.

After updating the image for the above instance it shows in the solution interface as shown below:

User with an avatar image added

User with an avatar image added

Read more about adding team members here, in the ICR solution guide.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Exciting new articles on using Managed Review & Approval Solution Accelerator 9.5

Posted on September 20, 2011 by Gilbert Yu | Comments (0)

Here are two more great posts from Alexandra Phillips on Managed Review & Approval Solution Accelerator 9.5. You will certainly find these post useful if you are implementing Managed Review & Approval as Alexandra shows you how to display a list of participants in the review emails and how to retrieve a RSS XML file to list all the comments made by reviewers for a document!

Check out the following articles:

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Rebranding the ICR email templates

Posted on September 15, 2011 by Ashish Gupta | Comments (0)

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.

***

Integrated Content Review solution sends out system-generated email notifications to team members and participants, for various events. Templates used for these email can be customized as per your branding requirements.

This customization scenario involves the following top-level steps:

  1. Locating the email template files
  2. Customizing the images in the email template files
  3. Customizing the content in the email template files
  4. Knowledge of all the available variables to customize the content in Step 3

For detailed information about these steps, refer to this (PDF) document.

See also:
This matrix of system-generated email notifications sent to participants.
This page, to know more about ICR solution.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Writing pre- and post-stage hooks for Integrated Content Review solution

Posted on September 15, 2011 by Suhas | Comments (0)

The Review, Commenting, and Approval building block, part of the Integrated Content Review solution, allows you to inject said functionality or custom Document Services processes at any point in your solutions workflow. You can add functionality or custom processes prior to or after staging, called Pre-stage and Post-stage hooks respectively. See Writing Pre- and Post-Stage Hooks for more information and a quickstart to help you get started.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Rebranding the ICR solution interface

Posted on September 15, 2011 by Ashish Gupta | Comments (0)

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:

  1. Open the Campaign Portal project in the Package Explorer view, in Flash® Builder®.
  2. 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.
  3. 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

    Path of ICR logo file

  4. 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

Dimensions of ICR logo file

 

See also:
This page, to know more about ICR solution.
The solution guide to get started with the solution.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

ICR customization to display custom asset attributes in advanced search

Posted on September 8, 2011 by Ashish Gupta | Comments (0)

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.

***
In the Assets view of the Integrated Content Review solution interface, you can find an asset using either basic or advanced search. You can perform advanced search using search attributes, such as campaign name, manager, state, status, and timeline. Besides these attributes, you can create new search attributes. These custom attributes appear in the advanced search options and search results.

To modify the advanced search parameters, you must update the FML file describing an asset. A few custom attributes for assets are predefined—for example, brand of an asset, asset height, asset width, and so on.

The following steps use a pre-defined, asset-level attribute to modify an asset’s FML file:

  1. Open workItem.fml located at: ICR_SOURCE/integratedcontentreview/package_data/apps/solutions/icr/assetDefinitions/.
  2. Add properties (described below) in the entity for workitem.fml.
  3. Update the solution interface. (Refer to Setting up your development environment to do so.)

Following is an explanation of the properties of the attribute:

  • visible: Marking its value as True makes it visible in the search results.
  • searchable: Marking its value as True makes it visible in the advanced search pane.
  • extendedPropertyPath: Path of this attribute.
  • assetPropertyType: Marking assetPropertyType as “extended” indicates using extendedPropertyPath attribute, instead of searchPath attribute, to search for the brand name.

For example, the following sample can be used to add a new attribute titled Brand in the advanced search pane.

<property name=”brandName” type=”string”>
<annotation name=”DDS”>
<item name=”displayName”>Brand</item>
<item name=”visible”>true</item>
<item name=”searchable”>true</item>
<item name=”searchPath”>WorkItem.attributes.brand</item>
<item name=”columnOrder”>5</item>
<item name=”basicSearchEnabled”>false</item>
<item name=”extendedPropertyPath”>WorkItem.attributes.brand</item>
<item name=”assetPropertyType”>extended</item>
</annotation>
</property>

An instance of the advanced search pane and the search results, as they appear after this customization, are shown below.

Custom attributes in advanced search pane

Custom attributes in advanced search pane

Further references:
This ICR page, to know more about the solution.
The solution guide to get started with the solution.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Changing skins and styles of ICR UX components

Posted on September 2, 2011 by Philomena Dolla | Comments (0)

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.

***

The look and feel of a UX component in the Integrated Content Review (ICR) solution can be customized to suit your business needs. You can choose to apply specific formatting and coloring styles, or even change the skin of the component.

The Asset Details pod of the solutions interface, for example, can be modified to change the way the asset attributes are displayed. In the existing layout, the Asset Details pod displays all the attributes in a single pane. You need to scroll through the pane when the attributes extend beyond the display area.

To minimize scrolling and for better accessibility, you can change the single pane format to use an accordion menu such that the system defined attributes and the custom attributes are displayed in two different panels. (This example assumes that a user is allowed to define any number of custom attributes for any asset at design time.)

To modify the Asset Details pod:

  1. Make a copy of the existing AssetDetailsPodSkin (CustomAssetDetailsPodSkin.mxml) skin and edit it.
  2. Modify the CSS (icr.css) to use the new skin.
  3. Specify the styling changes as part of the code for the skin itself, or update the CSS and apply it to the skin. For example, you can centre and underline the panel labels by associating a style with the accordion header.
    Defining your style in the CSS:

    Associating the custom style with the accordion header    :
  4. Save and deploy the customized solution interface. See this blog post for more information on saving and deploying.
    System Attributes Panel:

    Custom Attributes Panel:

You can view the the CustomAssetDetailsPodSkin.mxml file here. See UX components for more information on UX components. For background information about setting up the ICR development environment, refer to this blog post.

 

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

ICR: Update the campaign portal SWF without redeploying the package

Posted on September 1, 2011 by Samartha Vashishtha | Comments (0)

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.

***

If you’re working with just the Flex project that ships with Integrated Content Review, you may find it convenient to update the campaign portal SWF directly without redeploying the entire package (template-integratedcontentreview-pkg.zip).

You can generate the SWF in one of the following ways:

  • Clean the solution interface project from within Flash Builder:
    • In Flash Builder, select Project > Clean. The contents of the default project output folder—ICR_SOURCE\integratedcontentreview[CampaignPortal]\bin-debug—are updated.
    • Rename the ICR.swf file in this folder to campaign_portal.swf.
  • Run build.xml:
    • Run the build.xml in the ICR_SOURCE\integratedcontentreview[CampaignPortal] folder. The contents of the ICR_SOURCE\integratedcontentreview[CampaignPortal] folder, which includes campaign_portal.swf, are updated.
Once you have the campaign_portal.swf file available, follow these steps to update it in CRX:
  1. Navigate to http://localhost:4502/crx/index.jsp and log in using admin credentials.
  2. Click Content Loader.
  3. Click Browse and select /content/icr.
  4. Click Choose File and select the campaign_portal.swf file that you just generated.
  5. Click Import.
For background information about setting up the ICR development environment, refer to this earlier blog post.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Setting up the ICR development environment

Posted on August 29, 2011 by Samartha Vashishtha | Comments (7)

This is the first blog post in the series on customizing the Adobe Integrated Content Review solution.

***

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:

  1. Set up prerequisites
  2. Locate the solution interface and required dependencies
  3. Understand available projects
  4. Set up available projects in Flash Builder
  5. Set up Java projects in Eclipse
  6. Build and deploy the solution interface

For detailed information about each of these steps, refer to this PDF document (download).

Watch out this space for more customization scenarios for ICR!

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Integrated Content Review user scenarios

Posted on August 18, 2011 by Samartha Vashishtha | Comments (4)

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:

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)