Skip to main content

I am running for the ODTUG Board of Directors

By
After some thought, I decided I will be running for the ODTUG Board of Directors this year. I have been attending Kscope since 2008 (New Orleans). Presented at Kscope and APEXPosed since 2009. Did a few webinars. Was a member of the APEX Content Team for Kscope12 and 13. And now I am the Content Lead for the APEX track for KScope14 and Kscope15. So I like spending my free time for ODTUG, to keep Kscope the best conference out there. But ODTUG is more than Kscope. And I would love to add my time, expertise and network to ODTUG in order to do more.
So that's why I am running for the Board.

But it seems I am not the only one running.... As for four positions, there are 24 nominations. Twenty-four! That means the changes are slim, but it shows how vivid ODTUG is. Most organisations that run on volunteers have a hard time filling these kind of positions. ODTUG doesn't. I don't have a full list of names, but I now know about six of them. And they are all well known persons and excellent for the job.
So that's good for ODTUG. Good for the community. And good for you.

My campaign will be focused around internationalisation. The current Board members are all based in North America. So it is natural ODTUG's focus is in that area. But luckily there already are some initiatives to "go global" - but that's not so easy. So I would like to add the views of other regions to the board, whether it's Asia, Australia, South America or Europe. In my opinion ODTUG should go more global, in close collaboration with the local user groups. (Co-)Organising events, webinars and web pages in other languages, etc. Doing so ODTUG should be able to get more members in those areas as well.
That's good for ODTUG, That's good for the community. And good for you as well.

My second focus will be around my favourite Oracle tool of course: Oracle Application Express. So I am in favour of special events that focus in APEX - like the APEXposed we had earlier. And probably we can make this global - that would be awesome. The APEX community within ODTUG already has a strong presence. Therefor we should benefit from this presence and grow even more.
That's good for ODTUG. Good for the community. And thus good for you.

You can cast your vote between October 7 and October 28. And you have to be a paid  member to vote. But that's only $99 a year. And for that small amount of money, you are not only allowed to vote, you have also access to tons of material: articles, recorded webinars and presentations. And you get either a discount or free access to ODTUG events. So in the end ... becoming a member is a no-brainer. Thus if you haven't signed up for it: do it now.
Good for ODTUG. Good for the community. And definitely good for you!

Oh, and then don't forget to vote in October. On me .... 
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

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

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more