Yes, it would be very handy. We have about 100 jobs that execute, adding a Set Env Task to each job is fine because I can clone them so easily. Instead of a new type of task, another potential option would be to merge environment variables into the execute task's process before executing the command.
So here is a follow-up question related to the same topic. If I have two sequential execute tasks in a job, do they get launched in the same environment or does each execute task get a new environment?
What I am wondering is this...if I execute a .bat file to change the environment as the first task in a job, will subsequent tasks see the modified environment variables or will subsequent execute tasks run with the default environment variables?