Page 1 of 1
Inject job from Auto-manage folder
Posted: Wed Jun 15, 2016 10:51 pm
by lombert
As the subject says, can I use Inject Job to get a file from an auto-managed folder?
I tried but I got an error that says it not finds the file. I wondering if I need the suffix also to grab the file?
Re: Inject job from Auto-manage folder
Posted: Wed Jun 15, 2016 11:07 pm
by loicaigon
A bit weird to me but you can right click on auto managed folder and copy path so you can use it as a base path for your inject element.
However I would use nothing but specific folder for file injection

Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 9:12 am
by sander
Why?
Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 9:31 am
by lombert
sander wrote:Why?
Me?
I have a sort of Hold folder, and the file can came again, then I will have the file in the hold folder to be deleted, so it not will be released and continued in the flow..

Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 10:45 am
by sander
Why not replace the hold with a inject, with a hold before it. Place the documents in a static folder, so if the job gets released it always picks the correct one.
Depends on what is in your hold at the moment tho.
Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 10:56 am
by lombert
The "Hold jobs and deliver later" is a script. And it looks at the that folder and release jobs at different time.
But sometime we need to pass around the "hold" and work with the file, and then I want it to be deleted.
I think if I could use Database instead. If any job gets in the "get around the hold folder"-way, it set that job in the database and then it release the job from hold it checks if it is in the list and then put that job aside and delete it..

Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 12:58 pm
by loicaigon
If you have scripting module, you could think of a script that would store any files passed through and and see if any previous file has already been processed and might actually be in the automanaged folder. Eventually it would remove the file if needed.
FWIW
Loic
[EDIT all your posts appeared while I was posting so many data out of date

]
Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 1:52 pm
by lombert
After some more testing I found the answer to my question, it is possible to inject from Auto-managed folder. It is necessary to have the Switch prefix of the file you want to inject.
This is from the log;
/Users/macproauto/Library/Application Support/Enfocus/Switch Server/backing/JDF New/automanaged/Hold Jobs/TEST FILE.txt
And this is from the "copy path"
/Users/macproauto/Library/Application Support/Enfocus/Switch Server/backing/JDF New/automanaged/Hold Jobs/_02ABH_TEST FILE.txt
Then I put the prefix "_02ABH_" in the injection job name, it find the right file and deleted it.
So now I just need to find a good way to save the prefix so I can use it if I need to delete a file.
Thanks for all suggestions and comments!
Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 2:39 pm
by Terkelsen
Yes, it's really annoying that you can't inject a job based on it's JobName Proper rather than the job name including the unique prefix.
If there is any way you could place the files to be injected in a folder with no outgoing connection, you will be able to strip the unique name and that way it will work.
Re: Inject job from Auto-manage folder
Posted: Thu Jun 16, 2016 4:20 pm
by loicaigon
Yes but considering two files with same name,
say : dummy.pdf
Eventually you get XXXXX_dummy.pdf and YYYYY_dummy.pdf. If you want to deal with dummy.pdf which job has to be considered ? The former, the latter, both ?
Just asking.
Re: Inject job from Auto-manage folder
Posted: Fri Jun 17, 2016 11:58 am
by lombert
I'll give you all an update on the solved flow.
If you have the unique prefix you can inject from a auto managed folder. My solution is this;
A added a small Database there it stores the unique prefix and two other fields there one is a unique number for every job. If not the job-number is in the DB it inserts all fields. If the job-number exist, it updates the DB with the new prefix.
Then the extra file cames, it picks up the old prefix and the other fields and injects the job and delete it from the 'Hold Jobs'-folder. And delete the record in the DB.
And the same if the script is releasing the job, then the record will be deleted in the DB.
Maybe not the most beautiful solution, but it works..
