appstro
Well-known member
Hey everybody!
I am having a hell of a time trying to figure out how to consistently pick up jobs. The RAMpage current method is to "export" the previous job if its still on the client and then "import" it as a new named job. BUT then you have to go to the "FPO profile" for the new job and make sure that its pointing to the new jobs FPO folder. If the job has already been archived then you must copy the old job into an Import folder we have set up and import from there... Pain in the Arse...
On an exact reprints if you use the "pick up job" option it actually renames the old job. This is not so great for us as we like to keep the previous job untouched as redundant as that might seem.
RAMpage has a really complicated set up for what should to be a simple procedure. HOW is the real world handling pick ups with changes and exact reprints??
In the Scitex environment it was easy to do pick ups and easy to do pick ups with changes. This RAMpage stuff is confusing and a pain. Any suggestions? Help!
Mike
I am having a hell of a time trying to figure out how to consistently pick up jobs. The RAMpage current method is to "export" the previous job if its still on the client and then "import" it as a new named job. BUT then you have to go to the "FPO profile" for the new job and make sure that its pointing to the new jobs FPO folder. If the job has already been archived then you must copy the old job into an Import folder we have set up and import from there... Pain in the Arse...
On an exact reprints if you use the "pick up job" option it actually renames the old job. This is not so great for us as we like to keep the previous job untouched as redundant as that might seem.
RAMpage has a really complicated set up for what should to be a simple procedure. HOW is the real world handling pick ups with changes and exact reprints??
In the Scitex environment it was easy to do pick ups and easy to do pick ups with changes. This RAMpage stuff is confusing and a pain. Any suggestions? Help!
Mike