Maximo

 View Only
Expand all | Collapse all

Refreshing a record in Maximo (in the browser)

  • 1.  Refreshing a record in Maximo (in the browser)

    Posted Tue April 20, 2021 11:22 PM
    Edited by System Test Wed March 22, 2023 11:53 AM
    MAM 7.6.1.2; Google Chrome 89:

    I have a WO open in WOTRACK. The WO has been modified by some other process, so I want to refresh it in the browser so that I can see the latest data.

    Intuitively, since there isn't a refresh button in Maximo, I would hit refresh in the browser, and it would show the updated record. But if I do that, the browser just produces the same old snapshot of the record that I was looking at previously. (And a hard refresh (Ctrl + F5) doesn't work either.)

    Instead, I need to drag the WONUM from the Work Order tab, drop it into the Find Work Order text box, and click the search button. This seems to be the only way to properly refresh the record.


    While that technique works, it is not intuitive for new Maximo users.

    Questions:

    1. Why doesn't Maximo refresh when the browser refreshes?
    2. Why can't there be a refresh button that achieves the same thing as the drag & drop technique above?

    Thanks.


    RFE / Idea:
    Add a refresh button to Maximo applications
    https://ibm-ai-apps.ideas.ibm.com/ideas/MASM-I-544
    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Refreshing a record in Maximo (in the browser)

    Posted Wed April 21, 2021 08:15 AM
    For your first question, that's changing with Work Centers where they're designed to be stateless and retrieve data from the Maximo system via REST API. But with the legacy UI as you've mentioned a refresh won't trigger a refetch of the record. As a stateful application, the server is maintaining the MBOs (and corresponding MBOSETs) for tracking records that have been modified and how they've been modified. When you use the "Find", what you're really doing is adjusting the where clause the application uses and resetting that set to contain only those MBOs. It's not really a "refresh" in that sense. 

    For your second question, you probably could create an action automation script that does what you want but my experience with UI work is limited. I've done some simple navigation from one record to another using the below (replacing UNIQUEID with the ID of course). 
    webSession=service.webclientsession()
    webSession.getCurrentApp().getAppBean().moveToUniqueId(UNIQUEID)​


    And this works to navigate to a new record (including records that aren't part of your set) but doesn't seem to work in the simple refresh scenario. I think you'd have to get the AppBean's find() function to work somehow or at least mimic some of what they're doing. The function is designed around the WebClientEvent being the user utilizing the find, which won't be the case here (it'll be the user invoking your action), so that might be tricky to make it work. But implementing a subset of it seemed to work well for me.

    appBean=webSession.getCurrentApp().getAppBean()
    resultsBean=appBean.getResultsBean()
    resultsBean.resetQbe()
    resultsBean.getMboSet().ignoreQbeExactMatchSet(False)
    resultsBean.setUserWhere("")
    resultsBean.setQbe("workorderid","="+str(mbo.getUniqueIDValue()))
    resultsBean.reset()
    resultsBean.next()
    resultsBean.getMboSet().ignoreQbeExactMatchSet(True)​


    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------



  • 3.  RE: Refreshing a record in Maximo (in the browser)

    Posted 26 days ago

    Thank you Stephen. It's work for me.



    ------------------------------
    Emmanuel Perron
    ------------------------------



  • 4.  RE: Refreshing a record in Maximo (in the browser)

    Posted 24 days ago

    Hi,
    if it's helpful to you, a few years ago I wrote an article on this topic:
    How to add a reload button to your Maximo app



    ------------------------------
    Diego Visentin
    EAM BU Director
    Tempestive S.p.A.
    ------------------------------



  • 5.  RE: Refreshing a record in Maximo (in the browser)

    Posted Wed April 21, 2021 10:30 AM
    I like Stephen's approach, but call me jaded, it seems like a helluva lot of work and expense to develop/test /deploy a working to replace a VERY simple CTL+C / CTRL+V user action.  BTW the Refresh button on the browser has never been a good idea for Maximo going all the way back to 2001.

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------



  • 6.  RE: Refreshing a record in Maximo (in the browser)

    Posted Wed April 21, 2021 01:34 PM
    The ctrl-c / ctrl-v option has been around for a long time, and mostly does its job. Unless, you run multiple sites and the Wonum (or any key value you want to refresh) is non-unique. I've seen examples in the past where each site began with work order number 1001. This means that the ctrl-v action would give you any random Wonum = 1001, very likely not of the site your were working in at that time. As the refresh action IS part of some of the IBM code, it would appear to simple to expose it to the user. Unfortunately not something we managed to do, so ctrl-V it is for now...

    Ruud





  • 7.  RE: Refreshing a record in Maximo (in the browser)

    Posted Wed April 21, 2021 01:59 PM
    Ruud! Good to hear from you.  Totally agree with you.  Also if the user removes the default sited and or unchecked the "use as filter" checkbox, your scenario is usually the case.  If the user keeps that value and uses the checkbox then the issue becomes less annoying.  ;)

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------



  • 8.  RE: Refreshing a record in Maximo (in the browser)

    Posted Wed April 21, 2021 02:41 PM
    Edited by System Test Wed March 22, 2023 11:48 AM

    These are all reasonable points. Thanks.

    In my view though, the lack of an intuitive way to refresh just adds to the list of things that make Maximo hard to use. We're currently in the process of training users, and the feedback we've gotten has been unanimous: Maximo is unnecessarily difficult to use. Sure, after a few months, people can get used to its quirks, especially if they're IT people. But, the goal is always to deploy an easy-to-use system, and not have to train users about the system's quirks/issues -- right from the start. If this was the only quirk with Maximo, then there wouldn't be a concern. But unfortunately, it isn't the only issue.

    Maximo is a multi-million dollar system, and we still have to "jiggle it" to make it work in some cases.


    Sorry if I sound bitter. Most of this frustration is directed at all the issues with Maximo addons. For example, we have an issue where the Spatial map only loads about half the time. Support hasn't been able to fix the issue (ticket open for 8 months). So the direction we'll be giving to our users is to "wait a few minutes, then jiggle it, and hopefully, it will eventually load".
    In contrast, core Maximo is actually pretty decent in comparison. I wouldn't call it "easy to use", especially for new users. But it generally works, which is good.

    Thanks everyone for your input.