***Note from Migration:***
Original Title was: Restore TM_Prioriy parameter support when submitting server job via web interface
Imbedded TM_Prioriy workspace parameter prevent user from submitting server job via web interface.
Archived
Restore TM_Prioriy parameter support when submitting server job via web interfac
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+22- Safer
Could you provide additional clarification on this idea? Job priority (tm_priority) is not currently exposed as a form option in the Web UI's Run Workspace page. If you can elaborate on what you are looking to achieve with this idea and the current pain if there is any, then we can look at how to address that. Thank you
Yes, I know it not exposed.
In fme2015, if I manually create a tm_priority as published parameter, fme server web UI will accept this parameter.
And on fmeserver2016 web UI , it no longer support this parameter.
+22- Safer
Thanks for the feedback. I believe I understand this now. Here is a video showing the old and new behaviour to confirm:
http://www.screencast.com/t/70oN6mscNP
I've filed a problem report in our internal tracking system. I don't believe we were aware of this use case previously, which is why we didn't work to ensure backwards compatibility. Sorry for the problems. We would like to introduce a better solution in the future that doesn't require manual parameter publishing.
For my own usage, I would like to "rush" a job on FME Server and I can not use the /fmeserver/repositories#/runworkspace link. Instead of that, I have to code a workspace with a FMEServerJobsubmitter letting me set a lower priorty to have it in top of the queue.
+14- Safer
Please note that there are no current plans to resolve this idea in the short-term. The tm_priority parameter has been deprecated in favour of supporting Job Queues (which themselves support setting priority).
Previously, the priority of a job would have been designated at run time, through use of the tm_priority tag or parameter, but we have moved to a new model where priority is set on a subset of FME Server Engines – the "Job Queue" – and then a job is assigned to a Job Queue at run time.
Workspaces that specifically named the Job Priority parameter tm_priority should be updated to maintain compatibility with FME Server 2016 or Newer, or the transition to using Job Queues should be made if you are running FME Server 2018 or Newer. I'm sorry for any inconveniences you will experience for this transition. If you need additional assistance, please contact our Support Team.
For more information on Job Queues, please see documentation or the Safe Software blog.