I have been having some issues with files not deleting after 24 hours. the Xerox development team is working to solve this issue but during this process I have found out some information on the actual process. I have learned that 1) if files are held at the printer then they will not delete even though they have successfully been processed through the workflow and 2) if you forward a job from the original printer to another printer this may also cause some issues with files being automatically deleted.
Basically files are automatically deleted dependent on their status at the printer. For us this is a problem. I would prefer that the determination of files being deleted after 24 hours be based on whether or not they have successfully been processed through the workflow rather than their status of completion at the printer. This is the way the old process manager application worked. I would think that his would be easier for the Freeflow teams development as well as reducing the communication traffic between Freeflow Core and the printers.
I have had a SPAR created to have this changed but was interested in other peoples opinion on this. For us there is absolutely no benefit to have files remaining in the queues because they are still at the printer. I do understand that the reason for this is to have a complete end to end solution but for us, because we are putting so many files through Freeflow Core, it is just too taxing on our resources and we have to manually go in to Freeflow Core and delete files.
Solved! Go to Solution.
For FFCore 188.8.131.52, an option has been added to set the job deletion policy based on DFE vs. FFCore workflow completion. The switch is at C:\Program Files\Xerox\FreeFlow Core\MantisService.exe and is labeled " <add key="purgeCompletedJobsIfDFEJobCompleted" value="true" />". The valid values are "true" (for DFE job completion) and "false" (for FFCore WF job completion.
Keep getting "access denied" when I try to change it. Any other instructions that will help me make this change from "true" to "false"
I am able to update and save the file using Notepad. Do you have administrator rights? I cannot think of any other reason for the behavior you are seeing.
Yes, we have a similar problem. The difference for us is that we're not "printing" to a Printer. We're saving files to a save node.
If you open the Notepad application via "Run as Administrator", you should be able to edit the file sucessfully.