
Using a Global System Properties in an Automation Script
- January 25, 2023
- Xavier
- No Responses
- January 25, 2023
- Xavier
- No Responses
Maximo has a neat feature where you can set any value in the global property, and it will default to that value you have entered. In order to use a global property, you first must create one. In our example we created a global property for the person who does the PO Reorder.
After you create the global property, ensure you click on Live Refresh, so you can use the new global property created.
This is helpful because I could now use this global property in my automation script. In order to get the global property, First must create a variable like down below. “configData = MXServer.getMXServer().getSystemProperties()”
After that create another variable and get the property you have created.
“reorderAgent = configData.getProperty(“POReorderBuyer”)”
Once you completed these steps you can now use the variable “reorderAgent” which is grabbing the system property and you could use in the automation script any where you want. In our case we are setting the “PURCHASEAGENT” to the “reorderAgent” when the po description has reorder in it.
I highly recommend using this as it is helpful because now you don’t have to create a variable with the value hardcoded. So, example if this person ever goes on vacation, we could simply just adjust the global property value and this automation script will adjust the reorderAgent based on the new person we put. Instead of going into the automation script and changing the variable that was hardcoded.
We have a culture of education and paying it forward at A3J Group. Subscribe below to be the first to get the latest releases from our knowledge bank.



No comment yet, add your voice below!