Ability to set Variables per Location / Network environment.
These variables would override any variable with the same name set at a higher level (ie. System).
This would allow us to utilize these variables in bundle actions, to specify a content location outside zenworks, location specific values, etc. Currently, this is either not possible, or requires elaborate setup / scripting. Since the ability to set and use variables is already available, making it work on a location level should not take too much time and will offer a very dynamic way of setting up your bundles and more.
by: Wouter M. | over a year ago | ZENworks Control Center
Comments
Totally Agree!
Was just having internal discussions on solutions on how to handle this and how this very thing was needed for a proper solution.....
Perhaps it is possible to use the same choices as we can use in the requirements filter settings
This would be very useful!
Would be very usefull. We now put a variable like thing in the network environment name and extract it with a bundle install action script (zac cl output parsing).
Note: I implemented this for a customer who need to deploy software from different UNC shares across 40 locations. Maintaining 40 actions per bundle or 40 bundles per package was not really an option. See - https://community.microfocus.com/t5/ZENworks-Tips-Information/ZENworks-Implementing-Dynamic-Variables-Based-Upon-Location/ta-p/2759594/jump-to/first-unread-message