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

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
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

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more