Business Policy

3.3 Business Policy

OBAPI supports three types of validations

DTO field validations: These are the field level validations such as syntax check of the input. These validations are achieved by using field level annotations in request DTO. These validations are not available for extension. Below is the list of out of box annotations available

Annotation	Description
@Email	This annotation is used to validate the respective field with email regular- expression. If the field doesn't satisfy the mentioned regular-expression then the respective error code is thrown
@Mandatory	This annotation marks the fields as mandatory. Once marked, if the field is null then respective error-code is thrown Eg. `@Mandatory(errorCode = DemandDepositErrorConstants.DDA_MANDATORY_ACCOUNT_ID)` private Account accountId;
@Length	This annotation marks the lengths of the fields. Once marked, if the validation is violated then the respective error code is thrown. Eg. `@Length(min = 2, max = 20, errorCode = PartyErrorConstants.PI_LENGTH_EXTERNAL_REF_ID)`
@NonNegative	This annotation checks that the value is non-negative
@Regex	This annotation checks if the value matches regular expression provided

System Constraints: System performs these checks mandatorily. It is not possible to override or bypass these checks.

Business Policies: These are typically the business validations required to be performed before executing business logic. OBAPI framework allows customization developer to override business policies as per the requirement.

Parent topic: Extensible Points in Service Tier