How to Update the Path to the Product Data Zone in Esko

How to update the path to the product Data Zone in Esko.

LP Geerinck – 04-02-2014

Cases :

Example 1: One or more of your customers have merged into 1 company. So suddenly all existing products need to be linked to that 1 customer. This impactsthe Product Data Zone components since thecustomer of a Product has changed, and Customer ID can bepart of the Product Data Zone.

Example 2: You wish to make changes in the definition of the PDZ (product data zone)and JDZ (job data zone) to get rid of the Customer ID and customer keyword that is in it.

E.g. for the PDZ you wish to go from\\pre-press server\productimages\<#kla__rpn>-<#kla__ref>\<#afg__ref> to a structure like \\pre-press server\productimages\<#afg__ref index=1 count=3>\<#afg__ref>.

And for the JDZ you wish to go from \\pre-press server\jobs\<#kla__ref>-<#kla__rpn>\<#ord__ref>to \\pre-press server\jobs\<#ord__ref index=1 count=3>\<#ord__ref>

Example 3: You have a new prepress server and therefore need to change the definition of the PDZ (product data zone)and JDZ (job data zone)and move all products to the new server

Changing the PDZ and PJZ parameters in Cerm ORassigning an other customer in group toproducts can be easily done in Cerm. However, the AE value for Product Data Zone is not automatically updated, so AE will not find the product files anymore.

Screenshot case:

Old situation, before the PDZ and PJZ parameters are changed or the customer of the product changes:

Product 400177 is linked to prepress job 024905 and customer 100931 (Soaprah Ltd).

This structure is based on this product data zone definition, which needs to be identical to the one in Cerm.

Job 024905 is linked to customer 100931:

This is based don this job data zone definition, which has to be identical to the one defined in Cerm.

Solution:

Execute the following procedure first on 1 product together with the Esko consultant to be able to follow the different steps and make sure everything works fine! Only after successful test, you can execute the procedure on a larger amount of data.

Step 1 : remove all prepress jobs of Esko

First of all, you need to remove the existing prepress jobs for all appropriate products via an additional product status which is linked to a Custom JMF with the AE task ‘Remove Job’ to this product status to be able to launch the task automatically from the moment this status is set. The removal of the prepress job is necessary to make sure that the JDZ will be rebuilt when sending a new prepress job.

Beware, this should be an extra product status e.g. ‘Administration’. Do not play with the existing Artwork prepress-statuses. These should remain the same !

Ticket linked to the status change :

Status change to launch the ticket:

Step 2: return prepress jobs to WIP again

If you have the habit to take prepress jobs out of WIP after approval of the softproof, you need to return them to WIP again (only for the products you’re about to change) in order to be able to apply the changes you will make in the next step because it won’t work on jobs which are taken out of WIP.
Open the ‘Take jobs out of WIP’ module, look-up the appropriate jobs (you can use the criterion Kind of job = ‘Prepress job’)
Multi-select the jobs and choose from the menu Data / Retunr jobs to WIP
This action will NOT send a JDF

Step 3 : Change the PDZ and JDZ parameters OR the customer and contact ID in the products.

Only after all prepress jobs of the appropriate products have been taken into WIP again in Cerm and have been removed in AE, the necessary changes can be made:

Example 1: Update the Customer ID and the related contactof the product(s) in Cerm (e.g. 100931 will become 100934).

or
Remark: if you choose to chang the CustomerID and contact in group, do NOT change the product status in this grouped change wizard!

Upon modification of the product(s), the customer and contact are automatically updated in the related prepress job(s)in Cerm as well and as a result a JDF is automaically sent to Esko. However, since the prepress jobs have been previously deleted in Esko, a new prepress job (with the same ID) is automatically created there with the correct customer data andpath!

Example 2: The parameters of the PDZ and PJZ are changed in Cerm and in Esko to match the desired structure.
Close and restart the Jobs and Products module in Cerm (to make sure the changed properties are taken into account). Then, multi-select the appropriate products in the Products module and send a new JDF to Esko.

Since the prepress jobs have been previously deleted in Esko, a new prepress job (with the same ID) is automatically created there with the correct JDZ path!

Step 4 : Change the Product Data Zone in Esko

A workflow ticket needs to be created in AE : J-Relocate-Product

The ‘Select Product file’ needs to find the correct product PDF file, based on parameters of a new JOB jdf, without any product context. So we will use the Prepress Job SmartName ‘Project ID’ as a Product ID (that is unavailable here). This is based on the fact that Cerm will only create prepress jobs for 1 product and will always fill out the product ID in the value of the JDF “Project ID” of the prepress JOB.

The path of the Product needs to follow the Construction in the Product Data Zone Definition

The ‘Add to Products’ will fill out all product parameters.

Create a custom JMF in Cerm that calls the AE task J-Relocate-Product

<JDF JobID="<#JobID>" JobPartID="RelocateID__<#JobID>" DescriptiveName="BackStageTask" ID="n0001" Status="Waiting" Type="eg:BackStageTask" Version="1.2" xmlns=" xmlns:eg="

</RunList>

<eg:BackStageTaskParams Class="Parameter" ID="TaskParamLink" Status="Available" eg:JobAsInput="true" eg:TicketName="/swft/J-Relocate-Product" >

<eg:swftParam />

</eg:BackStageTaskParams>

</ResourcePool>

<eg:BackStageTaskParamsLink Usage="Input" rRef="TaskParamLink"/>

</ResourceLinkPool>

</JDF>]]>

Create an additional temporary product status in Cerm to launch this AE task

Create a new additional product status in Cerm which will allow to mark the products that need to be relocated. Then, you need to link the Custom JMF with the AE task ‘Relocate Product’ to this product status to be able to launch the task automatically from the moment this status is set.

Launch the Relocate ticket:

Change the product statuses of all appropriate products in group to this ‘to be relocated’ status.

In Esko the files of the product(s) are automatically relocated
Change the product status back to ‘-‘ again