> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details.md). # Condition details Conditions must be met for the actions in a business rule to execute. You can add or update conditions through [Settings](/reference/settings.md) > [Data governance](/reference/settings/data-governance.md) > [Business rules](/reference/settings/data-governance/business-rules.md) > [Conditions](/reference/settings/data-governance/business-rules/business-rule-details/conditions.md). | Condition | Description | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Is classified in category | Test if entity is placed in a specific category. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#is-classified-in-category)) | | Is using product structure | Allowes testing if variant is using a specific product structure. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#is-using-product-structure)) | | Is using variation definition | Allows testing if variantgroup is using a specific variation definition. | | Previous attribute value condition | Use to test if an entity's attribute value was changed from a certain value. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#entity-attribute-value-condition)) | | Updated attribute value condition | Use to test if an entity's attribute value was changed to a certain value. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#entity-attribute-value-condition)) | | Matches attribute value condition | Use to test if an entity's attribute value matches a certain criteria. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#entity-attribute-value-condition)) | | Has enrichment insight value | Allows testing on entities enrichment insight status. | | Regex check | Allows testing if an attribute value on entities matches a specific regex pattern. | | Does not have permission | Use to test if a user does not have a specific permission. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#has-permission)) | | Has archive status | Tests if entity has specific archive status. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#has-archive-status)) | | Has internal id | Tests if an entity has a specific internal id. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#has-internal-id)) | | Has permission | Tests if a user has a specific permission. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#has-permission)) | | Is in workflow state | Tests if entity is a specific workflow state. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#is-in-workflow-state)) | | Is in catalogue | Tests if category is in a specific catalogue. (Additional [configuration](/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details/condition-configuration-details.md#is-in-catalogue)) | | Is created by | Use to check who created the product. | | Is modified by | Use to check the current user making changes. | | Business units | Use to test if business units have a relation to an entity. | | Is classified in catalogue | Use to check if the entity is classified in one or more catalogues. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.struct.com/reference/settings/data-governance/business-rules/business-rule-details/conditions/condition-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.