Skip to main content

Why do I attend Kscope?

By
Kscope14 will be my 6th Kscope event. After New Orleans, Monterey, Washington, Long Beach and New Orleans again (yes, I missed San Antonio), this year Seattle will be the place to be at the end of June.

So why do I spent quite a lot of time and money to visit this event? That's because of two reasons: the content and the fellow attendees. Without any doubt the content of Kscope is best you can get in one conference. And it doesn't matter whether your interested in database development, APEX or Hyperion, there's only one conference with that much awesome presentations. And that draws a certain type of people: your fellow attendees. The size of the event and the location (usually) offers an unique opportunity to meet and greet whoever you want. You don't have to make an appointment to talk to someone, as there is a huge chance you'll run into each other at a presentation, during lunch or at the bar. Speaking of lunch ... there is no conference or event that serves better food than Kscope!

During Kscope14 I will do two presentations myself. One in the beginners track about "Starting mobile development with APEX" and one about "Creating hybrid APEX applications".

As the APEX Content Lead, I am looking forward to all (APEX) presentations. Especially all the planned APEX 5 presentations will have my attention. Apart from those I planned to attend the "Pins, Polygons, and Perspectives: Visualizing Geographic Data in APEX" by Christoph Ruepprich and "Oracle APEX + Node.JS A Primer" by John Scott.
Another thing I also like (and has been requested during previous conferences), is the "intro track". So the first two days of the conference we do have one (out of three) complete track 100% dedicated to APEX beginners. And another thing I'm fond of are our "newbie slots". In order to prevent an unequal competition between newbie presenters and well known APEX rock stars, we planned the presentations of the Kscope newbies against each other. So they all get an equal chance to get a full room!

So, right now you understand I am looking forward to Kscope14 a lot. And I hope I'll meet you there in June. Visit http://kscope14.com for all details, abstracts, location and registration.

Labels:
Location: Seattle, Washington, Verenigde Staten

Comments

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