Skip to main content

Validation rules in ADF


Purpose:
   
         Validation rules are used in almost all the applications which includes a database to make sure only valid data is committed to the database. You can define validations on your business service layer or directly on user interface.

 As per fusion guide there are three types of validation rules that can be used on entity objects:

  1. Attribute-level validation.
  2. Entity-level validation.
  3. Transaction-level validation.
Attribute-level validation:

         These validations are applied on attributes. Few examples might be upper and lower limit for salary, OrderDate should not be a date in the past and Length of attribute values. 


How to:

  1. Select the attribute on EO.
  2. Edit Attribute.
  3. Validation.
  4. Define the check you want to perform under Rule Definition.
  5. Use Failure Handling to provide info to user.
*Any conditions needed to perform/skip validation can be added in Validation Execution.

Entity-level validation:

          These are rules whose implementation requires considering two or more entity attributes, or children entity rows, in order to determine the success or failure of the rule. These validations are similar to attribute-level but with a broader scope which can be applied to whole row. One example is EventOrganiser cannot be a participant, collection validator. When entity-level method validation is created, a method will be added to EO's custom java class.

How to:

  1. Go to EO.xml
  2. Business Rules
  3. Add Entity Validator.
  4. Define rule by selecting available rule types from Rule Definition.
  5. Validation Execution with "Execute at entity level" and select attributes to which the rule should be applied.
  6. Use Failure Handling to provide info to user.


 Transaction-level validation:

            TL validation will be handy when you want to defer validation execution to transaction level or when you want to validate multiple rows data. This validation will be performed after all entity-level validations are performed. An example might be where only one eventOrganiser is allowed for each event. Creation is same as in Entity level except that "Defer Execution to Transaction level" is selected in Validation Execution tab. This method will be added to EO's java class.

Happy Coding :)



Labels:

Comments

Post a Comment

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...
Post a Comment
Read more

RADUS#4 - Caching the response in REST API's

  Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...
Post a Comment
Read more

Set BIND VARIABLE and EXECUTE QUERY programmatically in ADF

A very common scenario in ADF is to set a bind variable and execute query programmatically within AMImpl/ VOImpl classes. Here's a simple way to do this: To set bind variable for all rowsets:       ViewObjectImpl someVO = this.getSomeViewObject();       VariableValueManager vMngr = someVO.ensureVariableManager();        vMngr.setVariableValue("DefinedBindVariable",value);        someVO,executeQuery(); To set bind variable for default rowset:          ViewObjectImpl someVO = this.getSomeViewObject();          someVO.setNamedWhereClauseParam("DefinedBindVariable",value);          someVO,executeQuery();
2 comments
Read more