Workflow Concepts

Workflow Design

The Auto-Update workflow is a series of static policies, that run static Python code, that all call into one main policy that can be dynamically modified, either in the jamf UI or by automation.

Architecture Diagram:

In the above diagram, is the design of how the static policy chains work. The concept is you will only have to ever build the static policies once. The main idea is that you will only ever modify a single policy, which makes this easier to automate since your code only has to every touch one policy object in the jamf pro application.

Each policy will run the either the silent_update.py or the app_quitter.py script. These scripts will act as templates which you will need to fill out with the proper information in their positional parameters.

In each script, in the document code, there should be descriptions of what to put to make it work. This wiki will also outline that part as well.

The higher level concept of this workflow is that you will have one policy that AutoPKG (optional, but I recommend it) feed into, that is simply scoped to all devices and is only triggered as a manual trigger event. Here is a summary of each policy from the diagram above:

Main Policy

• scoped to all computers
• execution frequency ongoing
• event is a manual trigger
• recon enabled
• AutoPKG feeds this policy through automation of the JSS Importer

Silent Patch Policy

• scoped to a smart group of application name and version
• runs at check in
• executes the silent_update.py script
• no recon
• calls the main policy
• execution frequency ongoing
• manually build this policy once (static)

Prompting Workflow

• scoped to a smart group of application name and version
• runs at check in
• executes the app_quitter.py script
• no recon
• calls the main policy
• execution frequency once a week (you can adjust this to prompt more often if you want)
• manually build this policy once (static)

Self Service Install

• Scoped to all computers
• runs app_quitter.py just in case user has the app open when they execute a policy
• execution frequency ongoing
• no recon
• manually build this policy once (static)

Self Service Update

• scoped to smart group based on application title and version
• runs app_quitter.py just in case user has the app open when they execute a policy
• execution frequency ongoing
• no recon
• manually build this policy once (static)