Skip to main content

Engage!

One month in at Oracle, and I’ve been moving at what feels like warp speed – both literally and figuratively.  My team has been hard at work building the intake survey and that will solicit volunteers for the Phase 3 efficacy trials.  We’re also building all of the backend applications that will be used run analytics to select qualified participants and assign them to a local clinic to receive the actual vaccine.  This project is actually a part of the US Government’s Operation Warp Speed program – a program whose goal is to deliver 300 million doses of a safe and effective vaccine by January 2021.  

It should come as no surprise that we’re building 100% of this solution with Oracle’s low code platform, Oracle APEX.  Oracle APEX was the natural choice here, given the rapidly changing requirements, the need for a 100% responsive and custom UI, and the ability to deliver something substantial in just a couple of weeks.  The entire infrastructure – and it’s a lot more than just APEX & ORDS – all runs on the Oracle Cloud.

This is just one of four active projects that we have going on.  And thus the reason for this post – we’re growing.  Fast.  Each of the four current projects have multiple phases, many of which have yet to even start.  And there’s a bunch of new and exciting work on the not-too-distant horizon as we continue to reach out and assist those in need during this global pandemic.  Pandemic systems is also just the beginning.  Look for more exciting announcements about what we’re up to as we can share them.

We’re already well on our way putting together a world-class team to work on these projects.  You may have already seen Tweets from Doug Gault and Dan Mcghan about their roles on this new team.  These are just two of the several new team members that we’ve already recruited for this team.  

Despite this star-studded cast, we still need more help.  This is where you come in.  If you’re a seasoned APEX developer looking for a chance to make an actual difference in the world, we should talk.  We have a number of open slots that we need filled ASAP.  Know any good DevOps, Infrastructure or even DBA-type folks?  We’ll need them, too.

Interested in learning more or applying?  Drop me a note, hit me up on Twitter or hop on over here to fill out an application to get things started.

Comments

Post a Comment

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma
76 comments
Read more

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem
5 comments
Read more

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p
1 comment
Read more