Enfocus Community

"Connection priority"

Are you sure you set the folder constraints on the outgoing connections? Put the connections after Local and Remote on hold and place 5 input jobs in the input folder. The folders should each get 1 job and there should be 3 jobs waiting before "Hold job". Release one of the two connection and see wh...

There is no need to set a target folder and the second Hold job element is not necessary. This is the principle:

When a checkpoint does not define metadata you do not have to specify the metadata field. In that sense it is optional. But when the checkpoint specifies metadata you have to fill it in. I could easily reproduce this using the Web Services documentation: it worked, then I added a field of metadata a...

That is not much to go by. Did you use :id in the call or the actual job ID as returned by the List jobs call?

The commented lines have to go back in. The problem is the fact that you have not taken into account nodes that use the default namespace. Remember these two principles when using XPaths: when an XML uses namespaces the XPaths must use namespaces for ALL nodes the default namespace in an XPath IS NO...

It depends how you transfer the jobs to the other Switch and what it is that is not running. If you drop the job in a local folder that is a remote folder for the other Switch, the job will be stuck in that folder. As it is stuck "Hold job" will route all the other jobs to the other local instance. ...

There is a plethora of npm packages for processing XML files using NodeJS. I see no problem whatsoever. There are two possible approaches. Either you read the XML into a JS object with a package like xmltojson, or you use a package that processes the XML natively. I find the first approach useful fo...

When you add 2 outgoing connections to "Hold job" Switch will send 1 job here, 1 job there, 1 job here, etc. In this way the number of jobs will be equally split over the outgoing connections. That is not always the best choice because not all jobs take equally long. To make it a bit more intelligen...

In that case look at the OUTGOING connection of "Hold job". It has the same properties as the flow.

There are properties on the flow itself that allow to define when the flow can run.

Machine 1: is this a simple input folder or a hierarchy? Switch removes folders from a hierarchy when a folder is considered to be a job (this is related to the level settings), but Switch will never remove a simple input folder. If that happens then it means some other process is responsible for th...

I see 2 possibilities. You define a rule on the mail client to save incoming messages as .eml files, but this will require that you have the mail client open on the Switch server at all times. Alternatively you may have to script something in the mail client. Or you take what you get from Switch and...

Yet another method: if you have the Reporting Module then the processed jobs stay in the database for the number of days specified in the Preferences. You can use a GraphQL query to check how many jobs were processed by all flows during a certain period. Here is a query you can use in the Switch Web...

There is not much to go by and although the fact that it works for PDF files and not for ZIP files pleads against it, but the first thing that jumps to mind is this: viewtopic.php?f=26&t=3959