Maximo Open Forum

 View Only
  • 1.  Mandatory Table

    Posted 21 days ago
    Hi,

    Did anyone know how to make this table become mandatory to be filled in? This table located in "Actuals" tab.

    I did try to change field under input mode to "Required" under Application Designer for Observation field. It doesn't work. Maybe I miss something? Perhaps got someone know how to do it.
    #EverythingMaximo
    #Security

    ------------------------------
    Nor Herman Afandi
    ------------------------------


  • 2.  RE: Mandatory Table

    Maximo Certified
    Posted 20 days ago
    Firstly, I need to give you a bit more understanding.  The Tasks table window is available in both the Plans and Actuals tab.  Of course, they use the same data input and you said that the Actuals | Tasks tab was altered so making it only 'mandatory' for that tab.

    The field only becomes mandatory when the user adds a new task.  Is that the use case for you?

    Question: Have you used the Linked Controls ID on the table column?

    I have simply made the Observation field mandatory and added a task, and it works.  I've included a screenshot for you.

    Question: When should be Observation checked that its not filled in?  Only when adding a new task or maybe when completing the work order



    ------------------------------
    Regards,
    Craig Kokay
    ISW
    Maximo Practice Manager
    eMail: ckokay@isw.net.au
    Phone: +61-411-682-040

    #IBMChampion2022
    ------------------------------



  • 3.  RE: Mandatory Table

    Posted 18 days ago
    Hi Craig,

    My reply as below,

    The field only becomes mandatory when the user adds a new task.  Is that the use case for you?
    No. I want to make existing field becomes mandatory for this Actuals tab. User cannot completing the work order if this field left blank. Not a new task that user added.

    Question: Have you used the Linked Controls ID on the table column?
    No. How to use the Linked Controls ID? Perhaps you can advised me?

    Question: When should be Observation checked that its not filled in?  Only when adding a new task or maybe when completing the work order
    Observation/Measurement Value should be not filled in if there is no measurement point. User may proceed to do completing the work order if there is no measurement point. If got measurement point, the field become mandatory to be filled in.



    ------------------------------
    Nor Herman Afandi
    ------------------------------



  • 4.  RE: Mandatory Table

    Maximo Certified
    Posted 18 days ago
    Hi Nor,

    Thanks for the additional information, this gives more insight to say that a conditional UI is not the best solution as you want the field checked if:
    ===========================================================
    (a) the user is trying to change the status to COMP
    (b) the POINTNUM is not null on a task

    And if true, then:
    (c) check to see if the MEASUREMENTVALUE is populated

    If (c) is null, then raise an alert to have this completed.

    ===========================================================
    So, why do I say simply making the field won't work or the conditional UI won't work?

    Mandatory field
    When the user adds the task row, making the OBSERVATION field mandatory doesn't work as it doesn't discriminate, it just knows that the field needs to be populated at the time of saving the new row.

    Conditional UI
    This is better as now you can test if the field OBSERVATION field is empty when the task is COMP.  Please note, I said task.  This is because in reality or more specifically, it's the task that holds the observation field, so, it must be the task being completed.  This works, but only to an extent because the work order still gets COMPleted and observation becomes mandatory, but even if the user now changes the status to CLOSE, it won't invoke the warning.
    =====================================================================
    =====================================================================
    Solutions
    =======================================================================
    =====================================================================
    1. Have the work orders go through a Workflow where the conditions are checked.  You can then either invoke an Interaction node and loop back until the get it right.
    2. Create an automation script on the WORKORDER object that will raise an error, similar to the recent topic about stopping a work order if there is no labor.
    3. Create a Java class that does same and extend the current MBO class.

    ------------------------------
    Regards,
    Craig Kokay
    ISW
    Maximo Practice Manager
    eMail: ckokay@isw.net.au
    Phone: +61-411-682-040

    #IBMChampion2022
    ------------------------------