v1.3.1

ChangeLog.md

@@ -1,5 +1,14 @@
 #  Setup Manager - Change Log
 
+## 1.3.1
+(2025-07-17)
+
+- updates to Polish localization
+- improvements to launch process at login window
+- logs macOS version at launch
+- email addresses and urls in markdown text are not active links any more
+- documentation updates and clarifications
+
 ## 1.3
 (2025-07-08)
 
@@ -15,7 +24,7 @@ Notes added since 1.3beta are marked with '(release)'
     - changes to network interfaces are now logged, see the Notes section for details (#15)
     - network status can be shown in the top-right corner of the Setup Manager window
 - new flag file `/private/var/db/.JamfSetupStarted`, which is created when Setup Manager starts. You can use this to scope Mac App Store apps and Jamf App Installers, which prevents these apps from installing early in the enrollment, slowing down the Jamf Pro configuration
-- added [a specific webhook to send a message to Slack](Docs/WebHooks.md#Slack) (#104)
+- added [a specific webhook to send a message to Slack](Docs/Webhooks.md#slack) (#104)
 - two new defaults keys `finishedScript` and `finishedTrigger` allow to run custom behavior when Setup Manager has finished
 - new option `none` for `finalAction` (#115)
 - (release) Polish localization (Thanks to @bsojka)
@@ -91,7 +100,7 @@ When you click on the Network status icon, a popup will show:
 
 Note that the connectivity check is quite basic and might not catch all functionality that is required for a service to work. It should provide an indication whether a service is reachable, but deeper trouble-shooting and monitoring might be required for reliable diagnostics.
 
-Seen["Network Connectivity"](https://github.com/jamf/Setup-Manager/Docs/Network.md) for more detail.
+Seen["Network Connectivity"](Docs/Network.md) for more detail.
 
 #### Finished Script and Trigger
 
@@ -99,7 +108,7 @@ Setup Manager now includes functionality to launch a script or Jamf Pro custom p
 
 There are two keys relevant for this: `finishedScript` and `finishedTrigger`. 
 
-See ["Running Scripts and Policies when Setup Manager finishes"](https://github.com/jamf/Setup-Manager/Docs/Extras.md#running-scripts-and-policies-when-setup-manager-finishes) for detail.
+See ["Running Scripts and Policies when Setup Manager finishes"](Docs/Extras.md#running-scripts-and-policies-when-setup-manager-finishes) for detail.
 
 ## v1.3beta
 (2025-05-27)

ConfigurationProfile.md

@@ -422,6 +422,20 @@ Example:
 </dict>
 ```
 
+This example is the equivalent of this command line:
+
+```
+sudo systemsetup -setTimeZone Europe/Amsterdam
+```
+
+Notes: to break the command in to its components
+
+- full path to the command
+- arguments are split into the `arguments` array, one string entry per argument, no quoting or backslash escaping
+- if the command contains a `&` it needs to be escaped with `&amp;`
+- shell constructs such as substitution (e.g `$SHELL`), redirection (e.g `&2>1`)
+- `sudo` won't work in this context, instead set `requiresRoot` to true
+
 ### Jamf Policy Trigger
 
 #### `policy`

Docs/Network.md

@@ -3,9 +3,9 @@
 Setup Manager can display the current network status in the top right corner of the main window.
 
 By default, the icon will only appear when 
-- there is no network connection
+- there is no network connection or the connection is lost
 - Network Relay is configured
-- the `networkCheck` array is present in the profile
+- the `networkCheck` array is present in the profile, even when it is empty
 
 You can always manually toggle the visibility of the network status icon with command-N.
 
@@ -69,6 +69,13 @@ Example:
 </array>
 ```
 
+Example: empty `networkCheck` array to force Network icon to always show
+
+```xml
+<key>networkCheck</key>
+<array/>
+```
+
 ## Network Change logging
 
 Setup Manager 1.3 adds logging for changes to network interfaces. It is possible that there will multiple entries in the log with regards to the same network change. Most changes logged will be neutral and should not affect your deployment negatively.

Docs/Webhooks.md

@@ -128,3 +128,37 @@ Use this webhook format in the Setup Manager profile:
   <string>--insert url from Slack here--</string>
 </dict>
 ```
+
+### Multiple webhooks
+
+You can send multiple services per event:
+
+```xml
+<key>webhooks</key>
+<dict>
+  <key>finished</key>
+  <array>
+    <string>https://example.com/webhook-finish</string>
+    <dict>
+      <key>kind</key>
+      <string>teams</string>
+      <key>url</key>
+      <string>--insert url from Teams Workflows here--</string>
+    </dict>
+  </array>
+  <key>started</key>
+  <array>
+    <string>https://example.com/webhook-start</string>
+    <dict>
+      <key>kind</key>
+      <string>teams</string>
+      <key>url</key>
+      <string>--insert url from Teams Workflows here--</string>
+    </dict>    
+  </array>
+</dict>
+```
+
+### Webhooks in Debug mode
+
+Webhooks are generally _not_ sent when DEBUG is set to true. However, if you set a `DEBUG` key to `true` _inside_ the webhooks dictionary to true, webhooks will be sent, even when global DEBUG is enabled.