updated for Setup Manager 1.4.2

ChangeLog.md

@@ -1,5 +1,15 @@
 #  Setup Manager - Change Log
 
+## 1.4.1
+
+(2025-12-22)
+
+- `finishedScript` and `finishedTrigger` now respect when `DEBUG` key is set and do nothing (#181)
+- improved error detection and reporting in `DEBUG` mode (#150, #180)
+- adjusted recon/Update Inventory workflow, to adapt to a change in `jamf` binary (#177)
+- fixed custom JSON for Jamf Pro profile for Webhooks (#184)
+- localization fixes
+
 ## 1.4
 
 (2025-12-03)

ConfigurationProfile.md

@@ -21,7 +21,7 @@ These behaviors change in debug mode:
 - `policy`, `recon`, and `shell` actions that require root are replaced with a delay (and will always complete successfully)
 - `watchPath` and `wait` actions timeout and fail after 10 seconds
 
-When in debug mode, you can also set the `simulateMDM` preference key to `Jamf Pro` or `Jamf School`. This allows you to do test runs on un-enrolled Macs.
+When in debug mode, you can also set the `simulateMDM` preference key to `Jamf Pro` or `Jamf School`. This is _necessary_ for test runs on un-enrolled Macs and to launch Setup Manager as a local user.
 
 #### `title`
 
@@ -1118,7 +1118,7 @@ can be localized like this:
   <key>de</key>
   <string>Willkommen!</string>
   <key>fr</key>
-  <string>Bienvenu!</string>
+  <string>Bienvenue!</string>
   <key>nl</key>
   <string>Welkom!</string>
 </dict>
@@ -1170,8 +1170,10 @@ Use these codes for these languages:
 | Italian            | it              |
 | Norwegian          | nb              |
 | Polish             | pl              |
+| Portuguese (Brazil)| pt-BR           |
 | Spanish            | es              |
 | Swedish            | sv              |
+| Turkish            | tr              |
 
 The [plist and profile example files](Examples) contain localizations for many of the custom text elements.
 

Docs/Extras.md

@@ -33,6 +33,8 @@ When you reach the limits of the custom schema, use the XML it generates as a st
 
 Note that the custom schema can become confused when you switch between enrollment action types and you will need to clean up extra empty fields. It is best to delete the action type you don't need any more and create a new action of the desired type.
 
+While the Jamf Pro interface offers different schemas for different versions of Setup Manager, you _only_ have to upgrade to the latest version when you need to use new features only available in that version.
+
 ## iMazing Profile Editor
 
 There is also a manifest for Setup Manager in [iMazing Profile Editor](https://imazing.com/profile-editor).
@@ -45,7 +47,7 @@ The command-Q keyboard shortcut to quit the app is disabled. Use `shift-control-
 
 While Setup Manager is running you can open a log window with command-L.
 
-There are two or three tabs, one for the main Setup Manager log, one showing output from `/var/log/install.log`, one showing configuration profile installation and removal, and (Jamf Pro only) one tab showing output from `/var/log/jamf.log`. Some log tabs will be summarized to events relevant to the enrollment workflow. You can see the full log content by unchecking the 'Summarize' option.
+There are several tabs, one for the main Setup Manager log, one showing output from `/var/log/install.log`, one showing configuration profile installation and removal, and (Jamf Pro only) one tab showing output from `/var/log/jamf.log`. Some log tabs will be summarized to events relevant to the enrollment workflow. You can see the full log content by unchecking the 'Summarize' option.
 
 Note that the extra logs (Install, Profiles, and Jamf) show events that were not initiated by Setup Manager. Nevertheless, these events can be relevant to your enrollment workflow.
 
@@ -68,6 +70,8 @@ For example:
 sudo log show --last 30m --predicate 'subsystem="com.jamf.setupmanager"'
 ```
 
+There is a button at the top of the log window which creates a new folder named `SetupManagerLogs-<timestamp>` in `/Users/Shared` and copies Setup Manager, install, and (when present) jamf log files there. Hold the option key to select a different location. Note the logs are copied in their current state, so wait until Setup Manager is done before exporting. 
+
 ## Debug mode
 
 When you set the `DEBUG` key to `true` in the profile or locally with the `defaults` command Setup Manager will not perform any tasks that actually perform installations or otherwise change the system. When in DEBUG mode, Setup Manager will also read settings from the local settings (i.e. `~/Library/Preferences/com.jamf.setupmanager.plist`) which simplifies iterating through different settings. If you want to run Setup Manager on an unmanaged Mac, you may need to provide a `simulateMDM` key with a value of either `Jamf Pro` or `Jamf School`.

Examples/sample-com.jamf.setupmanager.plist

@@ -113,7 +113,7 @@
 		<key>es</key>
 		<string>¡^[^[Bienvenido](inflect: true)](inflectionAlternative: &apos;Te damos la bienvenida&apos;)!</string>
 		<key>fr</key>
-		<string>Bienvenu!</string>
+		<string>Bienvenue!</string>
 		<key>he</key>
 		<string>ברוכים הבאים!</string>
 		<key>it</key>

Examples/sample-jamfschool.mobileconfig

@@ -101,7 +101,7 @@
 									<key>en</key>
 									<string>Welcome!</string>
 									<key>fr</key>
-									<string>Bienvenu!</string>
+									<string>Bienvenue!</string>
 									<key>nl</key>
 									<string>Welkom!</string>
 								</dict>

Examples/sample-waitForUserEntry.plist

@@ -131,7 +131,7 @@
 		<key>es</key>
 		<string>¡Bienvenido!</string>
 		<key>fr</key>
-		<string>Bienvenu!</string>
+		<string>Bienvenue!</string>
 		<key>he</key>
 		<string>ברוכים הבאים!</string>
 		<key>it</key>