357 Lotus blogs updated hourly. Who will post next? Home | Downloads | Events | Pods | Blogs | Search | myPL | About 
 
Latest 7 Posts
Warriors of Light
Sun, Jul 20th 2014 140
Adventures with vert.x, 64Bit and the IBM Notes client
Thu, Jul 17th 2014 134
Cycle where?
Sun, Jul 13th 2014 163
From XML to JSON and back
Fri, Jul 11th 2014 234
The folly of root cause analysis
Wed, Jul 9th 2014 172
Documents vs eMails
Fri, Jul 4th 2014 318
The taxi loyalty program isn't working and how to fix it
Mon, Jun 16th 2014 187
Top 10
Domino Development - Back to Basics - Part 5: Finding data - Collections and Search
Thu, Jan 2nd 2014 934
Let's ditch IBM Notes and Domino
Thu, May 29th 2014 671
Domino Development - Back to Basics - Part 7: Map Reduce Domino Style
Wed, Feb 12th 2014 502
Download Connect 2014 presentation files
Tue, Feb 4th 2014 473
Numbers are numbers, you have to see it! - Selenium edition
Sat, Feb 15th 2014 468
What is your investment in Notes applications - revisited
Tue, Feb 25th 2014 458
MongoDB to switch to IBM storage backend
Tue, Apr 1st 2014 452
CRM > Sales Tracking
Sun, May 5th 2013 450
Domino Development - Back to Basics - Part 6: Better save than sorry - Security
Tue, Feb 4th 2014 443
You want to move to Domino? You need a plan!
Thu, Apr 17th 2014 428


Extracting data from Domino into PDF using XSLT and XSL:FO (Part 1)
Stephan H Wissel    

We all know "Notes doesn't print". Nevertheless the topic of document output and reports is not going away, even if I'd like to ban the reports. There are plenty of ready made tools, but today I'd like to start with home cooked reporting.
Why the effort? Using only tools that use open standards you gain more control over the whole process and you can use whatever deems fit. The downside: it is more things you need to know and might not be suitable for business users (but its great to torture interns). In the long run you have a portfolio of source transformations that you can combine potentially faster than any reporting tool. The general principle is "Extract Transform Render":
Extract Transform Render
  1. Extract:
    Whatever will pull out the XML for the second step will do the trick. For list type of rendering ?ReadViewEntries will do the trick or simple DXL exports. Quite often you might opt for some bespoke code to extract code with an eye of a fast and/or easy transformation phase. You also might consider to extract your data in conformance with an established international standard
  2. Transform:
    This step usually takes the XML from the extract phase and runs it through one or more XSLT transformations. XSLT is kind of IT Black Magic (other say it's just set theory) and can use quite some computing power. For high performance the pros use a dedicated applicance. Once you get the heck of XPath you can do some amazing reporting (e.g. "give me all sales guys where withing the last 5 sales of the 3 guys next to his ranking there was a carpenter")
  3. Render:
    Rendering is easy. The outcome of the transformation step will be XSL:FO which is a page description language. Use a free renderer or a commercial offering and a few lines of code. The output typically is a PDF file, but you can target graphic formats too.


---------------------
http://feedproxy.google.com/~r/Wisselnet/~3/48VBtr_nHl8/SHWL-8TMM9D
Apr 23, 2012
119 hits



Recent Blog Posts
140


Warriors of Light
Sun, Jul 20th 2014 11:15a   Stephan H Wissel
Inspired by Paulo Coelho's manual for the Warrior of the Light: Warriors of Light We were born from the stars Descended from the heavens Armed with compassion Determined to end the suffering Subjected to the human condition Battling ignorance with wisdom Laying our lives for the liberation from illusion When you look in the mirror - remember! You are one of us. [read] Keywords:
134


Adventures with vert.x, 64Bit and the IBM Notes client
Thu, Jul 17th 2014 8:12a   Stephan H Wissel
The rising star of web servers currently is node.js, not at least due to the cambrian explosion in available packages with a clever package management system and the fact that "Any application that can be written in JavaScript, will eventually be written in JavaScript" (according to Jeff Atwood). When talking to IBM Domino or IBM Connections node.js allows for very elegant solutions using the REST APIs. However when talking to a IBM Notes client, it can't do much since an external program ne [read] Keywords: connections domino ibm lotus notes notes client application development eclipse google java javascript oracle python wiki ubuntu
163


Cycle where?
Sun, Jul 13th 2014 1:12p   Stephan H Wissel
I like to cycle, I do that often and from time to time I have fun with traffic participants. One of the interesting challenges are multi-lane crossings (note to my overseas readers: Singapore follows the British system of driving on the left, so cyclists are supposed to cycle on the left edge of the road - which makes me edgy in some situations. So for right driving countries, just flip the pictures) where the outer lane allows more than one direction. Like these: Road rules do require the [read] Keywords: google wiki
234


From XML to JSON and back
Fri, Jul 11th 2014 8:12p   Stephan H Wissel
In the beginning there was csv and the world of application neutral (almost) human readable data formats was good. Then unrest grew and the demand for more structure and contextual information grew. This gave birth to SGML (1986), adopted only by a few initiated. Only more than a decade later (1998) SGML's offspring XML took centre stage. With broad support for schemas, transformation and tooling the de facto standard for application neutral (almost) human readable data formats was established [read] Keywords: application java javascript server wiki xml xslt
172


The folly of root cause analysis
Wed, Jul 9th 2014 6:12a   Stephan H Wissel
IT support's dealing with management is a funny business. Whenever something goes wrong, support teams engage in "defensive blaming" and the elusive quest for a root cause. I've seen this quest (and blaming god and country along the way if it doesn't appear) taking priority over problem resolution and prevention. The twisted thought is: "If I'm not sure about the (single) root cause, I can't neither fix nor prevent it from happening again". Why is that a folly? It paralyses: If a pe [read] Keywords: application database google wiki
318


Documents vs eMails
Fri, Jul 4th 2014 6:14a   Stephan H Wissel
With a public sector customer I had an interesting discussion on non-repudiation, messaging and regulatory control. We were discussing how to ensure awareness of information that has behavioural or legal consequences. While "I didn't know" is hardly a viable defence, relying on the other party to keep themselves updated is just asking for trouble. In a collaborative environment, where a regulator sees itself primarily as the facilitator of orderly conduct and only as policing the conduct as s [read] Keywords: domino database email microsoft server wiki xml




187


The taxi loyalty program isn't working and how to fix it
Mon, Jun 16th 2014 10:11a   Stephan H Wissel
Singapore is a little like New York: train and taxis are a mainstay of the daily commute. So the taxi market is highly regulated and fiercely competitive. As no surprise taxi companies try to bind customers before they loyalty switches to alternative bookings or the disruptors. So Comfort & CityCab started CabRewards. After all loyalty cards work well for their inventor. In a smart move, instead of creating a new piece of plastic, Comfort teamed up with ezLink Singapore's leading provider [read] Keywords: admin administration application mobile wiki
671


Let's ditch IBM Notes and Domino
Thu, May 29th 2014 7:11p   Stephan H Wissel
Finally you decided it is time to move on, legacy no longer means "tried and tested" but "we need to move one" to you. After all you never really liked Cher. Notes data is available via LotusScript, dotNet (through the COM bridge), in Java, Corba, C++, XML, REST, MIME, so how hard can it be? Actually not very hard, you just need to: Find sutiable replacement application platform(s) Rewrite the applications (don't dream: there is no such thing as "migrate an app") Migrate your users Migr [read] Keywords: domino ibm lei lotusscript notes richtext xpages application applications community database db2 enterprise google integration java linux mobile server wiki xml
250


Value, Features and Workflows
Mon, May 12th 2014 6:11a   Stephan H Wissel
In sales school we are taught to sell value. Initially that approach was designed to defang the threat of endless haggling over price, but it took an extra twist in the software industry. Since software companies rely on user's desire to "buy the next version" to secure revenue from maintenance and upgrade sales, a feature war was the consequence. As a result, buyers frequently request feature comparison tables, driving the proponents of "value & vision" up the wall. It also creates te [read] Keywords: ibm notes application archive email outlook server wiki
428


You want to move to Domino? You need a plan!
Thu, Apr 17th 2014 6:12a   Stephan H Wissel
Cloud services are all en vogue, the hot kid on the block and irressitible. So you decided to move there, but you decided your luggage has to come along. And suddenly your realize, that flipping a switch won't do the trick. Now you need to listen to the expert. The good folks at Amazon have compiled a table that gives you some idea how much it would take to transfer data: Available Internet Connection Theoretical Min. Number of Days to Transfer 1TB at 80% Network Utilization T1 [read] Keywords: domino ibm xpages database java microsoft network office wiki




Created and Maintained by Yancy Lent - About - Blog Submission - Suggestions - Change Log - Blog Widget - Advertising - Mobile Edition