InteractiveMode 0 - App-Auto-Patch/AAP3-Wiki GitHub Wiki

App Auto-Patch: Silent Operation Mode

Overview

App Auto-Patch is designed to streamline the process of identifying and updating installed software. This wiki page focuses on the end-user experience when App Auto-Patch's interactiveMode is set to 0 or Completely Silent mode, where both the discovery of installed applications and the updating process occur without user interaction.

Configuring this option

This option can be configured via MDM using the interactiveMode Key or the --interactiveMode command-line trigger

<key>InteractiveMode</key> <integer>0</integer>

--interactiveMode=0

Silent Discovery and Updating

Process Overview

In Completely Silent mode, App Auto-Patch operates discretely in the background. It automatically scans the Mac for installed applications and checks for available updates. When an update is found, App Auto-Patch via Installomator will attempt to download and install it, ensuring that the software is up-to-date without requiring user interaction.

User Experience

Users benefit from a seamless and uninterrupted workflow, as App Auto-Patch manages updates without displaying prompts via swiftDialog. This feature is especially advantageous in environments where maintaining productivity and reducing distractions is crucial.

Handling Open Applications via BLOCKING_PROCESS_ACTION

Installomator's handling of open applications requiring updates is governed by the BLOCKING_PROCESS_ATION parameter. This parameter can be configured in the following ways to manage open applications:

  • ignore: Continue the update process even if blocking processes (open applications) are detected.
  • quit: Politely requests the open application to quit to proceed with the update.
  • quit_kill: Makes two polite requests for the application to quit, followed by force termination if necessary. This option is suitable for service applications that do not automatically respawn.
  • silent_fail: Terminates the update script without user interaction or notification if a blocking process is found.
  • prompt_user: (Not applicable in silent mode) Displays a dialog box for each blocking process, allowing the user to choose between updating immediately or delaying the update.
  • prompt_user_then_kill: (Not applicable in silent mode) Similar to Prompt_User, but forcibly terminates the blocking process if the user opts to update immediately.
  • prompt_user_loop: (Not applicable in silent mode) Functions like Prompt_User, but re-prompts the user every hour until action is taken.
  • tell_user: Displays a notification about the update, allowing the user only to quit and continue with the update.
  • tell_user_then_kill: Notifies the user about the update and, if the application does not quit, forcibly terminates it.
  • kill: Forcefully terminates the blocking process without prior notification or the opportunity for the user to save their work.
⚠️ **GitHub.com Fallback** ⚠️