This feature is currently in a closed beta. For more information please reach out to your account team.
Prebuilt Apps are the easiest and most efficient way to manage macOS Application lifecycles in Addigy, with an easy-to-search catalog of the most popular applications and a set-it-and-forget-it style of deployment. You can configure exact versions of an application to deploy or have it set to auto-update. Prebuilt Apps include all the MDM profiles required by each software title and give granular management of deployment schedules — all at the click of a button.
This overview guide will show you how to use Prebuilt Apps from the Catalog.
Viewing Prebuilt Apps in the Catalog
Prebuilt Apps are available in the Addigy Catalog by going to Catalog > Software > Prebuilt Apps. This view opens up the application catalog. You can search for applications in the catalog, or you can filter based on Category by choosing the drop-down in the far right.
At a glance, you can see which applications are assigned to a policy and see the number of policies an app is assigned to.
Prebuilt App Assignment View in Catalog
To view the policies a Prebuilt App is assigned to, click on the tile of the software and it will bring up the assignments page.
This page shows all the policies in an organization, with the check boxes indicating whether a Prebuilt App is assigned directly or being inherited (see Viewing inheritance and Inheritance Override section).
New policies can also be added or removed from this window.
You can search throughout their policies on this page, view the application details, and filter by showing only top-level policies or assigned only policies.
Viewing Inheritance and Inheritance Override
To see if a policy is inheriting Prebuilt Apps or if it is overwriting inheritance, hover your mouse over the checkbox. Alternatively, you can quickly determine the status at a glance. A checkbox with a white background signifies it is being inherited. A solid blue background in the checkbox signifies that the Prebuilt App directly in the policy is overriding settings from the inherited Prebuilt App.
Assigning a Prebuilt App to a new policy from the catalog
To assign the Prebuilt App to a new policy, check the box and click Configure Settings in the lower right-hand corner.
Prebuilt App Settings View in Catalog
The Settings view can be accessed by either assigning a new policy and selecting Configure Settings in the Assignment view, or the tab in the top can be clicked into. Any newly added policies are designated with a “new” tag next to it. The default values are Latest and Auto Update, and 14 days for Enforce Update. This can be modified as needed.
Existing Prebuilt App Settings can also be modified in this view.
Targeted Version vs Latest and Auto Update
With Prebuilt Apps, you can choose to push a specific application version or have the policy always deploy the latest application version. The most up-to-date application is labeled as the Latest.
If you choose a specific app version, you will need to come back to choose a different target version when you want a new version of the app to be deployed.
If you wish for a more set-it-and-forget-it experience, you can choose Latest and Auto Update. This will always deploy the latest application version to devices in the policy.
Update Only
This setting enables Addigy to update applications on a device, but it will not enforce the presence of the app on devices. Devices in this policy that have the application installed will update according to the settings configured in Prebuilt Apps, but Addigy will not install the application on devices. This setting assumes the application is in the default application location, and the installation method of the application is not taken into account.
You can toggle the Update Only setting for relevant policies, all within the Settings window of the Prebuilt App:
Enforce Update
This setting allows you to set a deadline for when the app will be forced to update to the latest version. This ranges from the next deployment to 14 days. This can be set on a per-app basis.
The Set all to enforce update dropdown will allow you to set the same day across all policies.
Note: If this setting is set for 10 days, and the end user takes a 14-day vacation, the next time that machine powers on, the application will be forced to update.