Until recently when manually running a job in Orchestrator via a trigger (Queue based in my case) would have tab by the Execution Target for Arguments. When you click on Arguments you would see all the arguments for that job along with the default values used when the Trigger ran. If you wished to change them you could and those new values would be used for that execution but not saved in the Trigger. That all made sense.
Today I just tried this and the Runtime arguments is on the right and you must select the Entry point (I only have one and it’s not defaulted to that) in order to see the arguments. Now I must enter each argument manually (not defaulted to the values in the Trigger). I almost always want to adjust just one argument but now I must enter them all from scratch otherwise it will use the values in the package itself. This is quite a change and not good if you have many arguments. It’s also not intuitive to have to select the Entry point where previously it was set to the default (usually Main.xaml).
Not happy with this change…
Me too!
A workaround is searching for the last job of the process you want to run, and then restarting it. This will still bring up the last arguments used.
Same here. Often we need to re-run a job manually, and we start it via trigger, which usually always gets the arguments set on the trigger. Now we need to set all the arguments 