ModifyProperties is to modify the properties on the object, not in the object. so you will need modify to change it in the job and modify to change them in the blpacakge.
we wanted to make sure that important packages and jobs are not accidentally modified by deployers as it has happened before - giving Modify for the package and the job is out of the question for us.
Which also means that every time the same job needs to be deployed with a different set of parameters (local properties) a Bladmin needs to make the change in the package - this won't work either.
1 of 1 people found this helpful
Put in an RFE for this because I agree this is a good idea.
Another option might be to use ‘execution tasks’ if you are on 8.0.
Regarding Execution Tasks: yes this would be a great way to delegate execution of the job but there's no way to set parameters there.
Our problem is setting these parameters (local properties) in the job prior to execution and there seems to be only one way to do it (in the console) Job has to be opened and the deployer needs to edit the values and save them. An this will require DeployJob.Modify permissions which is what we're trying to avoid.
RFE is a great idea but we need to come up with the interim solution now.
What if we use custom property dictionary and creaate a custom prop class for each of these parameters (and change the jobs to use these custom property variables) Then we can give permissions to Modify just these custom properties to "Deployers" and thus avoid giving them Modify permissions to DeployJobs?
What do you think?
maybe the property set in the ET is coming in a future version.
i think the property class/instance thing might work. create instances and set those as the value for the package.
give the role modify on the instances and they can set the value there.
Yes, the property class/instance thing does work - basically we leave refrence to an intance as a value of a local property in the package and never touch it. the instance is then made editable by deployers and contains a bunch of individual property values they can set.
any commands in a package using parameter variables need to be edited to to be in the form of ??instance??.??property?? of course. Not the most elegant solution I'm afraid but it works.
Submitting an RFE as well. It could be very useful for another BMC BSA customer.