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.

@Jared-Wiltshire Sorry to re-open this thread, but with the anonymous user role introduced in v4, does it mean we should be able to define certain pages with anonymous "View Page" permission which allow access of these pages without the need of Mango login?

BR,
Ricardo

@tungthanh500 it comes with understanding angularJS scopes ($scope).
In this case you have a variable of $scope.currentArea
Since this scope is attached to our view, the variable (in this case) can be accessed as currentArea.
Since we want the variable and not a string called "currentArea", we "add" (I use the term loosely here) the strings that make up your RQL query and supply the dynamically allocated currentArea variable.

Also look at controllerAs to understand nesting controllers and their respective scopes.

Fox

@terrypacker thanks, but this is very unfortunate, as I am not thinking of "a much nicer page" in that I probably have 20 pages: most have dozens or hundreds of points. Converting by hand would be very tedious.

Is there a reference that explains how to recreate dashboard structures that are equivalent to existing structures used in the graphical view? For instance, the "Simple point" data structure normally shows the point value. On mouseover, a pop-up point links to the point details, and shows a pop-up default graph. Would I have to recreate that behavior in the dashboard from scratch?

Similarly, the "complex point" structure shows a table of Simple points, each with the Simple point mouseover behavior; binary points show pop-up default tables on mouseover. Would I have to write all that too, or are there equivalent data structures? Last time I looked at the dashboard a couple of years ago, I did not see a built-in way to replicate this behavior without going low-level. Even if there is an equivalent structure, mousing and clicking around to recreate each point would take ages because there are so many.

What is available to speed this conversion?

@sasa

The link mentioned is not valid anymore

@gordoe
Happy to, have sent you a PM

Any advise?

@jared-wiltshire Is there any way to add dynamic name of event detector using $index.

<div ng-repeat="point in soapDispenserLevel"> <ma-point-event-detector point="point" detector-type="LOW_LIMIT" alarm-level="DO_NOT_LOG" detector="soapDispenserLevel{{$index}}" ></ma-point-event-detector> </div>

6b1e3476-4f47-48f5-a465-ded1e1b46fe3-image.png

@jared-wiltshire
Thank you for your explaination. Can you be more specific about "datebar.to" and what is it in mango? I mean, there should be something like "myPoint.value" to show/assign a point value or "myDevice.name" to show the device name.

@joelhaggar
I am using v3.7.7 so I am out of luck there with the setttings.