Menu Close

Self Service Policy Progress with swiftDialog

Learn how to provide your users more detailed feedback for standard Jamf Pro Self Service policies with a proof-of-concept script from Bart Reardon, the creator of swiftDialog


Earlier this week on the MacAdmin’s #swiftdialog channel, Drew Diver asked if it were possible to use swiftDialog as a status bar for Jamf Pro’s Self Service.

“Ah, the Holy Grail …” was my reply.

Bart Reardon may just have delivered (once again).



The TL;DR of this approach is to:

  • Clone your current Self Service policy
  • Remove all of the Payloads and add Bart’s script
  • Add a Custom Trigger to your original Self Service policy and disable displaying it in Self Service


Presuming the latest version of swiftDialog is already installed on all of your fleet, complete the following steps to provide your users more detailed feedback for Jamf Pro Self Service policies.

A. Add Bart’s script to your Jamf Pro server
  1. Add Bart’s script to your Jamf Pro server (which I renamed in Jamf Pro to swiftDialog Self Service Policy Progress)
  2. Specify the following for Options > Parameter Labels
    • Parameter 4: Policy Name
    • Parameter 5: Policy Trigger
    • Parameter 6: Icon URL
  3. Click Save
B. Clone Current Jamf Pro Self Service Policy
  1. Clone your current Jamf Pro Self Service policy
  2. Append Options > General > Display Name with (swiftDialog Progress)
  3. Remove all packages from Options > Packages
  4. Remove all scripts from Options > Scripts
  5. Add the swiftDialog Self Service Policy Progress script
  6. Specify the Parameter Values
    • Policy Name: Cloud Foundry
    • Policy Trigger: cloudFoundryInstall
    • Icon URL:
  7. Remove all other Options payloads as necessary
  8. Click Save
C. Modify Current Jamf Pro Self Service Policy
  1. Enable Options > General > Trigger > Custom and specify a unique Custom Event, which precisely matches the value specified in Step B6
  2. Disable Self Service > Make the policy available in Self Service
  3. Click Save


To my delight, this all worked as advertised on the first and third tests, which were both on physical hardware; the second test — on a virtual machine — failed and I didn’t invest in any cycles debugging why.

After some extremely minor changes to Bart’s script, we’re now ready for internal review.


If instead of “standard” Jamf Pro Self Service policies, you’re using Installamotor, be sure to check out Display Installomator Progress with SwiftDialog in Jamf.

Posted in Jamf Pro, Scripts, Tips & Tricks

Related Posts