Posts tagged Integrated Content Review

Adding user images in ICR Solution Interface

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 avatarNewly 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 below:

User with an avatar image addedUser with an avatar image added

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

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/11/adding-user-images-in-icr-solution-interface.html.

Project and team hierarchy in ICR

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.

——-
Original article at http://blogs.adobe.com/samartha/2011/09/project-and-team-hierarchy-in-icr.html.

Building a Better Digital Customer Experience Doesn’t Have to Cost MILLIONS

In my role I spend a lot of time talking with organizations in both Corporate and Government sectors about creating great customer experiences. In fact, understanding the challenges and opportunities for these organizations is the aspect of my role that I enjoy the most. These organizations all want to achieve great digital customer experiences…who wouldn’t? […]

——-
Original article at http://www.avoka.com/blog/?p=1424.

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

- Suhas Yogin

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.

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/writing-pre-and-post-stage-hooks-for-integrate-content-review-solution.html.

ICR customization to display custom asset attributes in advanced search

- Ashish Gupta 

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

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/icr-customization-to-display-custom-asset-attributes.html.

Rebranding the ICR email templates

Ashish Gupta 

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.

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/rebranding-the-icr-email-templates.html.

Rebranding the ICR solution interface

Ashish Gupta 

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 filePath 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 fileDimensions of ICR logo file

 

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

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/rebranding-the-icr-solution-interface.html.

Changing application fonts for the ICR solution interface

Philomena Dolla

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

***

The applications shipped as part of the Integrated Content Review (ICR) Solution interface use certain default fonts to display text. You can customize your application and change the default font to suit your requirements. The CampaignPortal Flex application, for example, uses the MyriadPro font.

The default font files for the CampaignPortal project are located at campaign_portalsrcmainflexassetsfonts. The fonts used by the application are defined in the style sheet file, icr.css.

To change the font, create new font files for the project and update the style sheet, icr.css, with the path to these new font files:

    1. In Flash Builder, open the CampaignPortal project in the Package Explorer view.
    2. Copy the font files that you want the application to use.
    3. Navigate to CampaignPortal > src > main > flex > assets > fonts.
    4. Right-click fonts and select Paste to paste the font files to the fonts directory.
    5. Navigate to CampaignPortal > src > main > flex > css > icr.css.
    6. Open the style sheet, icr.css, in the editor.
    7. Update the paths to the font files to point to the new font files.
    8. Rebuild and redeploy the package. See this blog post for more information on building and deploying.

For background information about setting up the ICR development environment, refer to this blog post.

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/changing-application-fonts-for-the-icr-solution-interface.html.

Changing skins and styles of ICR UX components

- Philomena Dolla

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.

 

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/changing-skins-and-styles-of-icr-ux-components.html.

ICR: Add custom asset attributes

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

***

Integrated Content Review lets you define custom asset attributes that are listed in the solution interface Asset Details pod as well as the Task Details area in the Adobe Creative Suite Task List Extension for ICR.

In this blog post, we’ll learn how to perform the following tasks:

  • Create custom attributes using Adobe CRXDE
  • Modify the appropriate orchestration in Workbench to ensure that custom attributes are displayed in the Task List extension
  • Test the newly added attributes

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

Optional background reading

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/icr-add-custom-asset-attributes.html.

Go to Top