Business rule

Business rule enables you to define business logic using conditions and other parameters. The logic aims to support business processes that need to be incorporated when creating and providing information for products, materials, requests, among others.

You can create business rules to build basic data entry validation and mandatory field checking. You can define what fields are required during data creation, or what specific brands are shown for a given category, for example.

When creating business rules, you define a condition based on an entity, a role, or a required field, then define actions to take when a certain condition is met, or another action to take when the condition is not met.

You can add multiple conditions to a business rule. While you can nest conditions (condition within a condition), it is better to keep your conditions simple for easier maintenance.

You can create business rules for styles, materials or trims (overview tab fields), and requests (for select fields only - Reason, Reason Code, Request For, Request ID, Request Type, Status, and Subtype).

You can create style BOM rules for save events only.

You can create rules that establish dependencies between different tabs or information clusters of a style. For example, you can create a rule that checks if a style BOM meets a certain criteria (BOM status is set to operation or main material is defined, for example) before the style status can be set as For Approval.

You can also create a rule that goes the other way. For example, you can create a rule where you set and check conditions in the style overview tab when working on style BOM.