Archive for September, 2011

ADEP developers: new Client Component Framework help content!

Let your journey to the land of really, really cool modular Flex applications begin:

  • Develop large applications comprised of  loosely-coupled modules
  • Define service APIs  using interfaces, deployed separately from the implementation
  • Consume  services without a priori knowledge of the implementation
  • Use multiple (potentially conflicting) versions of the same classes in the same application

While Client Component Framework has been out there as part of  ADEP Experience Services, the help content has been brewing and is now live. Prepare yourselves for some heavy doses of dependency injection! Here’s where you can go to get the party started:

And here’s some information that is already out there:

Scott

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

Installing and working with the Windows service for the ADEP Experience Server

Although you can start your ADEP Experience Server by double-clicking the Quickstart JAR file or the Windows batch file, most people will find it convenient to install the Experience Server as a Windows service. It will configure the Experience Server to start automatically when your Windows restarts and, helps you control the start and stop operations of the Experience server by using the Services control panel.

Install Experience Server as a Windows service

To install a Windows service for your Experience Server:

  1. Open the command line interface and navigate to the [ExperienceServer root]/opt/helpers/ directory.
  2. Execute the instsrv.bat <serviceName> command to install the Experience Server as a Windows service.

Verify the installed Windows service

You can verify the installed Windows service in the Services control panel. To open the Services control panel,  execute the start services.msc command from the command line interface or select Start > Administrative Tools > Services.

Windows service operations

To start the Windows service, do one of the following:

  • In the Services control panel, select the Windows service and click Start.
  • In the command line interface, execute the net start <serviceName> command.

To stop or restart the Windows service for the Experience Server, click Stop or Restart, on the Services control panel.

Uninstall the Windows service

To uninstall the Windows service, execute the instsrv.bat -uninstall <serviceName> command on the command line interface. The Windows service gets removed from the Services control panel.

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

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)

Exciting new tutorial using LiveCycle Designer 9.5

Twin Technologies continues to share their knowledge with the Adobe LiveCycle community. Jack Freudenheim and Benjamin P. Lyons show you how to prepopulate drop-down lists in a dynamic PDF form using a back-end datasource in a tutorial. Check out this very informative tutorial here.

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

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

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

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

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)

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

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

Changing application fonts for the ICR solution interface

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_portal\src\main\flex\assets\fonts. 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.

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