Maximo

Maximo

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

 View Only
  • 1.  Graphite application cloning issue in MAS 9.1.4

    Posted Wed October 15, 2025 06:45 PM

    Hi everyone,

    I'm using MAS version 9.1.4 and I would like to try making some changes to a Graphite application to familiarize myself with the the new framework.

    Using the "Application configuration" app, I duplicated the "WOSUMMARY" desktop application. Then, I published my new application without customizing or making any changes to the "app.xml" file.
    When I try to load the app from Maximo Manage, it freezes on the loading spinner.

    Using the browser console and inspector, I looked for clues and I noticed something.
    When I load the cloned app, the "Sources" tab of the Chrome console shows only a "index.html" file with two errors related to two different import statements (one .js and one .css file).
    When I compared the "index.html" files loaded by the cloned and the original apps, I noticed that the import paths (src attributes) were different:

    • *.js from cloned app: /preview/assets/index-CWelaHWw.js
    • *.js from original app: ./assets/index-Dyxv3o5U.js
    • *.css from cloned app: /preview/assets/index-CVx2ZjyO.css"
    • *.css from original app: ./assets/index-DhOSQYh_.css

    I understand why the IDs in the file name are different. I suppose they are created dynamically during the build.
    However I don't understand why the cloned app tries to load the files from the "/preview" folder.

    Also, the loaded sources structure is different:
    Cloned app:
    Original app:

    Has anyone had any luck with duplicating a Graphite desktop app in MAS 9.1.4?



    ------------------------------
    Yuri Vedovato
    ------------------------------


  • 2.  RE: Graphite application cloning issue in MAS 9.1.4

    Posted 13 days ago

    This usually happens when the cloned Graphite app still contains build metadata from the preview environment. When you duplicate a Graphite application in MAS, the app.xml and generated assets sometimes keep references that point to the preview path instead of the final deployed path-so the app ends up looking for resources under /preview/assets instead of ./assets, which causes the spinner freeze.

    A couple of things you can check:

    • Open the cloned app's app.xml and verify the entryPoint and resource paths weren't altered during duplication.

    • Republish the app again using the "Build and Publish" option instead of just "Publish," since the clone may not have triggered a full rebuild.

    • Clear browser cache or load in an incognito window-Graphite apps can be sensitive to cached asset paths.

    • Make sure the app is not being opened from the Preview mode inside App Designer, which automatically prepends /preview/ to asset requests.

    If nothing was changed manually, the simplest next step is to rebuild the cloned app so it regenerates the correct asset paths. Let me know if you want to share your app.xml snippet - sometimes one line in the metadata points the whole bundle to the wrong directory.



    ------------------------------
    Areesha Adeel
    ------------------------------



  • 3.  RE: Graphite application cloning issue in MAS 9.1.4

    Posted 12 days ago

    This is DT dt446092 Known Issue: DT446092


    It was listed as fixed in 9.1.4 (Readme file for Maximo Application Suite 9.1.4) but might only be for new clones. I've never looked at fixing this for our customers so Areesha's guidance might be on point. I would personally delete and start over



    ------------------------------
    Steven Shull
    Principal Maximo Solutions Engineer
    Naviam
    Cincinnati OH
    ------------------------------