I have been playing with the script step. As I have some specific 'needs' (craves?), I tried to involve dockutil to set the Dock instead of using the native dock step.
We had a nice Slack conversation about this already. My goal is to set the Dock automatically but have a good timing control over it in combination with Jamf Setup Checklist. I do understand why that doesn't fully match the idea of Setup Checklist, as the intention is to guide the user through and not to automate things for them.
However, it works pretty well and I personally like the idea to keep things in one place. I replaced my initial message step by a script step and put my workload in the activateScript. It did exactly what I want, after I took into account that the step (and so the script) could run again.
A script step shows a button to open an item, which makes sense because in most cases the user would need to open something, and simply because it's an advanced variant to the open step. In my case, nothing needs to be opened. I would appreciate an option to hide the button. In other words, to make the script step behave more like a message step.
I have been playing with the
scriptstep. As I have some specific 'needs' (craves?), I tried to involvedockutilto set the Dock instead of using the nativedockstep.We had a nice Slack conversation about this already. My goal is to set the Dock automatically but have a good timing control over it in combination with Jamf Setup Checklist. I do understand why that doesn't fully match the idea of Setup Checklist, as the intention is to guide the user through and not to automate things for them.
However, it works pretty well and I personally like the idea to keep things in one place. I replaced my initial
messagestep by ascriptstep and put my workload in theactivateScript. It did exactly what I want, after I took into account that the step (and so the script) could run again.A
scriptstep shows a button to open an item, which makes sense because in most cases the user would need to open something, and simply because it's an advanced variant to theopenstep. In my case, nothing needs to be opened. I would appreciate an option to hide the button. In other words, to make thescriptstep behave more like amessagestep.