Skip to main content

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

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!
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …