mboSet() in Automation Script, getMboSet() vs getThisMboSet() | Maximo

Most of the time automation script creates an implicit variable "mbo". It represents the current record on which the script was triggered. 

let say we open one workorder: 123. in this case, our mbo is 123. 

what If we want to get the MboSet of this mbo. (like we are going back to the list tab :)

here you go. 

mboSet = mbo.getThisMboSet()

2. Most common way to call an mboset is using famous method , which is

mbo.getMboSet("PR")

where PR is the Relation Name already exists in database configuration from this record. 

3. or we can create at run time a new relation with WhereClause, like this:

 woSet = mbo.getMboSet("woSet ", "WORKORDER", "status = 'APPR' and siteid = 'BEDFORD'")

4th and last is get any MBO from the system, which is the least recommended if the things can be handled with first 3 methods.  

If the "mbo" implicit variable is not exists then you need this:

woSet = MXServer.getMXServer().getMboSet("WORKORDER", userInfo)