Sometimes requirements are such that you can’t write a simple SELECT statement to return the information you want to see on a page. For example, you might want a report that displays dates in the first column, names across the top and the task each person is performing on that date as the content of the report. I’ve written a scheduling application that requires a report exactly like this, however, I don’t know the date range or the people that the end user is going to want to see information for.

In another case we have a number of tables that all have the same structure. These are code tables that are used for Select Lists throughout our Forms and APEX applications. These tables all have the same four columns: identifier, code, meaning and an in use flag. There are hundreds of these tables so I don’t want to have to write a separate page to see the data in each of these tables. Not only would this take a considerable amount of time, but I’m likely to go crazy with boredom half way through! Luckily there is an easy solution to both these problems: Dynamic Report Regions. Read the rest of this entry »

Using APEX it’s very easy to display information using forms and reports regions, you could even throw in a chart or dial for a bit of something different. However, it’s also simple to generate HTML pages from PL/SQL code. This opens up a world of choice when it comes to designing and developing your application.

This tutorial is a simple demonstration of creating HTML output from PL/SQL code. It assumes that you have completed the APEX_ITEM Tutorial as it relies on the checkbox and ticked column that you create within this tutorial. Read the rest of this entry »

OK, so you’ve got a report, but you want something more. You want to add functionality to your report. You want to be able to tick things and have it do stuff. Luckily there’s an easy way and it’s called APEX_ITEM.

This tutorial will talk you through adding a checkbox to your report and adding functionality to your page to identify records that are ticked and processing them.

This tutorial assumes you have a workspace with the Sample Application installed.

Read the rest of this entry »

No, I don’t need any help designing a database, or the Oracle Application Express screens. And I’m not even after ideas for a new application, thank you. What I’m after is some suggestions on how to create design specs for APEX applications and any standards that could be followed. As I’ve probably mentioned before, I work for a fairly large software house where traditionally we’ve only worked with Oracle Forms. We’ve just finished developing our first commercial APEX application and we’re about to start on our next one, which will be considerably bigger. Read the rest of this entry »

The interest in APEX is definitely growing and it’s obvious that Oracle has a lot of pride in it. There’s a great deal of APEX buzz at the Oracle events, such as the recent ODTUG08 where Dimiti Gielis, Patrick Wolf, John Scott and Scott Spendolini have all been involved in the excitement. However, some of us can’t simply jump on a plane and jet off to America to join in these events. Read the rest of this entry »

Sometimes the simplest things make the biggest difference. Some users want to see a summary screen when they access an application, others want to get straight to business. If we can reduce the number of clicks required to get users to their desired page then we have happy customers. So how can you tailor your APEX application so that users aren’t just taken to Page 1 when they log in? And what if you don’t want to have page 101 as your login page? Read the rest of this entry »

Did you know the DHTML List (Image) with Submit template has been replaced by the Pull Down Menu with Image template? I’ve not checked all the themes, but certainly the ones we use no longer have this list template. Read the rest of this entry »

In this series of tutorials we have looked at using the apex_application API and learned how to create dynamic branches to return to previous pages. In Part 2 we created a blank About page, which we will now build on using different substitution strings to add extra fields and information.

It is assumed that you have a workspace with the Sample Application installed, as we will be building on this application, and that you have worked through Exercise 2, as we will be adding to the page we created then. Read the rest of this entry »

Part one of this tutorial demonstrated the use of the apex_application API. This second part will build on this to look at other substitution strings that are available and how they can be used. The exercise below will create a simple “About” page that can be used for any APEX application. It is assumed that you have a workspace with the Sample Application installed as we will be building upon this application and it’s data structure. Read the rest of this entry »

One of the most common pieces of functionality we use as Oracle Forms developers is substitution strings. Everything from user and sysdate in triggers to system variables such as :system.current_item in Forms. Substitution strings are also used in APEX and this tutorial aims to show how these substitution strings can be referenced and used. It is assumed that you have a workspace with the Sample Application installed, as we will be building upon this application and its data structure. Read the rest of this entry »