How do I run a Maximo automation script from an escalation, a workflow or a button?

Create a script with an action launch point. Saving it creates a record in Actions. You then connect that action to the escalation, workflow or button that should run it.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same wizard, action type, “Accessible From” values and applications 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 says: “Though this task creates the action, you must attach that action to the escalation, workflow or the user interface button or menu.”

Last checked: 17 November 2026

How it works

An action launch point never runs by itself. When you save it, Maximo creates an action. A caller runs the action, and the action runs the script.

ItemWhat we saw in the lab
The action Maximo createsIts name is the Action field of the launch point (by default the launch point name). Type CUSTOM. The Value and Parameter fields hold the class and names that find your script.
Accessible FromALL by default. You can limit it to ESCALATION or WORKFLOW.
ObjectOptional. With no object, the action has no object either.
One script, two action launch pointsWorks. The variables launchPoint and action tell the script which one ran.
Variables the script getsmbo, mboname, action, launchPoint, scriptName, user, service, app, interactive, onadd, onupdate, ondelete. No wfinstance unless a workflow calls it.
Who saves the recordThe caller. The script only changes mbo. A call with no save left the record unchanged.
CallerHow to connect the action
EscalationEscalations > Escalation Points tab > Actions: add the action. Use the same object as the escalation.
WorkflowWorkflow Designer: put the action on an action node or a connection line. Then validate, enable and activate the process.
Button or menu itemApplication Designer: add a signature option with the same name as the action, add the button or menu item, then grant the option in Security Groups (listed as “Security Groups (Manage)” on Maximo Application Suite 9.1).

What we observed in our lab: deleting the launch point leaves the action behind, and that orphan action then fails with a NullPointerException when it runs. Also, do not treat the launch point’s object as a check on the record: if the script must only run for one object, test mboname in the script.

Steps

  1. Open Automation Scripts. In the action menu choose Create > Script with Action Launch Point.
  2. Step 1 of 3: enter the launch point, the action name, the object (optional) and Active. Choose a new or existing script. Click Next.
  3. Step 2 of 3: script name, language and log level. Add variables only if you need bound values. With no object you cannot bind to attributes. Click Next.
  4. Step 3 of 3: enter the source and click Create.
  5. Open Actions and find the new action. Do not change Value or Parameter. Set Accessible From if you want to limit the callers.
  6. Connect the action to its caller (table above).
  7. Test with a caller that selects only one test record.

Where it breaks

How we checked it

On a Maximo 7.6.1.0 lab system we made a test script with two action launch points (one with an object, one without) and read the action records Maximo created. A second test script ran each action on our own test work order and recorded the variables the script received. We also read the wizard’s labels from the application definition. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.

Not tested here: a real workflow call (and wfinstance) and the button path. On Maximo Application Suite 9.1 we only read the configuration; we did not create a script or an action 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.