Exslt–Stale by 9 Years

No XMLPart of the exslt specifications include defining name spaces for their xslt extensions.  I find it fairly amazing that most of the namespace definition pages (for example http://exslt.org/strings and http://exslt.org/dates-and-times) are still undefined.  It’s somewhat deceptive, because when you are trying to implement a portion of the library incorrectly, the error message that the MSXML parser will typically say that their are no function definitions at http://exslt.org/dates-and-times. What the error actually means is that the function you are trying to use does not exist in the library you are importing.

February 22, 2010 • Tags: , , , , • Posted in: Technology • No Comments

Facebook Your Portal: Chronological Content vs. Pagelet Content

Recently I gave a presentation for the HEUG Alliance conference.  Since the HEUG website is fairly closed doors, I thought I would post the description, and my power point presentation here.

Description

This presentation will examine MICA’s switch to a portal based on events triggered by changes to a person’s Enrollment, Finance, and HR records. These events are then listed chronologically and contain links to direct calls to action.

This approach is more commonly seen on blog posts and social networking sites, but not portals which rely heavily on spatially sorted pagelet based content. This is a better organizational model since end-users are more interested in current events than the second pagelet to the right. Direct calls to action allow easier navigation to the PeopleSoft components that people are then interested in.

This concept was implemented with the use of the RSS standard, so that feeds from Campus Solutions, and Human Resources could be threaded and sorted together with other news sources on campus.

PowerPoint

eText, and XSL Templates for XML Publisher do not work in PeopleTools 8.49

This title really says the most important part.  The rest of this is a rant–I have no work around for making this work at the moment.

Back in May Human Resources aproached me, asking for help developing a flat file for uploading our retirement data with TIA/Cref.  Since I have taken this job as an Information Systems Developer, newly exposed to Oracle and PeopleSoft to a level I had not previously been exposed I have heard about this XML Publisher thing.  It’s supposed to replace crystal reports, which are old and gross (yet, seem to work).  Being a web dude, I love XML.  I’m all about it.  So clearly, me and XML Publisher seem like a match.

XML Publisher supports 4 template formats.  These are: Rich Text Format (RTF), eText Format (also RTF), PDF (Built using word in the RTF format), and miraculously enough Extensible Stylesheet Language Transformations (XSLT).  Personally, I was quite pleased that Oracle had embraced a web standard created by the World Wide Web Consortium.  As a bonus, I had used this technology previously, and while wordy, I had found it excellent for translating XML.

I tried creating a simple XSL Template.  Unfortunately, it did not work.  It was at this time that I created my first support ticket with Oracle.  Now, nearly 3 months later, my first support ticket is still open.

They told me that they didn’t really support, or have example XSL documents I could use.  I switched between XSLT to eText because, supposedly, eText worked and was supposed to do exactly this kind of thing.  It was also broken.

One thing that is cool about this is I think I was their first client that ever tried to use the XSL Template option.  That makes me a trail blazer, in a defunct kind of way.