Configuring business rule validations and overrides

About business rule validations and overrides
Sterling Order Management System supplies a validation framework that you can use for business rule validation and override scenarios.
Validation domains
A validation domain represents the functional area to which an business rule validation belongs.
Business rule validations
A business rule validation identifies a business scenario, either system-defined or defined by the user. Examples might include:
Validation policies and override rules
One or more validation policies can be associated with a validation. Validation policies are the business rules that define the conditions under which a transaction can proceed. A validation rule is either defined by business users or supplied predefined by the system. It requires configuration of applicable dates, document types, channel, region, and other attributes. A quantity or other data point, such as a value that specifies the maximum number of coupons to be allowed against an order or a minimum age, might also be required.
Override rules
Order validations and overrides
You can review the information about order validations and overrides.
Pricing validations and overrides
Payment capture validations and overrides
Payment processing validations and overrides
Returns validations and overrides
Approval plans
An approval plan presents a hierarchy of users that can allow or reject an override. It also considers information such as user department and user role.

Parent topic: Configuring Distributed Order Management