Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  WOTRACK Automation Script: Automatically expand child WO section if child WOs present

    Posted Thu November 11, 2021 01:44 PM
    Edited by System Admin Wed March 22, 2023 11:51 AM
    MAM 7.6.1.2; WOTRACK:

    [For my records, using the word "section" to describe Child WOs in WOTRACK tabs was incorrect. I should have used the term "table control".]


    I am hoping to automatically expand the child WO section in WOTRACK-->Plans/Actuals tabs, if child WOs are present. 
    Reason:
    • Some divisions don't use child WOs. So they want the child WO section to be collapsed by default. Despite extensive training, they've had problems with non-technical users accidently creating child WOs, when they actually meant to create tasks. Collapsing the child WO section solves this problem.
    • However, other divisions do use child WOs. But when the child WO section is collapsed by default, their users don't realize child WOs are there (even though the number of child WOs is listed in the header). This causes a lot of confusion. So we want to expand the child WO section, if child WOs are present.

    In a previous post, we determined that it isn't possible to collapse a section in an application via the conditional UI:
    Collapse application section based on field value?

    Question:
    As an alternative to using the conditional UI, would it be possible to conditionally collapse a section -- via an automation script? Could we use the UIContext method?

    Note: I don't want to completely hide/unhide the section; I just want to collapse/expand it. So that users can manually expand the section and create new child WOs, if needed.

    Thanks.
    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: WOTRACK Automation Script: Automatically expand child WO section if child WOs present

    Posted Thu November 11, 2021 02:35 PM
    The way I would do it is:. If child WOs exist, make the labels turn red.  That's a really easy thing to implement with conditional UI.







  • 3.  RE: WOTRACK Automation Script: Automatically expand child WO section if child WOs present

    Posted Mon November 15, 2021 06:21 AM
    Edited by System Admin Wed March 22, 2023 11:48 AM
    I suppose another option would be:
    - Expand the child WO section by default
    - Conditionally hide the buttons for creating new child WOs

    Related info here: A3J Group Pro-Tips: Change Field Color Using Conditional Expressions
    #Maximo
    #AssetandFacilitiesManagement


  • 4.  RE: WOTRACK Automation Script: Automatically expand child WO section if child WOs present

    Posted Fri November 19, 2021 02:07 PM
    Edited by System Admin Wed March 22, 2023 11:49 AM

    It turns out we can add collapsewhenempty="true" to the section in the xml.


    For example:
    <table collapsewhenempty="true" beanclass="psdi.webclient.beans.workorder.SelectWORecordsBean" collapsed="false" id="plans_children_table" label="Children of Work Order {0}" orderby="wosequence" relationship="SHOWCHILDREN">

    Credit goes to Rick in support for figuring that out.






    Also, it looks like collapsewhenempty is available in the conditional UI too:




    But to be honest, I think I've gotten my wires crossed here. I'm not sure what to set the Signature Option to...since the READ sig option seems to be hiding the Child WO section entirely (not just collapsing it when empty).

    I think I've just been starting at it for too long. And I'm not familiar with the conditional UI.


    #Maximo
    #AssetandFacilitiesManagement


  • 5.  RE: WOTRACK Automation Script: Automatically expand child WO section if child WOs present

    Posted Wed December 15, 2021 11:00 AM
    Edited by System Admin Wed March 22, 2023 11:51 AM
    FYI

    TS007579555
    Sub question:
    Why is the collapsewhenempty property available in the conditional UI, when it doesn't actually work in the conditional UI?


    IBM Support:
    "Development reviewed the collaspewhenempty property and said it was not meant to be used conditionally.
    They allowed APAR IJ36594 which will remove it from the list of conditional properties in appdesigner.
    It will be fixed in 7613"



    IJ36594: REMOVE COLLAPSEWHENEMPTY AS A CONDITIONAL PROPERTY