Planning how to process orders from your MarcomCentral store

If you want your workflows to process only print items, skip the instructions for non-print items. When you copy the sample MarcomProcessJobTicket workflow and modify it for your needs, remove the branch that processes non-print items.

For reference, this table lists the two RICOH ProcessDirector job properties that provide information required to process print items in the sample MarcomProcessJobTicket workflow.

Create a table similar to the one above to record the RICOH ProcessDirector job properties that provide the information required to process print items in your job ticket workflow. Add as many rows as needed.

For reference, this table lists the RICOH ProcessDirector job property that provides information required to process non-print items in the sample MarcomProcessJobTicket workflow.

Create a table similar to the one above to record the RICOH ProcessDirector job properties that provide the information required to process non-print items in your job ticket workflow. Add as many rows as needed.

The procedures for configuring RICOH ProcessDirector to retrieve and process MarcomCentral orders discuss two ways to supply information:

• XML files

  You can create a set of XML files, one for each item ordered at your MarcomCentral store. An ApplyXSLTransform step uses the XML file to set values for the job properties of the item. The sample MarcomProcessJobTicket workflow uses this method.

  To create the XML files, you map the XML elements used by each item to RICOH ProcessDirector job properties. The next step in this procedure explains how to create the XML files.

• AssignJobValues steps

  You can add to your job ticket workflow an AssignJobValues step for each item ordered at your MarcomCentral store. For example, if SKU IDs identify items, you can use an AssignJobValues step for each SKU ID. In the step, you assign all the job properties required to produce the item.

You can use other methods to supply the information required to process the items ordered at your MarcomCentral store. For example, if you have the Archive feature, you can store print items and the job properties required to print them correctly in a repository. When RICOH ProcessDirector processes the job for the print item, it can retrieve the PDF file and the properties required to print it from the repository.

The file contains the XML element or elements that identify the item and an XML element for each job property required for print and non-print items. Each property specifies the value required to process the item.

A separate file is required for each item, even if some items require the same processing information.

The jobticketsReceived.xslt and downloadOverrides.xslt files are in this directory:

• /aiw/aiw1/testfiles/Marcom (Linux and AIX)
• C:\aiw\aiw1\testfiles\Marcom (Windows)

• In an earlier step, you mapped MarcomCentral order elements to RICOH ProcessDirector job properties in a table. Refer to that table as you prepare the input to the tool.

• After you create the stylesheet, save it in a file named orderToOverrides.xslt.

This example shows the contents of the sample orderToOverrides.xslt file supplied with the MarcomCentral Connect feature:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet version="1.0" 
	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
	xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs">
  <xsl:output method="text" encoding="UTF-8"/>
  <xsl:template match="/">
    <xsl:variable name="var1_initial" select="."/>
    <xsl:for-each select="Order">
      <xsl:variable name="var2_current" select="."/>
      <xsl:value-of select="concat('Job.Marcom.OrderNumber=', OrderNumber, 
			'&#10', 'Job.Marcom.OrderId=', ID, '&#10', 'Job.Info.Attr1=', 
			ShippingAddress/Address1, ' ', ShippingAddress/City, ' ', 
			ShippingAddress/State, ' ', ShippingAddress/Zip, '&#10', 
			'Job.CustomerName=', User/Email, '&#10', 'Job.Info.Attr2=', 
			count(OrderDetails/OrderDetail))"/>
    </xsl:for-each>
  </xsl:template></xsl:stylesheet>

• In an earlier step, you mapped MarcomCentral ticket elements to RICOH ProcessDirector job properties in a table. Refer to that table as you prepare the input to the tool.

• Make sure that the stylesheet maps the job ticket element or elements that look up the information required to process each item in an order.

• Make sure that the stylesheet maps the order element that associates each job ticket with its order. In the sample MarcomProcessJobTicket workflow that element is OrderDetails/OrderDetail/OrderID, which is mapped to the MarcomCentral order ID job property.

• After you create the stylesheet, save it in a file named jobticketToOverrides.xslt.

• In an earlier step, you recorded in tables the RICOH ProcessDirector job properties required to process print and non-print items. In another step, you assigned XML elements to the job properties. Refer to those tables as you prepare the input to the tool.

• After you create the stylesheet, save it in a file named itemToOverrides.xslt.