Assetize

The Maximo screen reference IBM stopped publishing

IBM last published a complete Maximo screen reference in 2008. The product still knows every control and property; nobody had read it back out until now.

The old guides are seventeen years stale and the MAS docs have no control reference at all — while the interface itself changed under Carbon, one release at a time, documented only in blog posts.

The reference IBM stopped publishing

The Maximo Manage documentation for MAS 8.x and 9.x carries ten task topics as HTML, with no controls reference, no attribute reference, and nothing about what the Carbon interface changed for a screen you had already customised. The old SaaS "Control properties" topic returns 404.

The product itself never lost the reference. Application Designer edits every control through a property sheet backed by a CTRL_* object in the data dictionary, and every stock screen is a row in MAXPRESENTATION. Read those back from a running instance, check them against MAS 9.2, and the reference writes itself.

Every control, every property, from the product itself

The reference lists every control by family — containers, data controls, actions, display, navigation, data sources, framework tags — with the properties its CTRL_* object declares (type, length, required, Designer label, domain values), which Designer tab each sits on, how often the 204 stock screens use it and with which values, and a real opening tag as an example.

Attributes the stock screens write that the property sheet does not show are listed too, marked XML only. Lookup ids come from lookups.xml, common signature options from the SIGOPTION inventory. Everything is labelled lab-verified with the object or screen it came from.

What changed under Carbon

MAS 9.0 moved labels above fields, rendered YORN attributes as toggles and moved table buttons above the table. 9.1 returned toggles to checkboxes, unified the left navigation and renamed the masthead class from .bx--header to .cds--header. 9.2 continues Carbon with layout controlled by mxe.webclient.* system properties.

Application Designer, the presentation XML and export/import are the same across 7.6 and MAS 9.x: a 7.6 presentation imports unchanged and renders in the new skin. The versions page lists every change with its source class.

A playground that runs the stock screens

The playground parses the XML in the browser, draws the screen schematically under the skin you choose, and resolves every dataattribute — through datasrc references, dotted relationships and the 7,166 relationships — against the MAS 9.2 data dictionary read from a running instance (9.1 too, if that is what you run): real titles as default labels, the attribute type deciding the widget, a typo flagged with the nearest real name.

Click any control for its reference card and the lab facts of its attribute; fill the screen with real 9.2 work orders; apply a trick with one click and read the diff against the stock screen. The whole state lives compressed in the link. Nothing is uploaded.

Tricks you never had to code

Every trick is a change to the presentation XML that IBM's own screens already make: a relationship-dotted dataattribute, a signature option on a control, a rechover naming a hover window, a defaultvalue under the data source, an include from library.xml, a pushbutton whose event opens a dialog. No Java, no automation script.

Each one cites the stock screen and the registry property it rests on, and names what to verify on your instance.

Sources

More field guides