Thank you to everyone who's participating in the Flex Policies beta so far! We've seen some creative and powerful workflows for ordering device inventories, automatic remediation, and software updating with the use of Flex Policies. In June, we are introducing some fundamental changes to Flex Policies.
Moving devices from their root policies
You will now be able to move devices out of their root policies. The root policy is the policy your device was in before you enabled the Flex Policies beta. Initially, we restricted the ability to move devices outside of their root policy so that you may revert back to your original policy hierarchy. As Flex Policies becomes more robust and admin workflows increase in complexity, this restriction is no longer necessary.
It's important to note that after this change is shipped, removing a device from its root policy and disabling the Flex Policies beta will leave your device in a "No Policy" state.
Saving and Testing Filters
When creating an Auto Assignment for a Flex Policy, you'll find that you have to test the filter and save at the same time. We're going to split these two actions so that you can test filters and save auto assignments independent of each other.
Auto Assignments and Static Fields
We're extending the Auto Assignment functionality to not only support Addigy default facts and Custom Facts in your rules but also include Static fields. You'll be able to create Flex Policies that assign and remove devices based on the Static information you have attached to the device via static fields.
We'd love to hear what you think about these up-and-coming changes, feel free to reach out to product@addigy.com with your feedback or any questions you might have.