Use an attribute launch point on the Initialize Access Restriction event. It works; our lab adds a few things to watch for.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same event, wizard and messages are present (17 November 2026). The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 November 2026); we have not re-run the behaviour test on Maximo Application Suite 9.1.
IBM’s page: IBM’s current Maximo Manage documentation lists the same event, “Initialize access restriction”, with the description “Sets the access level for the attribute’s field.”
Last checked: 17 November 2026
In the script, set one of three variables: thisvalue_readonly, thisvalue_required or thisvalue_hidden. Maximo runs the script once for each record, the first time something reads the field’s flags or writes the field.
| The script sets | What happened in the lab |
|---|---|
thisvalue_readonly = True | The field is read-only. A script setValue fails with BMXAA0019I. |
thisvalue_hidden = True | The field is hidden and read-only. A write fails with BMXAA0019I. |
thisvalue_required = True | Saving with the field empty fails with BMXAA4195E, but only if something read the field’s flags first. |
| The flag depends on another field, and that field changes | The script does not run again. The flag keeps its first result. |
What we observed in our lab: the script runs only once per record, so a flag that should follow another field goes stale. A second script on that other field keeps it right (step 3).
if mbo.getString("STATUS") == "APPR":
thisvalue_readonly = Truefrom psdi.mbo import MboConstants
mbo.setFieldFlag("FIELD1", MboConstants.READONLY, mbo.getString("FIELD2") == "LOCK")On a Maximo 7.6.1.0 lab system we added two launch points to spare fields on a work order, limited by a condition to our own test work orders. A test script read the field flags, tried writes, and saved or rolled back. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.
Not tested: how the flags look on the screen, and a user who is not an administrator. On Maximo Application Suite 9.1 we only read the configuration (the application, the event names and the messages); we did not create a script there.
This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.