Just to add to my initial thoughts on this. I hadn't done the training yet for Pressero, so once we got to that I realize we can set the production queue for the product in Pressero for when it comes to Tflow. So this hasn't been as much of an issue as I had originally thought it would be. But in theory if we ever create jobs manually in tflow it would be a bit easier :)
HI there, I just purchased Tflow and Pressero and I had actually assumed this was already implemented. I'm just going through the training process now and this was one of my first questions. If we sell a product online (lets say a feather flag) we want that product everytime its sold to send the print file right to our specific printer / media for that flag. As it stands right now someone would have to MANUALLY set that everytime in a job or order? Doesn't that defeat the whole point of pressero / tflow if we can't automate a product from start to finish?
Hi Trent, No, what I am looking for is a way to set a specific tflow template to always default to a specific printer que. So when the order is created for say a 24x36 foam board, and the operator chooses the 24x36 board template, that, by default, goes to the print que on the board printer. They maybe could have the option to change the path if needed, but they would never have to input the path to the que as long as it goes to the board printer.
Right now my operators have to choose the template to use for a specific product and also choose the print que. 99% of my tflow templates only are set for one printer(and that que) So I would like a default que input area in the templates we make. Right now you cannot specify a que for that specific template.
Thanks Scott, would you want this to be like a stop point,,, as in the file comes in, gets checked,,, then someone would be alerted that they need to "set the que" manually? I can see it being a specific stats or another que where everything goes then an operator then manually sets it.
Allowing the assignment of a production que in the product would be very helpful to stopping errors in sending. We have a a group of processors working on files and sometimes the ques for products are set wrong and go to the wrong area. Templates are generally set to a certain product and the que would never change.
Just to add to my initial thoughts on this. I hadn't done the training yet for Pressero, so once we got to that I realize we can set the production queue for the product in Pressero for when it comes to Tflow. So this hasn't been as much of an issue as I had originally thought it would be. But in theory if we ever create jobs manually in tflow it would be a bit easier :)
HI there, I just purchased Tflow and Pressero and I had actually assumed this was already implemented. I'm just going through the training process now and this was one of my first questions. If we sell a product online (lets say a feather flag) we want that product everytime its sold to send the print file right to our specific printer / media for that flag.
As it stands right now someone would have to MANUALLY set that everytime in a job or order? Doesn't that defeat the whole point of pressero / tflow if we can't automate a product from start to finish?
Thanks for this. We'll take a look.
Hi Trent, No, what I am looking for is a way to set a specific tflow template to always default to a specific printer que. So when the order is created for say a 24x36 foam board, and the operator chooses the 24x36 board template, that, by default, goes to the print que on the board printer. They maybe could have the option to change the path if needed, but they would never have to input the path to the que as long as it goes to the board printer.
Right now my operators have to choose the template to use for a specific product and also choose the print que. 99% of my tflow templates only are set for one printer(and that que) So I would like a default que input area in the templates we make. Right now you cannot specify a que for that specific template.
Not sure if I explained that well?
Thanks Scott, would you want this to be like a stop point,,, as in the file comes in, gets checked,,, then someone would be alerted that they need to "set the que" manually? I can see it being a specific stats or another que where everything goes then an operator then manually sets it.
Allowing the assignment of a production que in the product would be very helpful to stopping errors in sending. We have a a group of processors working on files and sometimes the ques for products are set wrong and go to the wrong area. Templates are generally set to a certain product and the que would never change.