Page 1 of 1

Adding and enforcing custom fields

PostPosted: 28 Aug 2017, 15:45
by ch3m1kal
Hi,

I was just wonder if it's possible to add custom fields when submitting jobs and ideally making some of them mandatory.
For example, adding a field for due date of a specific render, or even making the "Project" field mandatory. Also why do some things only exist while editing net jobs, but not in the submitter?

Thanks!

Re: Adding and enforcing custom fields

PostPosted: 28 Aug 2017, 16:01
by Shoran Support
That's not possible, no. Some fields have simply not been added to the submitter yet.

Re: Adding and enforcing custom fields

PostPosted: 28 Aug 2017, 16:18
by ch3m1kal
That's sad to hear.
I don't suppose it's planned for a near-ish release?

Meanwhile there's no way to maybe feed custom metadata at least, maybe via a python pre-execution event?

Re: Adding and enforcing custom fields

PostPosted: 28 Aug 2017, 16:37
by Shoran Support
You can always pass arbitrary additional command-line switches to the underlying console RC when using the submitter. Take a look at the nj_project and nj_setfield switches (RenderPal V2 manual chapter 27.2).

Re: Adding and enforcing custom fields

PostPosted: 29 Aug 2017, 09:17
by ch3m1kal
Hmm looks like it may be possible with a combination of nj_setfield, nj_tags and nj_project, but that would require us to basically write our own submitter.

Thanks for the tip!

Re: Adding and enforcing custom fields

PostPosted: 29 Aug 2017, 12:31
by Shoran Support
Another way to go might be to not use custom fields but to add new parameters to the renderer(s) you use; these can be made mandatory.