Skip to main content

Usage

This section describes three basic examples of implementing the plug-in to validate a simple form and interactive grid columns. The usage guide shows a basic implementation of the plug-in but does not describe the plug-in attributes or ideas on how the plug-in can be used.

Examples of how the plug-in attributes can be used to enrich the validation process are shown and described in the Client-side Validation Pro sample application.

Validation on Button Click​

This guide describes the plug-in validation performed after clicking the BTN_PLUGIN_VALIDATION button. The dynamic action implementing the plug-in only performs validation without submitting the page and doesn’t implement any fancy features of the plug-in.

Introduction​

In an example application, page 710 is defined. On the page, a region called Form is created and contains 3 items and 1 button.

Oracle APEX items:

  • P710_ENAME
  • P710_DEPARTMENT
  • P710_SAL

Oracle APEX buttons:

  • BTN_PLUGIN_VALIDATION

The BTN_PLUGIN_VALIDATION button has it’s behavior set to Defined by Dynamic Action and it will be used to trigger the plug-in validation.

Each item has a native Oracle APEX validation defined which is described in the table below:

ItemValidation
P710_ENAMEItem is NOT NULL
P710_ENAMEItem is alphanumeric
P710_DEPARTMENTItem is NOT NULL
P710_SALItem is NOT NULL
P710_SALItem is numeric

Page 710 in page designer is presented below:

The resulting page will look as follows:

Implementing the Plug-in​

To implement the plug-in, creating a new dynamic action is required. Follow the steps below:

Dynamic Action​

  1. Create a new dynamic action
  2. Change the dynamic action’s name to The plug-in validation on button click
  3. Set When \ Event to Click
  4. Set When \ Selection Type to Button
  5. Set When \ Button to BTN_PLUGIN_VALIDATION

The dynamic action definition in the page designer is presented below:

Dynamic Action - True Action​

The default true action of the newly defined dynamic action is Show.

  1. Select the default true action Show
  2. Change Identification \ Action to Client-side Validation Pro [Plug-in]
  3. (Optional) Configure the plug-in using the Settings attributes
  4. Set Affected Elements \ Selection Type to Region
  5. Set Affected Elements \ Region to Form
  6. Set Execution Options \ Fire on Initialization to No
  7. Save the page

The plug-in dynamic true action is presented below:

Test the Implementation​

  1. Open page 710 in browser
  2. Click button BTN_PLUGIN_VALIDATION (plug-in validation)

The result after clicking the BTN_PLUGIN_VALIDATION button is presented below:

Validation on Item Event​

This guide describes the plug-in validation performed each time the Lose Focus event is triggered on any item in the specified form. The dynamic action implementing the plug-in performs only the defined validations without implementing any fancy features of the plug-in.

Examples of how the plug-in attributes can be used are shown and described in the Client-side Validation Pro sample application.

Introduction​

In an example application, page 720 is created. On the page, a region called Form is created and contains 3 items.

Oracle APEX items:

  • P720_ENAME
  • P720_DEPARTMENT
  • P720_SAL

Each item has a native Oracle APEX validation defined which is described in the table below.

ItemValidation
P720_ENAMEItem is NOT NULL
P720_ENAMEItem is alphanumeric
P720_DEPARTMENTItem is NOT NULL
P720_SALItem is NOT NULL
P720_SALItem is numeric

Page 720 in page designer is presented below:

The resulting page will look as follows:

Implementing the Plug-in​

To implement the plug-in, creating new dynamic action is required. Follow the steps below:

Dynamic Action​

  1. Create a new dynamic action
  2. Change the dynamic action’s name to The plug-in validation on item(s) Lose Focus event
  3. Set When \ Event to Lose Focus
  4. Set When \ Selection Type to Region
  5. Set When \ Region to Form

The dynamic action definition in the page designer is presented below:

Dynamic Action - True Action​

The default true action of the newly defined dynamic action Show.

  1. Select the default true action, Show
  2. Change Identification \ Action to Client-side Validation Pro [Plug-in]
  3. (Optional) Configure the plug-in using the Settings attributes
  4. Empty the Affected Elements \ Selection Type attribute (set value to - Select -)
  5. Set Execution Options \ Fire on Initialization to No
  6. Save the page

The plug-in dynamic true action is presented below:

Test the Implementation​

The plug-in validation is executed when the end-user leaves the input (event Lose Focus is triggered)

  1. Open page 720 in a browser
  2. For item P720_ENAME
    1. when the field is empty, focus it and click outside of it - validation Ename not null error message is displayed
    2. input non-alphanumeric values and click outside of the item - validation Ename alphanumeric error message is displayed
  3. For item P720_DEPTNO
    1. when the field is empty ( - Select - ), focus it and click outside of it - validation Deptno not null error message is displayed
    2. select any value that is not - Select -, no validation errors are displayed for this field
  4. For item P720_SAL
    1. when the field is empty, focus it and click outside it - validation Sal not null error message is displayed
    2. input a non-numeric value and click outside of the item - validation Sal numeric error message is displayed

Example validation result after providing invalid values is presented below:

Validation on Interactive Grid Columns​

This guide describes the plug-in validation performed each time the Change event is triggered on interactive grid ENAME, JOB, and SAL columns. The dynamic action implementing the plug-in performs only the defined validations without implementing any fancy features of the plug-in.

Examples of how the plug-in attributes can be used are shown and described in the Client-side Validation Pro sample application.

Introduction​

In an example application, page 730 is defined. On the page, an interactive grid region called Employees is created on the emp table. Columns ENAME, JOB and SAL have native Oracle APEX validations defined as described in the table below:

ColumnValidation
ENAMEColumn is not null
ENAMEColumn is alphanumeric
JOBColumn is not null
SALColumn is not null
SALColumn is numeric

Page 730 in page designer is presented below:

The resulting page will look as follows:

Implementing the Plug-in​

To implement the plug-in, creating a new dynamic action is required. Follow the steps below:

Dynamic Action​

  1. Create a new dynamic action
  2. Change the dynamic action’s name to The plug-in validation on IG column(s)
  3. Set When \ Event to Change
  4. Set When \ Selection Type to Column(s)
  5. Set When \ Region to Employees
  6. Set When \ Column(s) to ENAME,JOB,SAL

The dynamic action definition in the page designer is presented below:

Dynamic Action - True Action​

The default true action of the newly defined dynamic action is Show.

  1. Select the default true action, Show
  2. Change Identification \ Action to Client-side Validation Pro [Plug-in]
  3. (Optional) Configure the plug-in using the Settings attributes
  4. Empty the Affected Elements \ Selection Type attribute (set value to - Select -)
  5. Set Execution Options \ Fire on Initialization to No
  6. Save the page

The plug-in’s true action is presented below:

Test the Implementation​

  1. Open page 730 in a browser
  2. For the ENAME column, insert invalid characters (out of alphanumeric scope). For example !@#.
  3. For the JOB column, select the null value (- Select -)
  4. For the SAL column, insert invalid characters (out of numeric characters). For example Not numeric value.

The validation result will be visible after you leave the currently edited column. Example validation errors are presented below: