Finding Jobnames after combining on template

[StefanT-Xerox]

Great. Then I expect that the new job name will also be sent to the printer.

[DavidU54339-XRX]

I found using "$FFxpf$" "$FFjoinedJobNames.join(_)$" works correctly for a new PDF name from the Save node.

[StefanT-Xerox]

Assuming you have a manifest with both pdf and xpif containing job name, something like:

file;xpf;id
C:\max\doc1.pdf;C:\max\doc1.pdf.xpf;1
C:\max\job2.pdf;C:\max\job2.pdf.xpf;1

In an External process in the workflow after files are joined you could run a script like this:

$xmldata = [xml](get-content -path $args[0])
$name =$xmldata."xpif"."xpif-operation-attributes"."job-name"."#text"
(get-content -path $args[0]) -replace $name, $args[1] | set-content -path $args[0]

where $args[0] and $args[1] correspond to the parameters:

"$FFxpf$" "$FFjoinedJobNames.join(_)$"

The script will get the job name from the xpif and replace it with the joined string for the jobs with an underscore between.

I haven't tested to print this but I can see that the temporary xpf created has the job name for both files:

    <job-name syntax="name" xml:space="preserve">doc1_job2</job-name>

Of course this could end up in very long job names.

I have attached a sample workflow and sample files. You need version 5.4 to be able to import the ffc file.

Stefan

[DavidU54339-XRX]

Another option is to use a Save node that drops contents into a hotfolder. The Save node could use the following for the file name $FFjoinedJobNames.range(0,2).join(,)$ -- this will create a PDF name based on the first two jobs names separated by a comma. See screensnaps below. The "2" specifies the number of job names to be used. If there a 3 job names, use "3". Unfortunately, you need to know the number of jobs that are to be joined to ensure they  are all in the resultant name. "-1" does not work to specify all the job names for an undetermined number of jobs.

Note: The compound saved job name does not work unless there is a preceding Watermark node using the same variable content of $FFjoinedJobNames.range(0,2).join(,)$. I have written a BUG against this.

[StefanT-Xerox]

Do you need to have all the files that were joined in the job name? That could of course result in a very long job name. In theory the job name could be changed in the job ticket sent to the printer but that would require some scripting.

Other possible options for knowing what jobs were printed on a template could be to:

1. Watermark each job with $FFFile Name$ somewhere outside the TrimBox for each page before later in the workflow combining the jobs in an imposition template.

2. Insert a blank page to the job and print that as a banner page where you use a Watermark to fill the banner page with the jobs that were joined, using for instance:

$FFjoinedJobNames.join(,)$

The above would print each job separated with a comma as Job 1, Job 2,...

$FFjoinedJobNames.join(\r\n)$

The above would print the jobs as a list

Job 1
Job 2
...

Stefan

[T_Winkler]

We use the MAX workflow with version 5.4 of Freeflow. After combining two or more jobs on a template a group is generating. The jobname of that template has the name of one of the files. We need to now, what other jobs were combined on that template. 

The variable $FFjoinedJobNames$ seems to be the right one, but how could we set it into the workflow for generating the jobname for the printjob?