Media/Stock name from an XMPie uStore product not coming over

[JyriS-Xerox]

By default, uStore includes JDF nodes for several paper types, folding and colour settings. These nodes are available when you set up JDF requirements in the Product Properties page.

If your job includes additional requirements, such as printing on named stock, you need to create additional JDF node sets. To ensure that your product is printed according to the JDF specifications, make sure that you follow these steps:

1. Create the required property in the Product Properties page.
2. Create the new JDF Node Set. The JDF Node Set that you create is added to the list of options available when you set up JDF requirements in the Product Properties page. See To add new JDF node sets below.
3. Create the new JDF Node. See Setting Up JDF Nodes below.
4. Assign the required JDF Node set to the property options in the Product Properties page

To add new JDF node sets:

1. Select Presets>System Setup>JDF Node Set.
2. On the JDF Node Set page, click Add New.
3. In the Display Name box, enter a name for the node set. For example, if your product needs printing on SRFRed Stock, enter PrintOnSRFRedStock.
4. Click Save.

The Node Set is added to the list and is available in the Product Properties page when you set up customer input controls of the following types: Drop-down lists, radio buttons, and gallery/grid view lists.

To make sure that uStore sends the correct information when it creates the JDF file, you need to set up the JDF Node with the required XML code.

To add a new JDF node:

1. Select Presets>System Setup>JDF Node.
2. On the JDF Node page, click Add New.
3. In the JDF Node Set ID list, select the JDF Node Set that you want to set up. For example, if you create a JDF Node Set for printing on SRFRed Stock, select the PrintOnSRFRedStock node set.
4. In the Node XML box, enter the XML code for the new JDF node. For example, enter @ProductID="SRFRED".
5. In the Node Target Xpath box, enter the location of node in the JDF file. For example, the Media attribute should be located at //ns:ResourcePool/ns:Media.
6. Click Save.

The new node set is added to the list. Every time a product includes this property option, the XML code will be added to the JDF file. For your reference, uStore saves all JDF files at \\[ServerName]\App\JDF. (Thanks to Steve F and Per F for validating this information.)

[JavierM-Xerox]

FFCore supports both use of @DescriptiveName and @ProductID within the JDF.

@DescriptiveName is mapped to media-description in the XPIF print ticket.

@ProductID is mapped to media-key in the XPIF print ticket.

I do not know what that printer supports for XPIF ticketing but it seems that media-description is not supported. I would suggest mapping the stock names to @ProductID within uStore.

PS>If you add a Save component after the Print ticket you can save the XPIF version of the print ticket that's sent to the printer.

[GillesML]

Hi,

I'm having some issues with a print file coming over from uStore to FreeFlow Core workflow to print to a 6180 Docuprint. The job is set to have page 1-2 on thick stock and 3-6 on thin stock all 2 sided. When it arrives at the 6180 it is recognizing sides printed and that there are 2 blocks of exception pages (1-2 and 3-6) unfortunately the stock for both show up as unspecified.

I've made sure that the printer's stock library is matching the descriptive name in the JDF node setup in uStore.

Nodes in uStore

@DescriptiveName="Media Type Thick"

@DescriptiveName="Media Type Thin"

Names in the printer's stock library:

Media Type Thick

Media Type Thin

Should the uStore JDF node set have more entries so the the 6180 can properly ID the stock? Or is there a specific naming convention I should be using? Like say no spaces or capital letters?