***

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

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 added

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

• Upgrading to Document Services: The upgrade documents had significant updates, particularly concerning topics related to Business Activity Monitoring. As the cookie crumbles, ADEP Document Services is the last release to support Business Activity Monitoring and, hence, the BAM server cannot be upgraded, but it can certainly be reused to work with the new Document Server. See the Upgrade to Document Services documentation.
• Connector for SharePoint: All sites on the SharePoint server are available for configuration for all Document Services features by default. A new feature for the Connector for SharePoint allows you to restrict configuration and usage of Document Services features on a specified SharePoint site. The Configure ADEP Document Services – Connector for SharePoint tells you how you could do this.
• Plug-in for Hyperic HQ: Hyperic HQ allows you to monitor and manage your web infrastructure, server, services, and devices of ADEP Document Server. See Using the plug-in for Hyperic HQ, a new document, to know more about Hyperic HQ, its installation and usage procedures.
• Action Script Reference was refreshed with addition of new Packages and APIs for Customer Experience Solutions (Correspondence Management and Integrated Content Review in particular).
• Correspondence Management Developer’s guide had significant updates. The guide now has download locations of all jar files’ required to set up your development environment for the Correspondence Management solution.
• Disaster recovery for Correspondence Management explains how to back up and restore your Correspondence Management data.

Until the next time we have more updates, Adios!

-

ADEP Community Help and Learning Team

Problem: The Flex tile did not populate (it was blank), although the HTML tile appeared fine.

Solution: Use Flex SDK 4.5. Do not use version 4.5.1

Note: This problem/solution applies to ADEP 10.0.0.0. I don’t know what version of the SDK that future ADEP/CAF releases will support out-of-the-box.

If you used Flex SDK 4.5.1 by mistake, here is how to configure the project and tile to use Flex SDK  4.5.0:

1. In Flash Builder, right-click the Flex project for ADEP and click Properties.
2. In the properties tree, select Flex Compiler.
3. At the top of the Flex Compiler panel, set the SDK version to Flex 4.5.
4. Click OK and when the scary message about overwriting the html-template pops up, click OK.
5. Open the catalog file (.cxml).
6. Locate the tile:TileClass element for your tile and in the tile:Content child element, change the value of the flexSDKVersion attribute to 4.5.0.

   <tile:TileClass fitContent="true" height="300" label="WatchedFunds" name="WatchedFunds" width="600">
         <ct:Metadata>
              <ct:Description/>
         </ct:Metadata>
         <tile:Content contentType="application/x-shockwave-flash" flexSDKVersion="4.5.0" loadAs="module" uri="${catalogURL}/tiles/WatchedFunds/WatchedFunds.swf"/>
   </tile:TileClass>

7. Save the file.

Scott (Brodersen)

<quote>

Yes, Gravity logging APIs can be used in Mosaic as-is. To view the log output:

1.       Open CRXDE lite in a browser and log in
2.       Navigate to /libs/mosaic/components/index/index.jsp
3.       Locate the line in the file that initializes the flashvars variable. In 10.0 this should be on line 65
4.       After that line, add a new line:

flashvars.mdebug = true;

5.       Click the “Save All” button to save the changes

Then, when a new application is launched, a debug window will appear with a “Log Viewer” tab. Note that the debug window will appear in the upper left corner of the browser in a layer that will be behind html or pdf content, so if your application’s layout has html or pdf content in the upper left region you may not be able to see the debug window.

</quote>

What was the OP’s result you may ask?

“That debug window certainly is useful. It has much more useful information than I was expecting. The DOM Viewer is especially nice. It is good to be able to confirm which libraries get loaded.”

This is the forum post:  http://forums.adobe.com/message/3973532#3973532

Here are the Composite Application Framework docs: http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS6e4bbd81fea965ef18585f3012fda7a1d5e-8000.html

Here are the Client Component Framework docs: http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS3ad6fd7a5b41dea4-28996cf812f6f54ab88-8000.html

Client Component Framework ActionScript reference: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/index.html?filter_livecyclees=10.0&filter_flashplayer=10.2&filter_air=2.6#top — see the com.adobe.gravity.* packages.

Scott

How to Create a Data Services application for the Experience Server that returns data – Sound familiar? This is a remix of this walkthrough in the ADEP help. Lin’s version is friendlier to CRX and Maven novices.

How to create class/jar files for data service project without using maven – Not ravin’ about Maven? This is for  you!

ADEP Data Services Complete Quick Start – Boils down much of the product help content to include only procedures. If you just want to do, and knowing why is not the immediate priority, this is perfect for you.

Scott (Brodersen)

•  Installing and Deploying Solutions

• New section for installing the Experience Server as a Windows service.
• Update to describe how to obtain the Customer Experiences Solutions Quickstart.

• Installing Experience Services

• New section for installing the Experience Server as a Windows service.

• Developing for ADEP Experience Services

• New section about the ADEP Client Component Framework.

NOTE: Be sure to update any cached local copies of the PDF versions you have on your computer.

Please continue to help us improve the ADEP help content by adding feedback at ADEP documentation site. We appreciate the comments you have provided so far!

• 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:

• The ADEP Client Component Framework section of  Developing for ADEP Experience Services

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

• Generate libraries for the Client Component Framework (model-driven development for ADEP Data Services)
• Client Component Framework blog
• Adobe forum

Scott

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.

Check out the following articles:

• Displaying a list of participants for a review stage in email for Managed Review & Approval Solution Accelerator 9.5
• Comment recognition for the Review Tracking Sheet in Managed Review & Approval Solution Accelerator 9.5