skip to Main Content

Changing Font Size in Maximo for Long Description and Log Defaults

📚 Changing Maximo’s long Description and log default font sizes (For All Apps) 📚

If you’re like me, you might not have the greatest eyesight in the world. Logs and long descriptions in Maximo are a very useful way to let your co-workers know:

  1. what’s going on with a particular Work Order
  2. Asset, Purchase Order, Item or any of the various applications that would need more description, or a log put onto it.

IBM defaults the size for the long descriptions and Logs to xx-small type. It’s great for fitting a lot more on a little page. However, it’s very hard to read and for the majority of the world’s population, we need glasses to do so.

 

How do we go about making the font size larger?

Open the long description or log. From the middle drop-down column (size) you can choose your font size.

The catch…

You must go into system properties and make a change to the global property (webcient.richtext.blocknode.)

If you do not take the step above, each carriage return (geek speak for hitting enter) makes the font size small again. Every subsequent log or description that you edit will also need to be changed when you open it to edit.

Is there a way to just have the font size bigger than xx-small when you open any new or old log or long description?

The answer is yes, but you’ll have to roll your sleeves up and do a little bit of work to make it so.

Font sizes in Maximo’s Long Descriptions and Logs revolve around the rich text editor. The rich text editor does not allow for sizing fonts easily. With some determination, you can get those fonts changed into something you won’t have to strain your eyes to read. If you want to make those long descriptions and logs readable then you’re going to have to edit some CSS (cascading style sheets) files. CSS allows for bulk “styles” to re-occur across the website that they are applied to. Maximo is a web application, so this is where we start.

Here’s how…

Buried in the Maximo directories are files that make Maximo work. The ear file will be our focus, but there are others that also assist in Maximo’s functionality. On the application server (the machine that hosts Maximo), you will have a directory that gets installed that contains the CSS information to display Maximo. Navigate to [maximo-folder]\applications\maximo\maximouiweb\webmodule\webclient\css and search for the ‘extended.css’ file. Open it and add the following lines of code to the end of the page.

#dijitEditorBody {

Font-size: 20px

}

 

The second location of an extended.css file that needs to be edited is in the following path, [maximo-folder]\applications\maximo\maximouiweb\webmodule\webclient\skins\iot18\css.

For the latest versions of Maximo (7.6+), the iot18 folder is significant. The reason for this is other articles mention to add the edited extended.css file to a folder called tivoli09. To save time, understand that the Tivoli directories were made for older versions of Maximo like 7.5 and prior. If you are using a newer version of Maximo look for the iot18 directory. You will edit this extended.css file in the same manner as the last one by adding the lines below to the end of the css file:

#dijitEditorBody {

Font-size: 20px

}

Next, you will need to rebuild the ear file for Maximo and re-deploy it to your environment. The 20px setting will default the text to medium in the logs and Long Descriptions.

Originally there were some hesitations on using CSS to fix this problem. It was thought that the change could affect the reports and the way they looked when generated. We have not seen that happen after making the changes.

We want to hear your thoughts about our helpful guide. Please send us your inquiries to:

info@a3jgroup.com

Stay tuned for more helpful articles that will maximize your Maximo experience!

This Post Has One Comment

  1. Thanks for the information. I tried this, however, it still is set at xx-small. I modified both extended.css files, rebuilt/redeployed the ear files, and cleared cache but still nothing. Anything I might be missing? We are on 7.6.1.2.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top
×Close search
Search