Just a mass confusion of when and where and what JITL template fields accept ${params}, \${params}, or %params% syntax. There doesn't seem to be any consistency in usage.
Last edit: Grant Hopwood 2015-10-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree, it's not perfectly evident when to use what syntax. Instead of a consistent feature we face a number of historic approaches each with a limited scope.
Disregard.
Just a mass confusion of when and where and what JITL template fields accept ${params}, \${params}, or %params% syntax. There doesn't seem to be any consistency in usage.
Last edit: Grant Hopwood 2015-10-20
I will create an article in the JobScheduler Knowledge base until next week.
When I have created the article, I will post the link here.
Hi Grant,
I agree, it's not perfectly evident when to use what syntax. Instead of a consistent feature we face a number of historic approaches each with a limited scope.
In a first step we provide an inventory of substitution mechanisms with the
How to control substitution in Job Parameters article.
Please review this article and let us know if this covers your current needs.
In a next step we will re-work parameter substitution in a more consistent manner. Your proposals are welcome.
Best regards
Andreas