Multiple Variables
Proposal to add option to include multiple pre-set options within variables input. Example, a buildings variable where all of the building options are pre-populated and can select from drop down.
Comments (14)
-
-
Can you give me some use cases where this would be helpful? I can make some up, but I want to understand a bit more how it would be used.
-
reporter One thing that we track with our machines are their physical building location. Currently it is up to the technician to get the correct building name entered and spelled correctly, or even choose the newly decided upon name for the building. We would look to pre-populate that variable with multiple option that could be selected from a dropdown style menu.
-
For my case, I ask a “Munki option” variable to deploy a standard “office app pack” or a “full” DTP app pack after the first boot (and admin auto login).
For now it’s the mds_var2 who ask for “1 DTP / 2 Office”
-
You can watch my video for this : https://www.youtube.com/watch?v=xFASDulnU48
-
Conditional variables can be useful too. If $mds_var3 is set, then ask for $mds_var4.
And also an option to hide variables like password : ••••••
-
I would use it for the ClientIdentifier in my munki ManagedInstalls.plist. We have about 20 group/building manifest and it would remove the need for separate workflows for each ClientIdentifier.
-
- changed version to 2.1
-
- changed milestone to 2.1
-
- changed status to resolved
please verify in PreBeta-MDS_Build-21829_Version-2.1.dmg. See also video at https://www.youtube.com/watch?v=XI1owAKygK8&feature=youtu.be
-
existing workflows show new variables, but new workflows do not.
-
- changed status to open
-
- changed status to resolved
fixed in 21842 or later
-
fixed Issue
#178, regression. added in default values for new workflow→ <<cset 094524d23c16>>
- Log in to comment
A “drop down” style variable would be really useful.