Cannot evaluate expression on Banner page

[Jedidiah]

Sent you a message

[JavierM-Xerox]

Send me the workflow and the exact JDF you are using (Once something launches I am generally done with it so it would help to get the released JDF).

[Jedidiah]

Same thing couldn't get JDF #2 to work.

[JavierM-Xerox]

I would start one at a time. Try only using the variable for the main stock with JDF #2.

If you get that working make a copy of that file and add the stock color from JDF #3 to the new file and send that in.

[Jedidiah]

HI Javier,

So I've run the Sample (JDF - 5) against Freeflow core using Alces. I'm am still receiving an error for the variables of mainStock and Color, despite the fact that they are present.

Errors in log are
28-Jul-2015 14:20:11,665 [read2]: [ERROR] WorkflowEngine TraverseWorkflowNodes - TraverseWorkflowNodes->ExecuteNode:Caught com.xerox.solutionsdk.workflow.Expressions.ExpressionException. Unable to find color!. Job= PlatformJob(Id = 3.0, Status = processing, isJobGroup = false, , hasDocGroup = false, has 0 DocGroups, 1 inputDoc(s), 1 outputDoc(s), 8 resources). node=Node(seqNo: 7, Id: 60, next: 8, TaskExecuteService(92, , send individually preActions , Watermarks))
28-Jul-2015 14:20:11,665 [read2]: [INFO ] WorkflowEngine MarkJobAbortedInMemory - exception Unable to find color!
at com.xerox.solutionsdk.workflow.Expressions.ParameterGroup.GetValueFromParent(String[] qualifiedName, Object current)

And for Stock:

28-Jul-2015 14:13:48,754 [read3]: [ERROR] WorkflowEngine TraverseWorkflowNodes - TraverseWorkflowNodes->ExecuteNode:Caught com.xerox.solutionsdk.workflow.Expressions.ExpressionException. Unable to find mainStock!. Job= PlatformJob(Id = 3.0, Status = processing, isJobGroup = false, , hasDocGroup = false, has 0 DocGroups, 1 inputDoc(s), 1 outputDoc(s), 6 resources). node=Node(seqNo: 7, Id: 60, next: 8, TaskExecuteService(92, , send individually preActions , Watermarks))
28-Jul-2015 14:13:48,754 [read3]: [INFO ] WorkflowEngine MarkJobAbortedInMemory - exception Unable to find mainStock!
at com.xerox.solutionsdk.workflow.Expressions.ParameterGroup.GetValueFromParent(String[] qualifiedName, Object current)

The other variables for print information seem to work fine.
Are we sure that the variables shown in the Xerox Freeflow Core 4 Help document are correct?
Mainly $FFwfJob.mainStock$ and $FFwfDoc.color$...

On the plus side the Job information view in Freeflow core now shows a value for main stock when the stock is put as product ID in the JDF.

[JavierM-Xerox]

The references at the root of the LPP node are for the main stock, color and plex.

The references in the LPP elements that are inside the top LPP element are for exceptions - strock, color and plex.

The example shows both levels of ticketing.

[Jedidiah]

I thought it seemed redundant as well. That's just the way XMPIE has decided to send it across.

Yes. I did notice that example (JDF - 5).

I'm guessing this provides Main Stock information and Main Colour information but if I understand you correctly

I wouldn't be able to set apart a set of pages based on their colour.

Thanks for the information.

[JavierM-Xerox]

If you look at JDF #5 in the Job Information folder in the SDK you will see that the LPP media and plex in your JDF should map to media and plex exceptions.

I believe FFCore supports the media references in DPP. However, I would remove those off the JDF. They convey the same information as the media references in LPP so they are superfluous.

THe information in the JDF will be mapped to a print ticket that will pass through FFC and be consumed to the printer.

FFCore cannot select pages for manipulation based on their ticketing attirubtes.

[Jedidiah]

Thanks for your prompt response.

They are indeed referenced in line with LPP and DPP

I.E.

   <LayoutPreparationParams ID="LPP1" PartIDKeys="RunIndex" Status="Available" Class="Parameter" Sides="TwoSidedFlipY">
      <LayoutPreparationParams ID="LPP4856" RunIndex="0~4 " Sides="TwoSidedFlipY">
        <MediaRef rRef="M4856" />
      </LayoutPreparationParams>
      <LayoutPreparationParams ID="LPP4857" RunIndex="5 " Sides="TwoSidedFlipY">
        <MediaRef rRef="M4857" />

      </LayoutPreparationParams>
         ....

         ....

   </LayoutPreparationParams>

and

   <DigitalPrintingParams Class="Parameter" ID="DPP1" Status="Available" PartIDKeys="RunIndex" PageDelivery="ReverseOrderFaceUp">
      <DigitalPrintingParams Class="Parameter" ID="DPP4856" Status="Available" RunIndex="0~4 ">
        <MediaRef rRef="M4856" />
      </DigitalPrintingParams>
      <DigitalPrintingParams Class="Parameter" ID="DPP4857" Status="Available" RunIndex="5 ">
        <MediaRef rRef="M4857" />
      </DigitalPrintingParams>
       ...

       ...

   </DigitalPrintingParams>

I guess the pages of the document is being split by varied stock types.

What does this change? I checked the FFC SDK and couldn't find a JDF example that matched this. Most, if not all, seemed to only contain one media reference as you suggested.

So would it be safe to say that while the printer might be able to recognize it, this is a scenario we might not be able to manipulate in a FF Core workflow?

[JavierM-Xerox]

I am not sure how we would handle multiple media elements. I think it would depend on whether they are inline within LPP or DPP or not.

If there are multiple elements but they are referenced only once I think that would be ok.

We support either the ProduID or Media attributes but the descriptions below generally look ok.

I would suggest that you register for the FFC SDK: https://www.xerox-solutions.net/developers

You can get details on all the JDF that FFCore supports.