Yesterday, I was part of the KScope 14 APEX Abstract Review call. This call is used to discuss the rankings that the Abstract Review Committee has previously given each session. Naturally, we use APEX to help with this process - specifically WebSheets. The call allows us to ensure that the selections are as fair as possible. We make sure that no single presenter has too many slots, ensure that there are enough first-timers vs. veteran presenters and keep the topics of the accepted abstracts balanced. This process has been extremely useful in the past, and really makes for a much better conference.
In reviewing the abstracts, I could not help but keep mentally creating a do's and don't list when it comes time to submit an abstract. While most of them were fairly decent, there were a few that were sub-par in relation to the others, and there were a couple that stood out.
Based on this, I've come up with an ad-hoc list of things to consider when submitting an abstract for any conference. It's in no particular order and by no means complete, but I figured that I'd blog this out while it's still fresh on my mind. Here goes:
Catchy titles can definitely draw attention to your session. While the title "Intro to APEX & jQuery" clearly spells out what is covered, it's a bit bland. A more creative version would be something like “jQuery & APEX: 10 Must-Know Commands in an Hour”. Be careful not to use too long of a catchy title, as that's one of the sure-fire ways to not get accepted. If you can't spell it out in just a few words, then perhaps the topic needs to be re-thought.
If you're going to use a catchy title, then keep this in mind: you immediately raise the expectations of the reviewers. Nothing is more disappointing than a catchy title followed by a sub-par summary & abstract. So make sure that you spend at least as much time on the abstract as the title itself!
Less is More
Being succinct is key. We had well over 100 abstracts to review, and if your abstract doesn't stand out in the first sentence or two, then chances are the rest of it may get ignored. You’re not writing a book or even a chapter of a book here, so there is no time to build up what you want to say. Simply just say it!
KScope gives you two places to sell your session: Summary & Abstract. A sure-fire way to sink your session is to copy & paste the same text in both of these. They are different, and if you can’t take the time to fill them out correctly, don’t expect much in return. The Summary should be a paragraph or so that sells the session. This is what most reviewers read first. If it’s good & compelling, we’ll read the abstract. If not, then perhaps not.
Consider this example of a presentation summary:
Now, consider this one:
Want to learn how to enhance your application’s visual impact without learning any new commands or languages? Then this session is for you! We’ll show you 10 quick & easy ways to utilize jQuery to add some sizzle to your APEX application - all without more than a line of code each!
Clearly the second one just feels more exciting. It asks a question - which acts as a hook for the reviewer. It then spells out pretty clearly what it will cover, and throws in the added benefit of “one line of code each”. It doesn’t waste any time defining jQuery, but rather almost leaves that to the reviewer. If they know what jQuery is, then there is no issue. If they do not, they can either look it up or come to the session to learn more about it.
One note of caution about being succinct: there is such a thing as too succinct. Have a peer or two read your summary and then ask them to describe what they think will be presented. If they are too far off the mark, you may need to add some more content to it.
The abstract is where you’re going to spell out what you highlighted in the summary. Here’s where you can and should get somewhat technical. In the example above, spell out the 10 things that you’re going to cover. This is the only chance that we’ll get to see the outline of your presentation. If you fail to do this, then you’re less likely to get accepted.
Google it. Now print it out, and read your abstract. Did you get bingo, or even come close? If yes, then you have too many buzzwords. Nothing aggravates me more then reading a sentence, pausing, and wondering just what the heck the point of that sentence was.
Know Your Audience...
There are less than 50 available slots at KScope in the APEX track. While that’s a relatively large number, it’s actually not, especially based on the large number of submissions that we had this year. Throw in things like the Intro track and some of the deep dives, and this number gets even smaller.
Therefore, one of the key criteria that we consider is how wide of an audience will your session appeal to. There’s probably no such thing as too wide (as long as it has to do with APEX), but there is definitely such a thing as too narrow. A topic that covers IRs or Charts or jQuery will have a wide appeal, because we all use those components. Something like mobile will have a narrower, but still wide enough appeal, because many of us use it. However, once you venture into the more obscure corners of APEX, the audience starts to get dangerously narrow, and the likelihood of acceptance goes down as well.
…And Your Audience Should Know You
Speaking at a large conference such as OpenWorld or KScope is something that is earned. Thus, getting accepted may also take a little bit of work. If you did submit an abstract and not get accepted, don’t give up. Rather, try to start establishing a name for yourself. You can do this a number of different names: blogging, Twitter, and presenting at smaller, local conferences, just to name a few. Nothing delights the reviewers more than seeing a name of a popular blogger show up in the KScope APEX track.
The best part about blogging & social media is that everyone starts on the same level. If you start a new blog, your content and content alone will determine how others perceive your understanding of the topics that you blog on. If your posts are very detailed and contain a lot of good information, it’s more likely that people will share them, thus increasing your exposure. If they are not well written and technically incorrect, people will remember that, too.
While this post is clearly too late to matter for KScope '14, I hope that it can be helpful for any other conference whose submission deadline has yet to pass. Feel free to add your own advice in the comments.
To use it, simply create or edit a database connection, and set the Connection Color to whichever color you choose:
Once set, any and all windows associated with that connection will be outlined in that color. That's it! I already gleefully went through my connection list and associated different colors with different types of connections. For example, our development schemas got green:
While our production schemas got red:
Now, no matter what type of object I am editing, I will instantly know which schema it belongs to based on the color of the border. Simple AND effective!
Despite this fact, there are a couple of new "features" that were added by way of a new packaged applications called Sample Reporting and Data Reporter. Let's take a look at Sample Reporting first. Upon initial inspection, this application seems quite unremarkable and basic, as it simply contains a few IRs and standard reports. However, after a closer look, it is obvious that there is more to this than what is on the surface.
Upon running the Sample Reporting application, you'll see the following main five options:
The first two - Interactive Report & Standard Report are nothing more than their titles imply, and I won't spend any more time discussing them in this post. The last three, however, do merit some additional attention.
Filter Reports will seem very familiar to you, as this type of report has been implemented by a number of web sites. Basically, there is a list of filters on either the left side of in a drop down. Selecting a filter will, well, filter the report based on that criteria. Adding additional filters will OR each condition.
The point behind Filter Reports is to enhance usability by reducing the number of options available. While IRs are great, they may be overwhelming and not intuitive enough for some users. Filter Reports solves this problem by presenting all of the available options right there on the page. Users need only click on what they want to see.
If this is something that you think your users will benefit from, then you need to check out the second new packaged application, Data Reporter. Data Reporter allows you to create a Filter Report on any table in your schema. Rather than go into more detail on how to create a new report with the Data Reporter application, I'll reference Mike Hichwa's blog post here: http://michaelhichwa.blogspot.com/2013/09/apex-423-released-new-packaged-app-data.html
It would not surprise me at all if Filter Reports were integrated into APEX 5.0, as I think that a lot of users will benefit from their more streamlined approach to mining data.
The Use Cases section offers a number of different scenarios that involve APEX reports, as illustrated below:
While some of these examples are simple, many of them provide clear and concise examples on how to take your APEX reports to the next level. For example, the Custom Reports Template & Custom Buttons one illustrate how to easily change the look & feel of your reports to make them easier to use. Developers of all skill levels will be able to utilize these Use Cases as points of reference for their own projects.
As APEX developers, we often forget about the pure power available to us in the database itself. From advanced search techniques to analytic functions, the Oracle Database can provide a layer of functionally that is unsurpassed. The SQL Examples section outlines some of these features.
If nothing else, every APEX developer should have a look at these example and their corresponding SQL statements. At a minimum, they will serve as a refresher. But in most cases, most developers will learn a thing or two from these examples.
APEX 4.2.3 is available now as a patch or as a fresh installation. If you don't want to upgrade your own instances, then head on over to apex.oracle.com, as it is running 4.2.3.
The post details a number of different attributes of the tree and how to interact with it. It starts simple and shows how to get a tree reference and gradually gets more and more detailed, including how to search the tree and how to handle when a node is selected or even double clicked.
There's a working demonstration that goes with the post here: http://apex.oracle.com/pls/apex/f?p=54687:LOGIN
Many of the techniques and tips here have been invaluable to me in recent days as I work on a new project that heavily involves using trees. Thanks, Tom!
But the big news is spelled out right on the home page:
The Oracle Technology Network (OTN) Application Express Developer Challenge Oracle Open World 2013 is designed to highlight how quick and easy it is to build a "mobile" solution using Oracle Application Express.
Prizes include Amazon Gift Cards for first, second, and third. Participants will be required to build mobile pages (an application) utilizing Oracle Application Express in a free hosted development environment, http://apex.oracle.com.
When entering the challenge participants must provide a workspace on http://apex.oracle.com. At the completion of the challenge period, the participants will be locked out of the workspace specified.Registration and details for the challenge won't be available until Monday, September 23rd at 3PM PDT, so be sure to check back then!
Fast forward a year and change later, and finally, I'm happy to announce that Expert Oracle Application Express Security is now available for purchase (well, it has been for a while, and I'm just now getting around to posting this). The book really did not take an entire year to write, but there were a couple of challenges that were thrown in along the way. First of all, that night, we sat down with Enkitec and began discussion the acquisition plans. So that was a bit of a distraction. Also, I knew that at the time, APEX 4.2 was near release, and I wanted to ensure that I covered that release, so I had to actually write some of the later chapters first, and then circle back and complete the first ones last, since they contained more APEX 4.2-specific elements. Throw in the daily trials and tribulations of two kids and their hectic schedules and eventually a new job with new responsibilities, and all that added up to why it took longer than many of us wanted.
But enough about the excuses, and more about the book! The book contains 14 chapters, which range in topic from assessing a threat to preventing SQL injection to securing data at the database level. I've summarized each chapter below:
Chapter 1 begins with a discussion of how to identify and assess threats to your applications. It uses home security as an analogy when discussing this, since everyone already understands how to secure their home and has likely already taken steps to do so. It then categorizes all threats into two categories: preventable and unpreventable, and briefly discusses examples of each Chapter 2 covers what a security plan is and how to implement one for your organization. The main objective when creating such a plan is to first properly assess what the threats are, as specified in the previous chapter. The security plan is an ever-changing document that has to adjust as threats do, and should be reviewed often. Chapter 3 provides an overview of the APEX architecture from a security perspective. It starts by reviewing the Administration Console and how to configure Workspaces. It then covers a bit of APEX architecture, as well as touches on the different options for the web listener tier. Chapter 4 outlines all of the Instance Settings that pertain to security, and what the implications of setting them improperly are. Chapter 5 does the same as the previous chapter, but does so at the Workspace level. Chapter 6 covers setting within an application that pertain to security. It discusses them at the application, page and component level, as well as provides some advice when building mobile applications. Chapter 7 outlines the three main threats to an APEX application: SQL Injection, Cross Site Scripting and URL Tampering. It illustrates example of each, as well as shows how to protect against them. Chapter 8 covers how User Authentication schemes work and how they can be better secured. It also discusses the pros and cons of each type of scheme, as well as some commonly used APIs. Chapter 9 talks about Authorization Schemes and how they can be used throughout an application for access control purposes. It also briefly covers the Access Control feature of APEX. Chapter 10 provides an alternate, more secure way to download CSV files from an APEX report. It provides step-by-step instructions to implement this solution in your applications. Chapter 11 outlines a technique called Secure Views. Secure Views can be used in conjunction with a database context to provide a more secure way to display your data at no additional cost, if you are not using the Enterprise Edition of the database. Chapter 12 is similar to the previous one, but it uses Virtual Private Database, which is a feature of the Enterprise Edition of the database. Chapter 13 illustrates a concept called Shadow Schema. By using a limited privilege schema as your parse-as schema in an APEX application, you greatly increase the security of that application using this technique. Chapter 14 concludes with some examples of how using encryption in your application can increase the security of your data.You can get the book online from Amazon here: http://www.amazon.com/Expert-Application-Express-Security-Experts/dp/1430247312/ Alternatively, if you'll be at OOW this year, we will be giving away copies at our booth in the exhibit hall.
By far, the most anticipated feature is the new page layout UI. This interface is designed to do two things: make arranging regions and items easier, and allowing for batch updating of common item attributes. While the demonstrations were a bit rough and the UI is clearly not finished, this direction represents a lot of promise for APEX developers, as it is the one area that APEX has been lacking since day one.
Speaking of interfaces, there will be a new User Interface - Tablet - added to all applications. This will help bridge the gap between Desktop and Phone-based browsers, should a developer feel the need to do so.
One of the smaller yet more impressive features was the ability to add CSS/JS files as a ZIP files. The APEX listener will automatically unzip those files and even cooler - preserve the paths. This way, you can easily upload a set of related JS files and ensure that they will still function as intended. It also has a cool way of versioning these files. The URL that is uses for them will have a path like this: /v212/ As these files are modified and/or re-uploaded, the version will change, ensuring that the files do not become cached on user's devices.
While we didn't see it, the new tabular forms replacement - called Multi-Row Edit Region - seems promising. Also, the ability to add multiple IRs to a single page will also become reality. IRs are getting a little bit of a makeover, with modal dialogs replacing the traditional menu and the ability to freeze columns are added.
Another feature that has been long anticipated will be the ability to authenticate to the Application Builder et. all with a custom authentication scheme. This feature probably has more political impact than technical, since it allows APEX developers to be a part of an organization's identity management infrastructure. It will also make it a heck of a lot easier to remember your credentials for any workspace, since they can all be the same.
Speaking of security, it looks like there is some planned integration with Oracle Real Application Security, or RAS. RAS is a no-cost feature of the enterprise edition of the database, and is very similar to VPD. With it, you can define roles, users and privileges that can be used with any technology. Not too many more details were available about this, but it also seems promising.
Autocomplete in PL/SQL regions (or at least Application Processes! :) ) is also a part of APEX 5. When typing in code, you can hit control+space and autocomplete things like item names, APEX APIs, and database objects. To compliment this, a new code editor - very similar to that included with ApexLib - is baked into APEX 5.
Overall, it looks like there's a lot of interesting features to come in APEX 5. While there's definitely a lot of work to be done, each time I see it, more and more of the features are working better and better. It will be interesting to see how much progress can be made between now and OpenWorld.
In any case, if you're going to be at OpenWorld and use APEX, be sure to stop by and see the ODTUG APEX Symposium. This year, we're going to focus on printing with APEX. We have four different solutions lined up: PL/PDF, BI Publisher, Jasper Reports and the APEX Listener w/FOP. Each presenter will be discussing the benefits of each solution from a cost, ease of use, integration and security perspective. This will give the attendees an objective review of these printing solutions. We'll conclude with a panel discussion summarizing all of the solutions together.
Here's the session details so that you can add it to your OpenWorld agendas:
- Printing Options for Oracle Application Express: Oracle Business Intelligence Publisher [UGF10238] Sunday, Sep 22, 9:15 AM - 10:15 AM - Moscone West - 2005
- Printing Options for Oracle Application Express: Jasper Reports [UGF10240] Sunday, Sep 22, 10:30 AM - 11:30 AM - Moscone West - 2005
- Printing Options for Oracle Application Express: FOP and Oracle Application Express Listeners [UGF10239] Sunday, Sep 22, 11:45 AM - 12:45 PM - Moscone West - 2005
- Printing Options for Oracle Application Express: PL/PDF [UGF10237] Sunday, Sep 22, 2:15 PM - 3:15 PM - Moscone West - 2005
- Printing Options for Oracle Application Express: Q&A Panel [UGF10241] Sunday, Sep 22, 3:30 PM - 4:30 PM - Moscone West - 2005