Business rules
Business rules enable 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 (including all extended field types in the overview tab), and requests (for select fields only - Reason, Reason Code, Received Date, Request For, Request ID, Request Type, Status, and Subtype).
For style, material, and trim overview extended fields, you can use all field types (text, number, drop down, date, and check box).
You can create style BOM rules for save events only, while you can create delete events for styles 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.
Business rules that you create can also apply for the Infor PLM for Fashion Extension for Adobe Illustrator and CLO-Vise plug-in.
If a field is affected by a business rule, make sure that you add the affected field in your custom views or set it as visible in the plug-in.