Enfocus Community

Awesome, let me know what they come back with. We're fully using Phoenix via the API with some calls to it from Switch. The past few updates have had no issues for us so good to know about this one before upgrading.

We've not upgraded to 25.11 yet but I was planning to do it soon, I guess I'll hold off of this for now

Have you raised this issue on Esko Support?

Have you got an example of the HTTP Request configuration you have in Switch and the Postman request you're making?

Regarding which would be the right choice of Preflight Profile and what the settings do it's probably worth going through the Learn section for PitStop to understand how Preflight Profiles and Action Lists work and what they do: https://www.enfocus.com/en/learn/pitstop And again for Variable Sets th...

I've just had a debug through the PdfProperties script with a blank PDF I made matching the values of the screenshot and I get the same result as you with the artBox and cropBox values being the same. I don't think this is something you or the script is doing wrong. When I was debugging it looks lik...

Looking at the Switch Reference Guide regarding Defining metadata fields in Submit Points it states: Using variables: It is possible to use variables to define the default value for your metadata field (Single-line text with variables, Condition with variables). However, most variables (e.g. doc aut...

I'd open the Progress pane in the Switch Designer, find the script that is stuck executing in the Progress pane, copy the Process ID and kill it in Resource Monitor (If you're on Windows, unsure on the Mac alternative) which will then let the flow stop https://i.gyazo.com/caa941229ba8a8f1353e5c7c8d7...

Matthew's solution is of course perfect and for the flow design easier than what I will suggest, but here is an approach that does not use scripting for those users that do not have the scripting module. Define two pieces of private data on a folder after having run PitStop using the following XPat...

Awesome, glad it works as you wanted

No worries, updating it to look at multiple nodes ends up getting a little bit janky due to the Node.js scripting engine. The scripting engine only supports Xpath expressions evaluating to boolean | number | string | undefined, so I don't think its possibly currently to get all the node values in on...

Ended up taking me awhile to figure this one out, but reading the XML data set from a script expression looks like this: async function calculateScriptExpression(s: Switch, flowElement: FlowElement, job: Job): Promise<string> { const datasetPath = await job.getDataset("TestDataset", Access...

After debugging your script I think I was able to find your issue. The jdf variable you'd defined that queried the parsed xmlData was returning undefined As you can see from the screenshot below when debugging the value of the xmlData variable the properties within it don't contain any "dn:&quo...

Have you got an example JDF/XML you could provide? That would make it easier to debug what's happening in your script

The first thing that jumps out to me is the export declaration you've added to the jobArrived method, edit: also I noticed that you removed the s: Switch argument from the method too: export async function jobArrived(flowElement: FlowElement, job: Job) { ... } Remove the export declaration and add ...

The first thing that jumps out to me is the export declaration you've added to the jobArrived method, edit: also I noticed that you removed the s: Switch argument from the method too: export async function jobArrived(flowElement: FlowElement, job: Job) { ... } Remove the export declaration and add t...