I've continued to experiment with the use of Maximo BIRT's hidden parameter. In my previous post I was able to display values that were generated by related information of the Maximo user who ran the report. But the original data selection used the hidden username
parameter in the SQL where …
Extending the use of Maximo's hidden BIRT parameter
One of the common queries used by Maximo power users is:
siteid = (select defsite from maxusers where userid = :user)
This selection limits records to the default site the current Maximo user is checked into. So if a query is saved for future use, it will work with any site a …
Conditionally make 'Memo' a requirement
I will always admit I get inspiration on how I administer my company's Maximo environment from other sources. The most recent update I've made to our Maximo environment was based on a something I've had on the back burner, but got a virtual nudge from Steven Shull (@shullsa) after reading …
Flexible date ranges in Maximo BIRT reports
For a long time I've always promoted the idea that a report should have flexibility with date ranges. Either the report should allow a user to select a date range or include rolling date ranges. To match this philosophy, we have have several reports that include rolling date range, but …
Incorporating Location Hierarchy on WO Print
My company has recently been challenged with how we're using Maximo. On one front we're deploying Maximo to new sites that are transitioning off of another EAM platform. On the other front we have a facility that's tripling the size of the installed asset count. Both sites are dealing with …