Last Updated on November 19, 2022 by maximosecrets
The Work View application is the place where all the classes of tickets and work orders come together. It is an application that exists in the Administration module, but the WORKVIEW object is exposed in a couple of places across Maximo, and it has an unusual feature which we will come to.
The original purpose of the Work View was to provide a place where you could find all the tickets and work orders where you are the owner or a member of the owner group. The application wasn’t intended for a mass of users, it is in the Administration module, it was intended that users get access to see the Work View through Result Set Portlets on their Start Center and then they navigate from there to the relevant application. The Work View can show on the Start Center both Service Requests and Work Orders in a single list.
The administrator uses the Work View application to build a public query and save it so that it can be used on Start Centers. There are two public queries ‘Work View (Sorted by Priority)’ shows the logged in user’s open tickets and work orders, and the ‘Owner is login user’ shows the same records but also includes the resolved tickets and completed work orders. Neither shows records in history or work order tasks.
Whenever you create a new ticket or work order including tasks it is copied to the WORKVIEW table. Whenever you update those records or change status the WORKVIEW record is updated. Maximo keeps the data synchronised, including for deleted records.
The WORKVIEW object has a limited set of fields the Reported By and Affected By Person and Names, the Owner, Owner Group and the Assigned Owner Group, the Record Class, Key field, and Description, Reported Date and Target Start Date, Status, Priority, PM Group, Org and A structural element of a Maximo database that is used for data separation. More Identifiers.
You might have noticed that there is no A physical place where assets exist and where work can be performed. or asset fields, but it is possible to add them through configuration. There are two non-persistent fields TICKETID and WONUM on which you would need to add a Crossover Domain to copy from the originating record into the WORKVIEW object. The unusual feature is that these two fields are updated by Maximo in a way that causes the Crossover Domain to fire again. Normally Crossover Domains work on insert, and not on update, and on persistent fields and not non-persistent fields. In the Links section at the bottom of the transcript page there is an article where I show you how this can be achieved.
The number of records in the WORKVIEW table should be the sum of the number of records in the TICKET and WORKORDER tables. You may think that this would perform poorly in comparison to queries on one or the other tables, not so. In tests I performed over a two-month period on a system with more than 20 million records, queries on the WORKVIEW table performed on average greater than 400% faster. Some result set portlets which took 2 minutes to open, were now opening in 20 seconds with the same results.
The Work View object is used by Maximo in a couple of places. The most likely place where you will see it is in the Locations and Assets application and the View Work Details action. But it also exists in the dialog for the ‘Select From WO Hierarchies and Relationships’ button below the Multiple Assets, Locations and CIs table window in the Work Order Tracking application.