Maximo

Maximo

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

 View Only
  • 1.  App states Mobile Navigator

    Posted Fri December 01, 2023 09:17 AM

    In the Navigator app we find a lot of states as below.
    I tried to modify for example <state name="supportingDataDownloadEnabled" type="boolean" value="true" id="v5egx"/> and was expecting that the checkbox in the app was set to True. However nothing happened.

    Can anybody tell me what the states below do and how to set the checkboxes of the Navigator app?

    <state name="userAlreadyOnboarded" value="false" type="boolean" id="y7ppd"/>
        <state name="debugLoggingEnabled" value="false" type="boolean" id="r7v36"/>
        <state name="attachAutoDownloadEnabled" value="true" type="boolean" id="a7abq"/>
        <state name="supportingDataDownloadEnabled" type="boolean" value="false" id="v5egx"/>
        <state name="workListDataDownloadEnabled" type="boolean" value="false" id="yqma3"/>
        <state name="supportingDataDeltaDownloadEnabled" type="boolean" value="false" id="b5jy3"/>
        <state name="mapDataDownloadEnabled" type="boolean" value="false" id="bg4rd"/>
        <state name="txPendingCount" type="number" value="0" id="eqgp4"/>
        <state name="txErrorCount" type="number" value="0" id="yeemv"/>
        <state name="downloadErrorCount" type="number" value="0" id="nyqb4"/>
        <state name="isEamApp" value="true" type="boolean" id="qykab"/>
        <state name="appName" type="string" value="Maximo Mobile for EAM" id="ea27d"/>
        <state name="reAuthenticationAlert" type="boolean" value="false" id="n5v3_"/>
        <state name="loginPageClosed" type="boolean" value="false" id="k5e45"/>
        <state name="refreshTimeout" type="number" value="600000" id="xxjmy"/>
        <state name="updatingData" type="boolean" value="false" id="gqa8e"/>
        <state name="updatingApps" type="boolean" value="false" id="rz3j5"/>
        <state name="updatingLookupData" type="boolean" value="false" id="e53k2"/>
        <state name="updatingTransactionData" type="boolean" value="false" id="brn77"/>
        <state name="updatingMobileDb" type="boolean" value="false" id="xde6a"/>
        <state name="updatingAttachments" type="boolean" value="false" id="y9e_5"/>
        <state name="synchronizingData" type="boolean" value="false" id="zd52j"/>
        <state name="synchronizingTxs" type="boolean" value="false" id="jgnv_"/>
        <state name="isEncrypting" type="boolean" value="false" id="x3_58"/>
        <state name="dbStepNumber" type="number" value="false" id="najwr"/>
        <state name="dbDownloadError" type="boolean" value="false" id="ww7k6"/>
        <state name="masterSchemaLoaded" type="boolean" value="false" id="dk3ab"/>
        <state name="attachDownloadError" type="boolean" value="false" id="anz_j"/>
        <state name="toggleReadOnly" type="boolean" value="false" id="ex5pm"/>
        <state name="esigGeneralDynamicError" type="string" id="yrygz"/>
        <state name="esigKeyDynamicError" type="string" id="jznr2"/>
        <state name="esigKeyConfirmationDynamicError" type="string" id="gnqwa"/>
        <state name="esigDialogProcessing" type="boolean" value="false" id="q6rkd"/>
        <state name="isKeyCheckDisabled" type="boolean" value="false" id="d_vwb"/>
        <state name="esigKeyCreationRuleValidation" type="boolean" value="false" id="dejrn"/>
        <state name="esigKeyCreationRestrictionValidation" type="boolean" value="false" id="gp2j6"/>
        <state name="currentDefaultSite" type="object" id="a_wi3"/>


    ------------------------------
    Vincent Wanders
    ------------------------------


  • 2.  RE: App states Mobile Navigator

    Posted Mon December 04, 2023 10:35 AM

    The AppController.js is setting the supportingDataDownloadEnabled state variable to false in the applicationInitialized logic so the default value on the state in the app.xml won't matter. You could override this in the AppCustomization.js using another event. 

    I understand the desire to have this defaulted, but I would be very hesitant to modify the navigator application. This application is fundamental to how mobile operates and can't be cloned. Every patch will overwrite your changes and need to be reapplied properly. A mistake during the build process can negatively impact how all of Maximo Mobile operates. Some examples of potential issues:

    1) using the wrong version of the config tool. We bundle the graphite framework in the config image and going higher or lower can cause it to function differently than intended on that version. I've seen customers use a 8.11 image even though they're on 8.10 and I've seen them stick with the 8.10 base image even though their Maximo is running 8.10 IFIX 06. 
    2) publishing the wrong app.xml/controllers. The config tool works from your local workspace when you have files. I've seen customers upgrade their Maximo environment and republish their app without realizing they published the old version of the app.xml/controllers because they didn't re-download it from the server. 

    These types of things can lead to issues that are extremely had to identify because you're in a state that normally won't happen. 



    ------------------------------
    Steven Shull
    ------------------------------