.png%3Falt%3Dmedia%26token%3Dd0612356-caa4-4568-8fe7-740a2c1b1afd)
.png%3Falt%3Dmedia%26token%3Dd0612356-caa4-4568-8fe7-740a2c1b1afd)
Building Policy Rules
In this article we equip you with everything required to create new policy rules on your own
Building a new policy process is simple and based on few steps:
- 1.Selecting object type - determine what objects will be impacted during the policy execution: assets, defects or tasks
- 2.Structuring filters - allow filtering of certain items that the selected policy will be applied upon
- 3.Setting policy action - determine which operation will be applied to the filtered items and in what frequency
When creating policy rules for assets, defects and tasks, the policy starts by determining the target objects that should be impacted during execution.
Each filter component can have multiple filtering conditions with And/Or operator between them.
Filter component
Additionally, to increase filtering flexibility, the policy editor allows to create additional filter components that can intersect using an And/Or operator.
Logic operators to combine filters
After placing the filters and operators, it's time to add the actual actions that determine what the policy will perform on the filtered objects. Each object type has its own set of actions.
The list of available actions is gradually expanding to cover more and more use-cases.
Assets actions
Defects actions
Tasks actions
The editor supports multiple flows in the same policy rule. The flows can be completely independent or intersect.
Multiple policy flows
There are two types of action components:
- 1.Actions that are done constantly by default, like setting assets' class, tagging, changing defects' severity, etc.
- 2.Actions that requires schedule configuration.
Scheduling
Actions can be scheduled to run once in a predefined date and time, or run repeatedly (daily, weekly, etc.).
Once the policy is ready and saved, you can click the simulate button and view how many items will be impacted based on current data.
