Showing results for 
Search instead for 
Do you mean 
Reply
New Member
Posts: 3
Registered: ‎05-29-2015
Accepted Solution

Routing by Distinctive Hot Folders

[ Edited ]

With our daily production, we save the completed PDFs from Core to a folder on our printers.  Sometimes a printer can be down, so I ended up having to make a copy of the workflows with the only difference being the save location to bypass this issue (at first I just kept editing the main workflows, but I don't like messing with them all the time).  This works, but isn’t ideal since I have to remember to make any changes to both versions of a workflow, not just the main one.

 

To simply this, I was looking to see if there is a way to route the jobs in a workflow based on the specific hot folder to which they are submitted.  That way any submitted to the backup hot folder can use the same main workflow, but be saved to the other printer instead. I looked through our version of Core (4.0.2.2), and there doesn’t seem to be a way to route by distinctive hot folders.  I was curious if this is a feature in the newest version?   If not, maybe it is something that can be implemented? 

 

 

-RM

New Member
Posts: 2
Registered: ‎09-12-2016

Re: Routing by Distinctive Hot Folders

Hi

 

I don't have a direct answer to your question but this is what we do as a solution to your essential problem...

 

We use stand alone Xerox Ouput Manager rather than the one built into Core. It's setup so Core outputs to a folder and uses a LPR script to send to the Output Manager where operators can then choose which machine to send the file to.

 

New Member
Posts: 2
Registered: ‎09-12-2016

Re: Routing by Distinctive Hot Folders

Looking through the Route options in version 5 there is an option to Route by Workflow-> Submitter Name

 

If the source is a Hot Folder the submitter name is the Hot Folder name according to Core Help.

 

I haven't tested this.

Highlighted
New Member
Posts: 3
Registered: ‎05-29-2015

Re: Routing by Distinctive Hot Folders

"Submitter Name" is exactly what I needed; it worked perfectly!  I'll admit that I glossed right over that part of the help section. Good catch!

 

Thanks!

-RM