Enfocus Community

You are on the right track. The only thing you still have to do is to send the job to the output folder. In your case a single output connection will be enough, so in the properties of the script you define it as having just one output connection and the end of the jobArrived function you add: job.s...

It is a bit safer (because there is no encoding involving) and certainly more efficient to use than to do it in two steps by reading the file as a string and then convert that to a ByteArray.

Use the "Delete files" app that is part of the bundle "Folder apps". With this app you can easily keep all the jpg files you want and with the "Rename job" element you can flatten the folder hierarchy of the job folder.

I do not quite understand the original question. It suggests that the output of the review process is a report, but it is not: the output of the review process is the input file, possibly enriched with comments that have been added. And why would you preflight a file after it has been approved and n...

There are many things that could be wrong: is the endpoint correct, do not you have to add the authorization string to a special header, does not the content-type have to be application/json, ...? Without the documentation of the API it is impossible to help.

The principle is the following. Create a variable set and add a variable that reads the value from metadata, and add a variable that is rule based and that evaluates to true or false depending on the value of the first variable (if Taip then true, else if Ne then false). Create a preflight profile a...

It is not difficult to do with a script. Here is a code snippet that shows how to decode from base64 and save the result to a file: var xml = new Document( somePathToTheXMLfile); var base64String = xml.evalToString( "/xpath/to/the/InvoiceFile"); var decodedResult = new ByteArray( base64Str...

I take everything back. it is a coding mistake. On line 13 you log currentValue instead of newValue.

I found a workaround but it is weird: newValue = readGlobalData(s, testScope, testTag); job.log( -1, "New value 1: " + currentValue); job.log( -1, "New value 2: " + s.getGlobalData(testScope, testTag)); and you will see that the second log does give you the expected global data v...

I have never had any problems with global data. Are you using variables for the scope and key? If so, then my first idea would be that there is a discrepancy between the values at set time and get time. You store the result of an API request. Assuming that it is a REST API call and you store the ser...

You can use the Switch REST API to query active jobs with a certain flow stage in a certain flow. Look at the GraphQL section of: https://www.enfocus.com/manuals/DeveloperGuide/WebServices/19/index.html#api-Reporting-dashboardGraphQL . To query live jobs you do not need the Reporting Module. When th...

You do not explain what you do to get rid of the Nordic characters. The easiest method is to use the action "Reduce character set - Portable ASCII". That gets rid of everything that looks "weird" and you need just 1 rename, and not multiple as I can see in the screenshot of the f...

Indeed, Jan, the new 2019 submit point functionality allows to submit only metadata, but behind the scenes there is still a file. As Mostafa plans to integrate an external system into Switch using the REST API he will not be using Switch Client, but he will still have to create a file too. To expand...

Submitting a file to a submit point obviously requires a file. What you want to submit is not data, but metadata! You can easily do this by putting the URL in some XML structure and submit that XML file into the flow. The first thing you do in the flow is "XML pickup - Metadata is asset", ...