This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I've been making a real hard push for users to start using the QBR/Ad Hoc reporting tool inside Maximo. The downside to this is that any non-persistent data cannot be used in the QBR tool. A key field for a new program I'm rolling out is being able to use Failure Remarks in QBR reports, but it turns out that Failure Remarks is tagged as a non-persistent data field.
Looking at the DB config properties for the Failure Remark field (WORKORDER.REMARKDESC) it appears it uses a class file to populate the Date/Time on when the remark was entered. Would it be as easy as decompile the class file to a java file, replace the references of the "REMARKDESC" field in the java file with a custom field that was tagged 'persisten', recompile the class, then add that back to my custom field?
Or am I WAY off base on extending the class file for my use?
Pretty sure those are stored in the FAILUREREMARK table. You may just have to modify the Work Order Object Structure that is consumed by reporting to add the table as selectable from the QBR.
But that isn't the right way to extend the classes, what you describe is actually against the Licensing agreement with IBM. To extend the class, you create a new one and in the initial definition of the class you use key words like "mynewclass extends theotherclass". Then when you create methods with the same name it will override the method within the original class.
-- Sean Clark-McCarthy
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Jason Verly
Sent: Monday, November 28, 2011 6:14 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re-using a class file for Failure Remarks
I've been making a real hard push for users to start using the QBR/Ad Hoc reporting tool inside Maximo. The downside to this is that any non-persistent data cannot be used in the QBR tool. A key field for a new program I'm rolling out is being able to use Failure Remarks in QBR reports, but it turns out that Failure Remarks is tagged as a non-persistent data field.
Looking at the DB config properties for the Failure Remark field (WORKORDER.REMARKDESC) it appears it uses a class file to populate the Date/Time on when the remark was entered. Would it be as easy as decompile the class file to a java file, replace the references of the "REMARKDESC" field in the java file with a custom field that was tagged 'persisten', recompile the class, then add that back to my custom field?
Or am I WAY off base on extending the class file for my use?