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
I would like to see a live progress bar, or status line (page 2 of 12) in the Job Server Queue dialog, so I could know if I should wait a minute, or walk away for 10 minutes.
Hitting Refresh is a less than ideal way to see the server's status of plotting a PDF.
Would a be okay to add text in the Job Server Queue dialog that states? ## in progress, ## pending, ## errors.
Also add an automatic refresh of the Job Server Queue so that you don't have to click the Refresh button.
A live progress bar for each job would require the Job Processors to constantly talk back to the server to update the progress. This could cause a lot more network traffic, slow down the performance of the Job Processor, and slow down the performance of the server.
Thanks for the reply. I don't think that would be much help. At least for our company workflow, you can pretty quickly see how many items are in the list.
How about a calculated ETA for each job, so while you're waiting for a PDF to finish, for instance, and you hit refresh, you could get an update that it should be done in 30 seconds or 10 minutes. Do I check my email or go get a coffee?
Or maybe more specific but perhaps easier - a status column (per job) that shows it's currently processing XYZ AutoCAD dwg layout # 7 of 10, or whatever the equivalent would be for other programs/files.
I understand that live updating this info for many workstations would be a problem, so I guess I could accept if these only updated when you hit refresh. I was thinking it could be programmed similar to a mobile push notification to whoever has the Job Server Queue window open and in focus. Maybe push an update automatically every 10 seconds or so. Most users would close the window when not waiting for something to finish.
These changes could help us to decipher why sometimes the server is getting bogged down, or simply see that you can wait 1 more minute to send the PDF to a customer.
I completely understand that the Vault Job Server's main purpose is not just to plot / create Pdfs - I'm sure seeing a status for other processes would be a benefit as well.
I missed the part where you suggested Auto Refresh. That would be cool.
Probably separate topic, but I would love to have that for the main Vault window as well. What if when the job server finishes a task, it pushes out a main window refresh for the user that requested the job?
There have been a few times I've walked away from my desk after sending a job to the job server (changed status on a job forcing a 'create pdf'), came back, forget to hit refresh and ultimately send an old revision to a customer. That's a problem.
Sending a refresh back to the Vault client wouldn't work. If you working in a different folder, it would refresh the current view and you could be in the middle of doing something else.
An ETA on job completion could be misleading or not accurate. There are a lot of factors that could contribute to the amount of time it could take for a job to complete.
Understood. Do you think its possible to display the status of a plot/print task like "Processing page 7 of 10" ?
Often, our 2nd layout sheet has a lot of very tiny xref details that bog the process down, but everything else will tend to process quickly. It would be nice to know when the job server has progressed past sheet # 2. Thank you.
I think this would be perfect - note, this details menu only shows data when you click on the task. Auto-refresh ONLY the Status field every 5-10 seconds. Once the job is done, the status box should state "Complete", or "Error...{insert reason here}". The job(s) won't be hidden/removed until the user hits refresh.
Okay, I'm sure I just don't understand since I don't know how to write program code, but it seems like if you limit it to only when a user is actively requesting the information by highlighting the specific job line, it would be less taxing than the user(s) hitting refresh multiple times, refreshing the entire list, waiting for their job to disappear. This is the only way we know something is complete.
@ihayesjr and I had a phone conversation discussing a few things. He has a few ideas on how to actually implement this, like notifications sent to the user who submitted the job, or a new column in the main window to show if something is being processsed or complete. Live updates are probably not likely, but automatic refreshes could be possible. One additional idea would be to add a system level checkbox to disable any automatic refreshes or status updates should this prove to degrade performance for larger companies with multiple job servers.
