Automation Script Quick Reference

Here are some of the quick reference guide for every maximo developer.

Before we begin with some example, you must be aware of automation script implicit variables. Please refer to this post for detailed explanation of the implicit variables. 

How to generate asset description from classification using automation script

To generate the description from classification, Generate Description (GENASSETDESC) and Use Classification (USECLASSINDESC) has to be checked.

Run automation script as cron task in Maximo 7.6+

You can use a script to run the cron task by using a Java Class com.ibm.tivoli.maximo.script.ScriptContask in the cron task definition and then attach the automation script to the cron task in parameters. For this script, we don't need a launch point.

Types of Automation Script

Below are the Scripts with events you can create in Maximo 7.6+

Automation Script Implicit Variables Explained

There are certain variables provided by the framework. These variables are not necessary to be declared before using. Some of these variables are valid only for specific launch point or a particular event. For example: user is valid for all the launch point where as mboset is valid only for Object launch point allow object creation event.

There are two types of implicit variables. Those which are not associated with any other variables and are used directly in the script and those which has to be associated with the variables. Lets get into the details.

Implicit Variables in Maximo Automation Scripts

Implicit variables are those variables which need not be defined separately in the script. Some of the variables can be used directly ex: app, user, mbo. Some need to be associated with other variables we declare, ex: var_required (var is the user defined variable)
Below are the list of some of the implicit variables.

Yes No Exception Handling in Maximo 7.6 Automation Script (Gathering User Input)

A company requires to send email to the owner of work order when the highest priority is set in the work order priority. An automation script is used to send this email. The automation script uses a choice that confirms to email should be sent.

What is REORDERMUTEX table

The REORDERMUTEX table is a locking mechanism to make sure no two users are running a Material Request, Direst Issue or Storeroom Reorder at the same time.
The REORDERPAD table is a temporary data holder to collect item information for the Reorder process.
After the Reorder process is done, data will be left in ReorderPad.
When the next Reorder is run by the same user, data will be removed from ReorderPad.
If you are sure no Reorder is running currently, you could delete data from these two tables.

Concatenate two fields using automation script

Goal:
To create an automation script in Maximo 7.5 that combines two fields into a new field and is triggered by the change of one of the fields.

Send email through Communication template in Scripting

We can send email notification from Communication Template with Automation Scripts.

It is needed only if the Application doesn't have the feature or if it cannot be attached to workflow/escalation. 

This script uses Communication Template feature to send email from Automation Script. In the below example email will be sent to the owner of work order as and when the work order is saved.