Apex 5 Universal Theme – Navigation Experiment #4

His blog is a gem :)

svenweller

Coloring side menu entries

Sometimes you want to add a little more color to the navigation menu. The idea in one project was to use colors for certain areas in an application. The color would show the user where he is currently working. Whether such colors are a feature that end users like, is still part of an ongoing discussion. But here are the technical details how to implement it.

The example uses a very small apex application that I’ll be using for a DOAG2015 presentation “Exotic SQL” (http://syntegris-doag.de/#vortraege).

Before / After
apex5_sidebar_colored_beforeapex5_sidebar_colored_after

Steps to create this

I explain the changes in detail a little further down.

  1. Create a new List template based upon the current one.
  2. Switch the user interface from the old to the new template
  3. Edit the template
  4. Add colors to the parent list entries
  5. Update alls sub menus to match the parent color

Special Features:

  • can be…

View original post 902 more words

Advertisements

10 Oracle SQL features you probably didn’t know

svenweller!

svenweller

10 Oracle SQL features you probably didn’t know

I can not guarantee that you never heared of this. But the majority of developers doesn’t know or doesn’t seem to know. And honestly –  most of this information is fairly useless – and mostly harmless.

10. Why we have the CONCAT function

There is a concat function that can be used instead of the concat operator ||.

Nobody uses that! But there is a reason why it exists.

This is from the 8.1.7 Oracle documention

On most platforms, the concatenation operator is two solid vertical bars, as shown in Table 3-3. However, some IBM platforms use broken vertical bars for this operator. When moving SQL script files between systems having different character sets, such as between ASCII and EBCDIC, vertical bars might not be translated into the vertical bar required by the target Oracle environment. Oracle provides the CONCAT character function…

View original post 2,420 more words

Why APEX running inside the database is a GOOD thing!

Johns Blog

I’ve had quite a few discussions with people regarding whether APEX running inside the database is a good thing or a bad thing. Personally I believe it is definitely a good thing, I see no downsides really. However a recent forum thread

For me, the fact that APEX runs inside the database means that one of the major positives is you are able to take full advantage of each and every database available to you. A recent forum thread illustrates this very nicely. The poster in the thread has deleted some files and has unfortunately performed a commit before realising their mistake.

Here is where the features of the database can help you, for example we are able to take advantage of the Flashback feature to get the database back to the state it was in before the files were deleted.

The user in the forum deleted some files from…

View original post 838 more words

APEX: Form on a Procedure

Hi!

You have a procedure.

And you want to prepare an interface for enduser so they could execute it by themselves.

however, your procedure is expecting some input parameters which are not so-easy for the users to get..

Let ‘s go with an example:

form_on_a_proc_1

example

Say this procedure is taking an account number and generating a risk report for that customer.

So you decided to publish a form on one of your APEX user dashboards:

form_on_a_proc
Building form on a procedure

After a few easy steps with this wizard, you ‘ll have your form with a field (i.e. :p_acc)on it prompting you to enter an account number

Although it works just fine, it is not that easy for users to know which company has which number. It would be way easier if they could go with company name for instance..

If you have no chance to touch to that procedure, means you can ‘t modify it to make it work with another parameter instead of v_acc (account number), you still can do something similar.

i. Create a Page Item on your page region

ii. Display as: Text with autocomplete

iii. Give your new page item a unique name (i.e. :p_cust_name)

iv. Adjust the population logic of your text field to make auto-complete thing work.

v. Then take a look at execution statement which runs your SP. You can see it by double-clicking Run Stored Procedure

form_on_a_proc_2

vi. You ‘ll see something like this

#OWNER#.basitmis_proc(V_ACC => :p_acc);

vii. Now let ‘s modify it so it could work with our other parameter :p_cust_name

form_on_a_proc_3

Let ‘s see what we did here:

 

i.We declared another variable p_cust

ii.Use it to collect account number. To know which customer ‘s account should return, we used our Page Item p_cust_name and remember, this information was provided by user.

iii.Then we bind it to our SP

**

Now your users can type ABC to automatically get ABC Company in the company name field, then click the button that triggers your execution process. Your little declaration above will do the rest :)

Tschau!