Skip to main content

Your Kscope15 abstract is due today (or before Oct 15)!

By
It is still a long time before Kscope15. But if I look at the website .... I can hardly wait! 
A good conference needs a good time for preparation. An awesome conference .... needs even more time. So that's why we need your abstracts a.s.a.p. After the close every member of the review committee will go over every abstract and will give it a rating and a comment. When that's all done, the committee will have a number of (virtual) meetings to select the best abstracts and create the stunning program you expect from Kscope. And last but not least the schedule for the event has to be created where everything falls into it's place ... So we really do need some time after October 15!

But what are we looking for - and this only applies to the Oracle Application Express track as every track has it's own "wish list"...you can see that when you enter your abstract in the Sub Category field. We split it up into these six:
  1. Integration: We often see that it is not "just APEX" out there. As APEX is an open framework it can be integrated with a lot of different technologies: AngularJS, NodeJS, ORDS, MySQL, NoSQL, EBS, Sharepoint, Web services, etc, etc. This integration can be on the front end / browser side or on the back end / database side. It doesn't matter. If you have something to share where APEX is used in combination with any other technology or tool. This is your subcategory.
  2. New Release: With APEX5 lurking somewhere around the corner - and it is pretty save to assume it will be production at Kscope15 ;-) - it is time to share your ideas, thoughts, experiences with this New Release. Did you build your own Universal Theme? Please show it! Did you discover features that boosted your productivity? This is your chance to share it. So everything that's related to specific APEX 5.x features should go into this subcategory.
  3. Real World: How is APEX used within your company? By your clients? We want to hear stories from the real world. Maybe not cutting edge technology - but therefore even more valuable to the audience as they can use it immediately when they get home. Did you built a 3,000 page application? We want to hear about it! Did you built a 5 page application that is used by 10,000 people? We want to know that as well. And everything in between. 
  4. Detail Plunge: You might be familiar with the Deep Dive sessions at previous Kscope's. A specific subject covered to every little detail for two or three hours. For Kscope15 we came up with the idea of a Detail Plunge: similar but way shorter Just grab your most favourite small piece of APEX and tell us all about it! Do you know everything about Interactive Reports? This is your chance to share that knowledge. Totally enthusiastic about web services or XML? Come up and tell! So it isn't a broad subject, but it should be deep ... 
  5. Other: For everything that doesn't fall into one of the other categories. That doesn't mean it isn't worthwhile. Absolutely not! That just might mean we missed a very good subject... So don't hesitate to categorise your abstract as such.
  6. Hands on: There's always place for a good Hands On session. Ideas are more than welcome.
So you should submit your abstract soon .... but certainly before October 15. This is the absolute deadline. No negations possible. No exceptions ... You only have to be an ODTUG member to submit. That can be either a full member for $99,- or an associate member for ... free. But hey, it's just $99,- a year - and for that small amount you get access an awful lot of content on the ODTUG site - and there are other advantages as well, check out the ODTUG web site.

You can submit here. 
See you in Hollywood, Florida!
Labels:

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 o...
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