Symptom:
A user imports a new definition with modified default values or changes the default values of a parameter on a job definition. Upon saving they are prompted about what to do with existing schedules of this definition. The user selects use new definition, but upon checking the recurrence finds the values aren't changed.
Issue:
If the parameters used are not evaluated at runtime, then modifying the default values of the parameters on the definition will have no impact.
If you would always like the default values of a job definition to be used in a recurrence, set the parameter to be a runtime parameter.
The values of job chain calls are always evaluated at runtime and the default values will be used unless other values were provided in the job chain call itself while editing the job chain definition.
Comments
0 comments
Please sign in to leave a comment.