Closed dwshore closed 5 years ago
You are correct. The customer is creating a list of selections. The policy event you are calling referenced from softwareInstall would look at that list and perform accordingly. In our environment we use event triggers rather than policy id numbers as that makes things more portable when moving between environments (qa to prod for example).
The script living behind the policy called would move through each item in the list, updating the UI along the way by writing to the property list. This way, if there is a change to success criteria, that can be incorporated into the script / policy without having to change the app. You can feel free however to build the app for your needs, if executing multiple policies through the app works better for you.
In the JAMFConstants.swift file, line 29:
It's not clear what to put in for either of these variables. Is there an expectation that there's one policy that installs everything? Or how do we define a different ID for each of the different bundles we want to deploy?
Thanks!