LiveCycle/ADEP Solutions

Removing Sample Data and Users from Correspondence Management Solution

- Mayank Gupta, Computer Scientist at Adobe

Adobe LiveCycle Correspondence Management Solution provides some sample collateral and creates some sample users so that developers can start using the application and make use of these samples to know about and learn the product capabilities. It is highly recommended to remove these sample assets and sample users when the solution is deployed on to a production server.

Steps to remove sample assets and sample users:

1. Removing sample assets by uninstalling them from package manager:

  • Go to http://[hostname:port]/lc/crx (on author instance)
  • Login as admin
  • Click Package Manager
  • Click on Package with name “cm-sampleassets.zip”
  • Click More dropdown in action bar (This action bar has other actions like Edit Build etc.,. , More option is in the right most area of this bar)
  • Click Uninstall
  • Click Uninstall again on confirmation dialog
  • Wait for sometime till you see a message like “Package uninstalled in <some>ms” in the Activity Log
  • Now if you log on to CM Manage Assets UI , you will not see any sample assets. If you are still seeing them then restart the server.

2. Removing sample users from CRX user administration:

  1. Go to http://[hostname:port]/lc/crx (on author instance)
  2. Login as admin
  3. Click User Administration.
  4. Note: Correspondence Management creates Todd Goldman (tgoldman), Caleb Lopez (clopez), Gloria Rios (grios), Frank Kricfalusi (fkricfalusi), Jocelyn Robinson (jrobinson), and Heather Douglas (hdouglas) as the sample users.
  5. In the user administration dialog , Navigate to each of these users and click Remove user. Now you cannot log in to the Manage Assets UI with any of the above usernames.

Follow the steps mentioned above in 2 and remove sample users from publish instance as well. There is no need to uninstall sample assets from publish instance as they are installed on author instance only.

Adding a custom service in Correspondence Management Solution

- Mayank Gupta, Computer Scientist @ Adobe

Steps to add a custom service in Correspondence Management solution are as follows:

  1. The implementation for this user story involves code changes and rebuilt. So, one is required to setup the development environment via steps mentioned @ Setting up development environment.
  2. Add your sample custom service interface and implementation class in the CorrespondenceManagementSolutionTemplate/Services project for example @ com.adobe.icc package in the source code. See the sample @ http://blogs.adobe.com/LiveCycleHelp/files/2012/06/SampleCustomService1.zip.
  3. Now define your service as a spring bean. For this, add the following entry in your CorrespondenceManagementSolutionTemplateServicesresourcesMETA-INFspringcmadobe-cm-spring-config.xml file: <bean id=”sampleCustomService” class=”com.adobe.icc.SampleCustomServiceImpl” />
  4. Now expose your spring bean as a osgi-service. For this, add the following entry in your CorrespondenceManagementSolutionTemplateServicesresourcesMETA-INFspringosgi-context.xml file: <bp:service interface=”com.adobe.icc.SampleCustomService” ref=”sampleCustomService” > <bp:service-properties><entry key=”connectors.httpinvoker” value=”true” /> <entry key=”connectors.httpinvoker.alias” value=”/sampleCustomService” /> <entry key=”connectors.remoting” value=”true” /> <entry key=”connectors.remoting.id” value=”sampleCustomService” /> </bp:service-properties> </bp:service>
  5. Rebuild and redeploy the Solution template to view the changes. For information on rebuilding and redeploying, see Building and deploying the Solution Template.
 

Correspondence Management: Move active assets betwixt systems

- Samartha Vashishtha, Content and Community Lead @ Adobe

Correspondence Management 9.5 now lets you conveniently move active assets from one system to another. You can export the selected assets from the source system as a ZIP package and import the ZIP package into the target system.

This functionality is useful in several scenarios; for example, when you’re moving assets from a development environment to a production environment.

Read the complete post at The Doc Fox.

Enter special characters in Correspondence Management asset names

- Samartha Vashishtha, Content and Community Lead @ Adobe

Sometimes, you may want to create Correspondence Management solution assets that contain special characters in their names. To do so, you must first define the list of special characters that you want to use in the tbxeditor-config XML file.

Read the complete post at https://blogs.adobe.com/samartha/2012/05/enter-special-characters-in-correspondence-management-asset-names.html.

Author-instance clustering for Correspondence Management

- Samartha Vashishtha, Content and Community Lead @ Adobe

We’ve added a brand new section to the Installing the Correspondence Management Developer’s Guide explaining how you can set up author-instance clustering for Correspondence Management.

When the Correspondence Management solution is deployed, the author instance runs on the same server as LiveCycle ES3. However, setting up the LiveCycle cluster doesn’t automatically configure the Correspondence Management author-instance cluster. You must set up this cluster manually.

Author-instance clustering has no dependency on LiveCycle clustering. The LiveCycle cluster acts as a backend system for author instance clustering when LiveCycle is integrated with the Correspondence Management solution. The shared nothing mode of clustering is supported for Correspondence Management.

You can read the full technical article here.

Postprocessing your correspondence

Saket Agarwal

Correspondences created in enterprises would typically have to be integrated to a back-end process for further distribution (via email, fax, print), document processing (apply digital signatures, encryption, etc.) or archival of the correspondence.

The Adobe Correspondence Management solution provides a convenient way to achieve this by leveraging orchestrations/processes on the ADEP Document Services platform for defining the back-end process (that can use one or more Document Services, based on the enterprise requirements), and providing the ability to easily bind them to a given correspondence template.

Read more about creating a postprocess for the CM solution on the Document Server.

Once such processes are created on the Document Server, can then be mapped to a Letter template in the  Postprocess drop down of the Letter Template Editor (as shown below), where the available postprocesses (as defined on the Document Server) are listed:

 

 

 

 

 

 

 

Tip: If you create a new process, with an existing Manage Assets UI session opened, your process will not be listed in the Postprocesses dropdown until you relaunch or refresh (F5) the Manage Assets browser window (or open the Manage Assets UI in a new browser window).

When the correspondence creation is complete (using the Create Correspondence UI), users can Submit the correspondence (see snapshot below indicating the Submit button), which invokes the associated/mapped postprocess for that Letter template, with the final correspondence PDF and XML data (used to generate the PDF). The postprocess, which would be an orchestration, can then act upon the document (PDF) as necessary.

 

——-
Original article at http://blogs.adobe.com/saket/cm-postprocess/.

Using Lists and Conditions in Correspondence Management to create complex template rules

The Correspondence Management Solution presents unique concepts of List and Condition assets (aka modules), to enable advanced correspondence template design. These asset types allow defining rules for content inclusion, that may be quite complex by using a combination of (nested) Lists and Conditions.



Read the complete post here.

Updated Adobe Digital Enterprise Platform (ADEP) Help Content!

- Gilbert Yu

As part of our continuous effort to make the help content better for you, we have recently updated the following help:

  • New section for installing the Experience Server as a Windows service.
  • Update to describe how to obtain the Customer Experiences Solutions Quickstart.
  • New section for installing the Experience Server as a Windows service.
  • 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!

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/10/updated-adobe-digital-enterprise-platform-adep-help-content.html.

Quick Tip: CSS to customize the TabbedViewNavigator and ActionBar in Flex Mobile Applications

- Kevin Schmidt

If you are building Flex Mobile applications on of the first things you will end up wanting to change is the default look of the TabbedViewNavigator and ActionBar! This can be done through skinning but for simple changes it can be done much quicker with CSS. The CSS below illustrates how to do this.

@namespace s "library://ns.adobe.com/flex/spark";

s|TabbedViewNavigator #tabBar {
	chromeColor:#028bba;
}

s|ActionBar
{
	chromeColor: #028bba;
	fontSize: 28;
	fontWeight: bold;
}

Save the file as a CSS file and include it in the Flex Mobile application using MXML

<fx:Style source="file_name.css" />

This is the CSS that I used for mapi and ends up looking like this:

All the CSS properties for both the TabbedViewNavigator and ActionBar can be found here:

TabbedViewNavigator
ActionBar

A general article on Styling and Themes can be found here: Styles and themes

——-
Original article at http://www.underprise.com/2011/09/22/quick-tip-css-to-customize-the-tabbedviewnavigator-and-actionbar-in-flex-mobile-applications/.

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.

Go to Top