Enfocus Community

Support for XSLT2.0 is an existing feature request, but can you please describe what you are trying to achieve that requires the use of XSLT2.0? I will add your comments to the feature request to give it some more "meat".



Freddy

OK, thanks, that explains why you inject the XML as a job. Next question: why is it important that the XML passes before the PDF? You write that the PDF goes into production and the XML into the archive. The chronology of these events would only be important when production picks up information from...

Sorry for my late reply, but I had a whole bunch of holidays I had to take. Question: you are picking up the XML as a dataset and you are submitting both the XML and the referenced PDF as a job, why? When you submit the PDF job with the XML as a dataset you can always get hold of the XML file with t...

Can you share the use case/story why you need to know those names? I will gladly add to it to the feature request list.

I have been able to get them to work. What exactly is your problem?

To update the metadata of files you can use the "Inject XMP" element. This element can not only inject XMP, but also update it, and that is what you want to do. I have put a flow on the Crossroads site that illustrates how to do this. Search for XMP. It may still take a day or two before i...

Hmm... Somehow this does not work, the files continue through Assemble Job to another application without waiting for all the files to be present there first. As clarification, both the script I run via Generic Application and Photoshop which comes later in the flow, need GUI so my script gets mixed...

It is not obligatory to know the number of files in an ungrouped job. The "Assemble job" element has a property "Scheme" where you can choose "Ungrouped job". The "Assemble job" will wait until all the ungrouped files are there before recombining them into an ...

Peter is right about the job variable inside the function. However, there is a flaw in the whole setup: inside the body text you can access variables, but not script expressions. You can also use a script expression for the body text, but then you can only return 1 string. Put the string you want to...

I am sorry, but I fail to see what is wrong with Dwight's suggestion to use "Assemble job". Looking at the script it does not do anything else than what the "Every N jobs" property of the "Assemble job" element will do.

If the script is complete I do not see anything that cannot be done with "Set hierarchy path" and "Archive hierarchy". In "Set hierarchy path" you set the first segment to [Job.NameProper] and in "Archive hierarchy" you set the root F:/Switch/in and that will ...

@Thorsten: you have not specified how you update the dataset, but I am assuming you are using a script. Here is a suggestion: do not update the dataset of each dismantled job straight away, but store the information in global data. After having assembled the jobs you update the dataset with what you...

Although I fully agree with the fact that a separator-based string extract is a great enhancement, there is something you can do with the string of the file name in your example. The 88888 is easily extracted with [[Job.NameProper:Before=_]. The same goes for the 16:[Job.NameProper:After=_]. The 1 o...

No matter how many elements there are in your hierarchy path only so many will be used as are listed in Subfolder levels in Archive Hierarchy: /abc/def/ghi/jkl/123.pdf will end up as /abc/def/123.pdf when Subfolder levels is 2. I am not certain I fully understood what you are trying to achieve. If t...

Pack/Unpack is a possibility but not necessary when you stay within the same environment. When you set the output folder to a specific path and you set Strip unique ID to No, then another flow can pick up the file from the location where it was saved and it will retain the metadata.



Freddy