Skip to main content

Updateable IR...at least sort of ..(a.k.a calling an On Demand Process on a Public Page)

Image
By
On apex.oracle.com I created an example of an updateable Interactive Report. It is not an in-line update functionality, but you can click on an image and so update the status of a record. It is not rocket science but a nice way to present such a functionality to your end users.
But while creating the example I discovered that the example worked on a Page that requires Authentication, but didn't work on an Public Page... To call the On Demand Process I used the namespaced function apex.ajax.ondemand, instead of the more or less old-fashioned htmldb_Get. But unlike the htmldb_Get, apex.ajax.ondemand has no parameter for the page where the process should run (actually apex.ajax.ondemand passes '0' as the page parameter to htmldb_Get). So in order to get things working I needed to mark Page 0 as Public also...
I guess it would be a nice enhancement if you could either pass a page parameter to apex.ajax.ondemand (default 0 is acceptable) or it should use the current page ($v('pFlowStepId')) as a default. Then you don't need to mark Page 0 as Public also. And I want as less Public Pages as necessary...

Comments

Anthony Rayner said…
Hi Roel,

I agree, it makes sense to be able to specify the page for the namespaced version as well. We will look into this.

Anthony.
12:27 pm
Roel said…
Hi Anthony,

And looking at the code it seems not so difficult to make that adjustment.

Cheers,
Roel
2:48 pm
Patrick Wolf said…
Hi,

I think it would make sense to always use "current page" instead of page 0 as Roel suggested. An extra parameter for the page would only make sense if page level on-demand processes are supported in the future and a developer wants to call an on-demand process of another page.

Cheers
Patrick
12:03 pm
Anthony Rayner said…
Patrick,

Ok, I think that a combination of the 2 would make sense, so we default to the "current page", but still provide an optional parameter for the page for the situation Patrick mentioned, (as we are currently looking at page level on-demands) and also where the developer wants to leverage other components (such as regions) defined on different pages.

Anthony.
10:35 am
Patrick Wolf said…
Perfect! :-)
3:58 pm
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function
Post a Comment
Read more