How to restrict allowed status changes for workorders

Maximo has a predefined set of statuses for work orders that are defined in the WOSTATUS synonym domain. The values and their meaning are well documented in the official documentation. Unfortunately the allowed state transitions are hardcoded in the class and cannot be easily changed since they are defined as private arrays. Here is a brief […]

Maximo search operators

Maximo search features are quite advanced but often neglected. By using the advanced search techniques described in this post it is possible to find relevant records easier and faster. Equal The equal ‘=’ operator can be used to find only records that match that a word or number exactly. In other words ‘=’ means “exact […]

Find inactive users in Maximo

Here is a quick SQL query you can use to find inactive users that haven’t logged into Maximo in the last 2 months. DB2 select * from maxuserwhere status=’ACTIVE’and sysuser=0and not exists (select userid from logintracking where logintracking.userid=maxuser.userid and attemptresult=’LOGIN’ and attemptdate>(current date-60 DAYS))order by userid; Oracle select * from maxuserwhere status=’ACTIVE’and sysuser=0and not exists […]

Long Descriptions in Maximo

Long descriptions in Maximo are a special fields meant to store long text. Unlike all the other fields they are stored in a dedicated table called LONGDESCRIPTION. Tables link to the LONGDESCRIPTION table through their unique ID and the long description attribute is stored in a CLOB field. Let’s change the long description of the work […]

Scroll to top