Maximo Manage v8 Administration
Domain: Maximo Manage v8 Administration
This domain tests day-to-day configuration and control of a Maximo Manage v8 environment running inside IBM Maximo Application Suite: how records, fields, and security are defined, how background processes fire, and how configuration changes are promoted safely. Because v8 places a suite layer above the classic Maximo applications, many questions probe which layer owns a given administrative task.
The two administration layers
In MAS, user accounts, application entitlement, and suite-level access are managed in the suite administration tools and synchronized into Maximo. Maximo's own Users, Security Groups, and Application Designer then decide what a person sees and can do inside a record. A frequent discriminator: the account originates at suite level, while Maximo authorizations come from security group membership plus application authorizations and signature options.
Core objects to know
- Database Configuration - defines objects, attributes, relationships, and indexes. Structural changes need admin mode and "Apply Configuration Changes", which generates and applies scripts rather than mutating the live schema on save.
- Domains - ALN, NUMERIC, TABLE, SYNONYM, and CROSSOVER (used to filter a lookup by a related field's value).
- Application Designer - signatures, controls, and Configure Conditional Properties (required, read-only, hidden) driven by expressions such as
:status = 'APPR'. - Cron Tasks and Escalations - cron task instances schedule background work; escalations are evaluated by the ESCALATION cron task using point-based or schedule-based conditions.
Worked example
A work order must allow the failure code to be edited only while work is in progress. Open Application Designer for WOTRACK, select the failurecode control, open Configure Conditional Properties, and make it Read Only with the expression :status = 'INPRG'. Then verify the security group's application authorizations: a user without the relevant signature option access never reaches the field, so the conditional expression appears to have no effect at all. Check both layers before concluding the expression is wrong.
Traps that cost marks
Deleting a domain still referenced by an attribute leaves a broken lookup; editing database configuration without admin mode prevents apply; and a cron task whose instance is inactive never runs, no matter how the schedule is set.