Script Studio Pro guide
Script Runner
Script Studio Pro is coming soon. This is preview documentation; details may change before release.
Script Runner is a local test workspace for editing, running, simulating, and inspecting scripts before deployment.
What Script Runner Does
Script Runner helps you:
- Load a script from Script Studio Pro into a test workspace.
- Start a scratch script without changing the connected service.
- Run a script as the current signed-in user inside the app sandbox.
- Run management-style simulations.
- Supply runtime parameters
$4through$11. - Inspect Output, Errors, Simulation, and Guidance.
- Apply runner workspace text back to the selected script editor.
Loading a Script
Use Load From Studio to choose a Script Studio Pro script and load it into the runner workspace.
If the runner workspace contains unsaved changes, Script Studio Pro asks before replacing the runner text.
Scratch Scripts
Use Scratch to start a new temporary script in Script Runner. Scratch scripts are useful for experiments, helper snippets, and quick tests.
Scratch scripts are not linked to the connected service until copied into or applied through a managed script workflow.
Execution Modes
Script Runner supports multiple execution modes:
- Current User: runs locally as the signed-in macOS user inside the app sandbox.
- Management Binary Simulation: runs with management-style root context, runtime parameters, and a simulated management binary.
- Enterprise Simulation: runs with enterprise simulation flags for policies, APIs, inventory, packages, profiles, protected writes, and failure-state testing.
Runtime Parameters
Runtime parameter fields represent $4 through $11. Fill these fields before running scripts that depend on policy-supplied parameters.
If a script references a runtime parameter that is empty, Guidance can show a warning.
Output Tabs
Script Runner separates output into:
- Guidance: admin-friendly explanation of issues, simulation events, warnings, and next actions.
- Output: standard output from the script run.
- Errors: real error output, filtered separately from simulation messages.
- Simulation: Enterprise Simulation messages and virtualised actions.
Applying Runner Changes
Apply Changes copies the runner workspace text back to the selected script editor. This does not save anything to the connected service.
After applying changes, review the script in the main workspace and use Save when ready.