• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Graphic view controls showing hourglass for some users

    Mango Automation general Discussion
    2
    3
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • AldoRamosA
      AldoRamos
      last edited by

      We have a Graphic view that not only summarizes plant operations, but allows the most commonly-used functions (start/stop etc.) to be controlled from that view. This has been operating just fine for a super-admin, but now that we've delegated the control to another user, it does not display the controls. It only displays an hourglass that never resolves to the expected input (binary toggle, numeric input).

      The user has proper permissions, and is able to enter the input on the Data Points page without any problem. It's only on the Graphic view that this problem appears.

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by phildunlap

        Hi Aldo,

        Graphical views are a little idiosyncratic when it comes to permissions. Have you given the user in question set permission to the graphical view itself? These permissions can be edited when editing the view.

        Graphical views always had a slightly unique permissions: the current behavior was due to old behavior overriding data point permission (way back when every data point had a row of permissions radio buttons on the user's page) and the availability for anonymous views. So, we retained compatibility when updating the module to the current permissions system.

        1 Reply Last reply Reply Quote 0
        • AldoRamosA
          AldoRamos
          last edited by

          Bingo! Good call!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post