Maximo Open Forum

 View Only

Related Content

  • 1.  Scratching my head over this issue.

    Posted 08-07-2024 12:32

    I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

    For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

    The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

    This is only happening in the client's DEV environment and not in their test environment.  

    What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.

    This is the screenshot... I added the jpclass attribute to the work order header, and you can see it is blank.  Any ideas of where to look next would be helpful

    #WorkManagement

    ------------------------------
    Stephen Hume
    Sheffield Scientific LLC
    ------------------------------


  • 2.  RE: Scratching my head over this issue.

    Posted 08-07-2024 20:05

    Hi @Stephen Hume!

    In the application editor (WOTRACK), you can edit the WOCLASS field. You can put it read-only, default, required (I've seen it in all 3 ways). You can put a default value or not. So, if you define a default value, every time you create a new WO record, it will appear. If you do not define any default value and the field is released (defined as default), it will not load anything and will leave it released.

    So, the difference is in the default value. You can modify this either by editing the wotrack xml or in the application designer on WOTRACK, by pressing "Toggle show conditional UI Control" (it will show you all the conditional controls with a black icon).

    Regards!



    ------------------------------
    Martin Fabra
    ARSAT S.A. - Actively seeking employment
    ------------------------------



  • 3.  RE: Scratching my head over this issue.

    Posted 08-08-2024 09:11

    Thanks Martin, the woclass field is not the problem... it is being defaulted with the value WORKORDER which is correct.  The issue is that in the wotrack application for some reason the JPCLASS which is a non-persistent field and is supposed to equal the WOCLASS it blank (null values).  In other applications using the workorder object, the JPCLASS is being populated when the WOCLASS contains a value.  JPCLASS is handled by a java class and default value cannot be set for a non-persistent attribute.  I am just trying to figure out how the field a null value when it should not be.



    ------------------------------
    Stephen Hume
    Sheffield Scientific LLC
    ------------------------------

    Original Message


  • 4.  RE: Scratching my head over this issue.

    Posted 08-08-2024 13:22

    Hi Stephen,

    Is this causing you a problem or are you just curious?

    The JPClass attribute is used by the dialog that is launched by clicking "Select Value" option from the "Detail Menu" next to the "Job Plan" field on the main "Work Order" tab in the "Work Order Tracking" application.  It's only purpose is to filter allow the user to filter for Job Plans based on the WO Class(es) associated with the Job Plans, if any.



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



  • 5.  RE: Scratching my head over this issue.

    Posted 08-08-2024 18:05

    It's unlikely this class has any customisation. And since it only occurs in the DEV environment, I rule out it is a Maximo bug. I would try refreshing the DEV environment from Production first. If it doesn't help, two options I can think of are:

    • Develop the feature in TEST
    • Connect an IDE with Maximo DEV to do a live debug


    ------------------------------
    ------------------------------------------
    Viet Tran
    Relia App Development & Consulting
    https://relia.app
    ------------------------------



  • 6.  RE: Scratching my head over this issue.

    Posted 08-09-2024 08:38

    Thanks Viet, 

    Here is what I have done to work around this issue.  I cloned the WOTRACK application to make a version specific to the business unit that will be using it, and lo and behold the JPCLASS attribute is functioning properly.  I believe that somehow the WOTRACK application itself is corrupted in some way, and unfortunately the project I am on does not have the latitude to restore DEV from Production.  We did try importing the WOTRACK xml from the TEST environment where it is working properly, but even after doing that it was having the same problems with JPCLASS.

    The bottom line it is one of life's mysteries, and we have a work around (the cloned application) so our project can move forward.

    Thanks for your suggestion..

    Steve



    ------------------------------
    Stephen Hume
    Sheffield Scientific LLC
    ------------------------------

    Original Message