We have a beautiful job with 20 job variables. These variables are assigned values in the job = 20 tasks. These values are only relevant at run time, but because of risk of spill over from one job run to another (eg. because of unanticipated errors), we start the job with a clearance by nullifying all variables = 20 extra tasks.

It would be nice if it could be indicated (eg. in the job variable details) that the value should be nonpersistent = cleared when the job completes. A default value could be added as well then.

This could be implemented in many ways. It could look like this (default value should be greyed out if Persistence is checked: