As a Workspace ONE UEM admin, you can view settings related to the policy service of product provisioning. Do not alter the settings on this page unless you know what they do and have discussed it with a Workspace ONE UEM representative. Altering them could adversely affect your environment.
What can you do with the Policy Engine Settings page?
The path to the settings page in the Workspace ONE UEM console is .
With the Policy Engine Settings page, you can review settings for the product provisioning service. You can edit options on this page but only do so if you have help from your Workspace ONE UEM representative.
Determine your Organization Group hierarchy
- Current Setting – Select whether to Inherit or Override the displayed settings. Inherit means use the settings of the current organization group's parent OG, while Override enables the settings for editing so you can modify the current OG's settings directly.
- Child Permission – Select the available behavior of child organization groups that exist below the currently selected organization group. Inherit only means child OGs are only allowed to inherit these settings. Override only means they override the settings, and Inherit or Override means you can choose to inherit or override settings in child OGs that exist below the currently selected OG.
Maximum Threads
Enter the maximum number of threads the system spawns to service work items from the in-memory queue.
If there are more work items selected than threads available, then the policy engine will spin up additional threads until it meets this maximum amount. Only the number of devices as there are threads available will contact at once.
As a thread completes the operation for the work item, the system allows it to decay (provided there is no more work in the in-memory queue) down to the minimum threads level.
Queue Batach Size
The Queue Batch Size is the interval the policy engine picks up work items from the database and claims into the in-memory queue. If set to zero, it attempts to claim everything so in a multiple policy engine scenario, it should be set to a non zero value, like 1000, to avoid starving a policy engine.
Audit Policy Engine Queue
When enabled, the product provisioning system stores policy engine queue items in Policy Engine Queue Audit.
Audit Device Policy Job
When enabled, the product provisioning system stores product jobs in Policy Job Audit.
Device Batch Size
Enter the number of devices you want the Policy Engine to act on in batches.
Product Batch Size
Enter the number of products you want the Policy Engine to act on in batches
Maximum Try Count For Failed Items
Enter the maximum number of times you want the Policy Engine to retry processing after a failure.
Back Off Time For Failed Items
Enter the maximum time in minutes, that you want the Policy Engine to try to process after a failure.
