#dominoforever | Product Ideas Portal


Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Nomad: Disable MarvelClient function

A customer don't want to use MarvelClient on Nomad, so they want to disable it, because sometimes Nomad causes MarvelClient issues, although they are fixed by upgrading Nomad version.

They think it is a fatal issue that Nomad can't be used when MarvelClient causes something issue.

  • Guest
  • Dec 21 2020
  • Shipped
  • Attach files
  • Admin
    Thomas Hampel commented
    12 Jan 08:57pm

    If there is an issue, then it should be fixed in the product. So please do not just try to find a workaround yourself, but open a ticket to address the issue.

    The MarvelClient is enable by default on mobile devices, but not performing actions unless told to do so. If you still want to disable even loading it then see our documentation: https://help.hcltechsw.com/nomad/1.0/hcln_disabling_marvel.html or https://help.hcltechsw.com/nomad/1.0_android/hcln_managing_mdm.html See Table 2.

  • Guest commented
    22 Dec, 2020 10:44am

    I think this is not the real case. MarvelClient is embedded to manage Nomad and solve client issues not the other way around. As far as I know we as panagenda were not involved in that case, which probably would make sense to be involved.


    If you have any issues with HCL Nomad and you think MarvelClient is involved, please let us know by sending us a mail to support (at) panagenda.com. We are always happy to help!