Maximo Open Forum

Upon decompiling the class, it is observed that the dataBean parameter passed into the DataBeanContext constructor has not been initialized.

#Administration

------------------------------
Ethan Williams
secrecy
------------------------------

Looking at your screenshot it does appear that the constructor accepts the databean parameter but it then doesn't use it.

This would need to be raised with IBM as a support case. They will need a log demonstrating the NullPointerException that is raised when the getDataBean() method is called.

------------------------------
mark robbins
Cohesive
IBM Champion 2017-2024 Inclusive
See my blog on Maximo support related topics here:
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
------------------------------

This has been this way since it was implemented. I'll be honest, I haven't opened a support ticket to get a defect on it. IBM never documented this feature publicly. I only learned of it because I was at IBM and did this presentation (MSUG - Automation Scripts in Maximo Application Suite | Maximo Open Forum) to share to a wider audience. Since then, people covered it even further including my now colleague Andrzej (https://www.linkedin.com/pulse/ibm-mas-manage-ui-bean-scripting-andrzej-wieclaw-4vtbf/ ) 

Undocumented features are a little bit trickier to get defects approved because it has never been documented how you are supposed to be able to utilize it. But in this scenario, I imagine if someone opened the support ticket, they would get IBM to approve it. 

------------------------------
Steven Shull
Naviam
------------------------------