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

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...
Post a Comment
Read more

Stored Procedures in ADF

One of the common requirements for ADF programmers is to invoke Stored Procedures and Functions. Implementing this is so simple with few lines of code in Java classes used under business components. Following code snippets from fusion guide  will help execute different procedures with and without arguments. Execute stored procedure with No Arguments: public void callProcWithNoArgs() { getDBTransaction().executeCommand( "begin devguidepkg.proc_with_no_args; end;"); } Execute stored procedure with only IN arguments: Procedures often take arguments in order to process some business logic. Arguments are limited from none to many. In order to use stored procedures with argument mode we need to use JDBC PreparedStatement object. How To: Create connection Create a JDBC PreparedStatement with procedure details wrapped in a PL/SQL begin..end block. Assign the values to arguments if any. Execute the statement. Close the statement. protected void callStoredPr...
Post a Comment
Read more