Skip to main content

Lots of New Stuff

The last few weeks have been quite hectic indeed!

In addition to my day job, I've been busy working with Doug Gault - Sumner's newest member - in re-structuring a number of our services and training classes.  I'm also happy to announce a couple of new products that we will be launching soon.

SumnerPrint is a PL/SQL-based solution that allows you to easily print APEX reports to PDF, HTML and XLS.  Built on top of PL/PDF, SumnerPrint easily integrates into any APEX application and allows your end users to print high fidelity reports with the click of the mouse.  Since it's built on PL/PDF, there is no middle tier to configure or extra servers to purchase.  You can be up and running with it in just a few minutes!

SumnerFramework is a set of APEX applications and tables that allow you to manage who has access to which APEX application.  It also provides a single point of management, so that you can centralize your role management for easier access and better reporting.

You'll be able to see demonstrations of both of these offerings at ODTUG next week.  If you can't make it, drop us a note and we can arrange for a private demonstration.

We've also launched a new corporate blog here:  http://feeds2.feedburner.com/SumnertechBlog

While I will still occasionally still update this one, most of the APEX-related content will be posted on the new blog.  So be sure to bookmark both of them!

Comments

Olivier Dupont said…
Hey Scott,

This sounds very interesting. Is it possible to get some screenshots from your product?

There will also be a session on ODTUG about alternative PDF printing.

I'm curious about both products as it's always a difficult choice to find a decent affordable print solution.

Regards,
Oli
Scott said…
Oliver,

We'll be posting some screen-cams in the future. There's really nothing to "see", as it's just a JavaScript call and Application Process that you can add to any application. It functions just like the BI Publisher integration.

The difference between SumnerPrint and JasperReports is that SumnerPrint requires no Java or extra server components. It's 100% PL/SQL, and installs in the same server as your database.

Also, JasperReports has a lot of functionality that SumnerPrint currently does not, such as a layout editor. SumnerPrint currently solves the problem of easily, cheaply and quickly getting a dataset into a PDF (or HTML or XLS) document so that it can be shared with others who do not have access to the system. Again, two more tools for two different needs.

Thanks,

- Scott -

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

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

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