Skip to main content

Oracle Apex Basics: Conditional Formatting

Our Objective:

Here I will be outlining how to apply conditional formatting to your grids and reports in oracle apex, for instance shading highly positive figures as green or negative figures as red. This can be especially helpful when creating end user reports.

Lets Begin:

First you will need the report you're applying the formatting to, to have an SQL query as it's source.

Once you have the query you want, we need to add an additional "Conditional_Formatting" column, and for that column to be populated with 'Green' should a certain column's data meet a criteria. Here I have made the 'Conditional_Formatting' column populate with 'Green' when the figure in the 'Likes' column is greater than or equal to 2.

This will have added an extra column to our report, one which you will probably want to hide from view as it is only used in deciding the color of the conditional formatting. 

From here we need to write the HTML expression for the column we want the formatting to be applied to, if you want the whole row to be highlighted you would need to duplicate the HTML expression for each of them, adjusting the column name in the script as you go.

Below is the HTML expression I have used in this example, as you can see it applies a style to the 'LIKES' column, by pulling the value from the 'Conditional_Formatting' column and inserting it into the HTML expression as the 'color' value.

To customize this to your applications needs simply change the html color coding and the sql formula for the "Conditional Formatting" column as required, so if you want negative figures to be shaded red, simply adjust the SQL formula to populate the 'Conditional Formatting" column with the word 'Red' when the require value is less than 0.

 I hope this information proves useful to you and let me know of any other aspects of Oracle Apex that could deserve a blog to help explain.

Thank you for reading,

You can read many other useful Oracle EPM Cloud and Netsuite ERP blogs posted by my colleagues at Brovanture here



  1. Any player shall be entitled at the time the winner is decided to name for a verification of numbers drawn. The verification shall be within the presence of the member designated to be cost of|in command of|in control of} 카지노사이트 the occasion or, if such individual is also be|can be} the caller, within the presence of an officer of the licensee. The failure of any licensee to make funds as prescribed in paragraph is a violation of this part, and the licensee could also be} subjected by the fee to a civil penalty of as much as} $1,000 for every day the tax cost just isn't remitted.


Post a Comment

Popular posts from this blog

Connecting EPM Cloud Planning to Apex with Rest API: GET Substitution Variables

Intro: Oracle Apex and Oracle Planning should be a match made in heaven, both are cloud based and full of API possibilities. You can even get a free trial of Apex  here to see if these sort of features would prove useful for you, or your organisation. Our Objective: Here I will be outlining how to create a table in Oracle Apex that dynamically pulls through the substitution variables from a Planning application, In a follow-up blog post I will try and outline how to then push changes made to the substitution variables in Apex back into Planning. Let's Begin: We start off this process in the “Shared Components” area of the application you want to add the substitution variables table to . Then to “Web Source Modules” within the “Data Sources” tab. From here we click “Create” , then select the “From Scratch” option. Then here we select “Simple HTTP” , name the module anything of your choice; I’ve named mine “Planning_Substitution_Variables

Connecting EPM Cloud Planning to Apex with Rest API: Running Jobs in Planning from Apex Part 2 of 2

In Part 1 I covered how to setup your web source modules, one to perform a GET request on available jobs, and another to perform a POST request to run these jobs. Now lets build the connector between the web source modules and our application. Head over to SQL Workshop and create a new Package  with the following "Specification" and "Body" , substituting "PLANNING_RUN_JOB" with the name you gave your package. Or as text: Body: create or replace package PLANNING_RUN_JOB as procedure planning_run_job(   p_jobtype varchar2,   p_jobname varchar2 ); end planning_run_job; ---------------------- Specification: create or replace package body PLANNING_RUN_JOB is procedure planning_run_job(   p_JobType varchar2,   p_JobName varchar2 ) is   l_parameters apex_exec.t_parameters; begin   apex_exec.add_parameter(p_parameters => l_parameters, p_name => 'JOBTYPE', p_value => p_JobType);   apex_exec.add_parameter(p