Maximo Open Forum

 View Only

Related Content

  • 1.  Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 01-16-2023 14:55
    OVERVIEW
    In many Maximo applications the specifications table is setup to show dedicated columns for alphanumeric value, numeric value and table value. The dedicated columns map to the three dedicated columns for the three different datatypes in the backend. However, I have found that the three columns can be frustrating to end users. To simplify this I have seen a combination of a non-persistent field and automation scripts to consolidate the three different types of values into one field in the applications. While effective this can be a bit cumbersome to configure and a bit error prone.

     A couple years ago I found some IBM documentation that in the Maximo Developing Applications 7.5 documentation. This documentation showed how you can use {CLASSSPECVALUE} in application designer to consolidate the 3 columns into 1 column for the user to both read and enter values. I have added a copy of the IBM documentation below for easy reference. In my experience this has been very reliable and I use it anytime I am given the opportunity. I hope you find it helpful too.  

    IBM DOCUMENTATION FROM DEVELOPING APPLICATIONS v7.5
    Before you begin
     The Maximo ® business object (MBO) that the Classification Specifications table is bound to must contain ALNVALUE, NUMVALUE, and TABLEVALUE attributes. If the MBO does not contain the attributes, you cannot merge classification attribute values. The Classification Specifications table must also contain either a field class or a MBO validation class. The inclusion of either a field class or a MBO validation class ensures that all the value fields are read-only. The only exception is the value field associated with the data type of an attribute. For example, if the datatype is alphanumeric, the alphanumeric MBO attribute is read/write while the numeric and table value MBO attributes are read-only.

     About this task
     You can merge classification attribute values only for the classification specification attributes.

    Procedure
    1. In the Application Designer application, open the application that you want to change.
    2. In the Specifications table on the Specifications tab, click the attribute that you want to change.
    3. Delete the alphanumeric value column, the numeric value column, and the table value column by using the Context menu.
    4. In the toolbar, click Control Palette and select the Table Column icon.
    5. Drag the table column onto the Specifications table and close the Controls window.
    6. Open the Context menu, click Properties, and specify the label name for the column. If you do not specify a name, the label from the alphanumeric value attribute is used.
    7. Specify {CLASSSPECVALUE} as the attribute value, and clear the Show Filter check box.
    8. Ensure that the Sortable check box and the Filterable check box are clear.
    9. Save the changes.

    #Administration
    #Customizations

    ------------------------------
    Phil Runion
    Projetech
    ------------------------------


  • 2.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 05-12-2023 17:20
    Edited by Christopher Winston 05-15-2023 09:05

    @Phil Runion This is a great idea. I have added screenshots of the before and after as well.

    Before


    After






    ------------------------------
    Christopher Winston
    Projetech Inc.
    ------------------------------



  • 3.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 07-12-2023 10:56

    Hi Phil,

    I found this post while I was looking at how to combine my spec value fields into one, because I have seen you Demo this before.

    Looking in my 7.6.1.3 environments I do not have a CLASSSPECVALUE attribute on my database.  Do you know what is required to get this created out of box?

    Thanks!

    Eric Godel



    ------------------------------
    Eric Godel
    Bay Systems Consulting
    ------------------------------



  • 4.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 07-12-2023 13:33

    To utilize this you don't have the add it to the database. This is a built in non-persistent that you can use without any changes in database configuration. I have included a screenshot from application designer in an instance that I am using this in. 



    ------------------------------
    Phil Runion
    Projetech
    ------------------------------

    Original Message


  • 5.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 03-06-2024 18:26

    It doesn't look like this lovely shortcut works for DATE type Specifications.  It was a great find though!  If you leave the original columns around, it's also entertaining to see the wrong attribute getting it's value changed, and then everything works out when its saved.



    ------------------------------
    Scott Mahon, P.Eng.(AB)
    Maximo Solution Architect
    ------------------------------

    Original Message


  • 6.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 03-07-2024 12:41

    You're right about the DateValue attribute not being handled by {CLASSSPECVALUE} that option was introduced in Maximo 7.5 whereas the DATE Data Type and the DateValue attribute are fairly recent additions.  And as unfortunately happens much more often than it should, the DATE Data Type and the DateValue attribute were added without considering the full implications.  For one thing, when the DATE Data Type was added in Maximo 7.6.1.2, the DateValue attribute was only added to the TicketSpec, TkTemplateSpec, and TkTempltActySpec objects. 

    In Maximo 7.6.1.3, the DateValue was added to AssetSpec, ItemSpec, JobPlanSpec, JobTaskSpec, LocationSpec, and PDSpec.  But it is still missing from many ...Spec objects such as ActCISpec, AssetFeaSpecHist, AssetFeatureSpec, AssetSpecHist, BIMProducBaseSpec, CISpec, CISpecHis, FeatureSpec, PlusCTpSpec, PlusDCUSpec (Utilities), and SolutionSpec.

    I highlighted AssetSpecHist because not having the DateValue there presents a particular problem since it was added to the AssetSpec.  There is specific logic for Assets (and a few other objects) that writes the history of Spec Value changes to a history table, which is AssetSpecHist in the case of Assets.  Since DateValue exists on AssetSpec, someone may enable it without realizing the history is not being written as expected.  APAR IJ39622 is outstanding to fix this but I have been waiting almost 2 years for a fix.

    I noticed at one time that someone submitted an Idea (previously known as a Request for Enhancement or RFE) to add the DateValue to all objects and I believe it was accepted but hasn't been delivered.

    I would suggest submitting a Case to report that the {CLASSSPECVALUE} option is not handling the DateValue as it should.  There's a good chance you will be asked to submit an Idea instead but at least it will get the process started.

    Thanks.



    ------------------------------
    Julio Hernandez
    Ergonare, Inc.
    ------------------------------

    Original Message


  • 7.  RE: Simplify Specification Screens By Utilizing {CLASSSPECVALUE} - Show Values in One Column Instead of Three Columns

    Posted 07-11-2024 08:47

    In the June 2024 release the DateValue attribute not being handled by {CLASSSPECVALUE} issue was addressed in the 8.11 and 9.0 releases. 

    https://www.ibm.com/support/pages/apar/IJ51093



    ------------------------------
    Phil Runion
    Projetech
    ------------------------------

    Original Message