Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Give the Vault administrator the ability to set fixed priority values for specific job types. For example, DWF generate jobs could be set to always have a priority of 100, regardless of how they got added to the job queue.
@ihayesjr , Absolutely yes. (I don't mean just a visual sort button, I mean change priority so another job can be moved in front of the others.)
Just to state it a different way; I have 10 jobs in queue and the last job in line is my ".idw export to dwg" job. The other jobs are just "stp file export" jobs.... So the idea is to allow us to right click the "idw export to dwg" job and select either Promote or Demote or Promote to next.
This could also be accomplished with buttons on the toolbar above too. I was just making it simple.
Priorities of submitted jobs are specified when submitting them to the Job Queue. Priorities are hard coded. Which jobs are enabled on which job processors highly depend on the expected load on a particular job worker. The order of handling submitted jobs on the other hand can only be controlled by: The date the job has been submitted. The priority the submitted job was given while coding.
Proposal:
Being able to prioritize the order jobs accepted by a particular Job Processor helps to cope with higher demand for specific jobs. The Job Worker can specify: The jobs being accepted by that job processor. The priorities which jobs should be taken from the queue first. How to treat jobs that are not prioritized to prevent starvation in case no other job processor handles them.
Thank you for your feedback. Based on what jobs you know exist today, what priority order would you place on the jobs? Keep in mind that a job has multiple steps. For example, creating a DWF file also requires that synchronizing properties is done.
For us, the biggest impact is getting custom jobs to run in a specified sequence. For example: 1. Custom job 1 2. Synchronize properties 3. Create PDF/DWF 4. Custom job 2 Our client requires we use a specific records repository, with PDF files being the preferred media. To avoid having to have our staff work in two separate applications we have an integration process that picks up new releases nightly. Custom job 1 “stages” the released files by populating and emptying specific UDPs that the nightly process uses to identify the files to pick up. If the custom job runs after the synchronization and PDF creation, then the generated PDFs never get picked up because the applicable UDPs are not set properly. Yes, we can probably work around this by using additional state transitions, but this is not a desirable method as it results in additional work and slows down the process, plus you need to enforce a delay between the last two transitions to give the job processor time to run.
Last days we have lots of contruction data state changed to released. DWF-Creation from vault has (by default?) priority 1. Always when one of the (quick) release job where done the next one has to wait for the dwf create job to be completed. As a resut the user had to wait many minutes till all dwfs are created before he can continue work on item / ERP side of his data. These dwfs are not necessary at this time and it would be fine if they are only made when our job server has nothing other to do...
It would be nice if you could change these default values and change the priority also while the jobs in the queue. (Of course an admin has to know what he do that there is no "wrong" order then)...
Any changes on this? This is something I need desperately as an ETO manufacturer. i have hundreds of Jobs daily and some I need to get out within the hour, some are lower priority. But if a urgent job comes in need to be able to prioritize it higher.
We have questions from the team regarding the ability to change the job's order in the queue to the highest priority order. We are exploring this idea and are currently under discussion on the NDA-based Vault Feedback/Beta forums.
Please help us by answering the question and validate the concept by using this link:
