Skip to main content

PL/PDF 2.0

It appears that the folks over at PL/PDF have released version 2.0 of PL/PDF.  According to their documentation, this is the list of new features for 2.0:

 - SetDocDisplayMode: doc extended
- native PNG support (PrintImageCell, PutImage p_type)
- use without InterMedia
- PrintFlowingTextLimit: bad charter handling fixed
- PrintMultiLineCell: bad charter handling fixed
- compress: LZW without Java
- SetCompress: new parameter: p_method
- plpdf_const package: new entries
- PutImage: new parameter: p_type
- PrintImageCell: new parameter: p_type

Check out PL/PDF, as it is an excellent way to generate PDF files from the Oracle Database without requiring any middle tier hardware/software, as it's mostly PL/SQL.

Comments

Stew said…
FYI - The latest version is 2.1. Their website says it adds the following features:

* XHTML to PDF converter package - supports most XHTML tags
* TTF (True Type Font) loader GUI - to replace the manual loading of True Type Fonts
* Doc-XML - document your PL/SQL packages by putting XML tags in the package headers. With Doc-XML the XML tags are converted to a PDF document.

From my limited experience with it (3 reports, including 1 complex form), you can create a simple report pretty quickly. But be prepared to spend a lot of time creating complex reports (i.e. text wrapping, drawing graphics boxes, shading, positioning). I found some of the documentation to be concise to the point of useless.

The tool does the job for much less than Oracle Business Intelligence would (though that obviously does more), but it can take a lot of time to create sophisticated reports.
Scott said…
Stew,

Thanks for the update.

The new PDF template feature is really nice if you need to have some fixed background formatting. You can use any tool you like, save it as a PDF, and then render that PDF as a background for your documents. Has saved me a tremendous amount of time!

- Scott -
Stew said…
Scott,

Happy to add to your content. I wish I'd known to use the template feature when used V1.7 this past winter. By the time I realized it was available, I'd already invested many hours, so felt like it couldn't take that much longer to hand-code it. Wrong! :-(

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