@mkart-vrn there are help docs available. This can be exposed by showing them via the edit menu page and saving the changes. Alternatively, on the scripting datasource page. There are question marks you can click on that will render a sidebar to the right with a detailed explanation and or help docs.
I also encourage you to look through the forum and see what has been accomplished by other mango power users.
As for delays, there is a delay option so you can delay the firing of a script upon a trigger as well as using a cron style scheduler. There's also an advanced scheduler which you can attach event actions to for triggering scripts, running a local application, even setting point values.
Feel free to raise more forum posts in user help to fill in any blank areas. I'm on here throughout the week usually. I'm currently remote however so expect up to week delays...
@Benoit watchlists are either statically defined, or dynamically with the use of an rql lookup or with tags.
Since you're unfamiliar with scripting data sources it may be outside of your capabilities..
What I'd do is:
Use a json data store to store a list of data sources, including the total datapoints and datapoints tagged count.
Load said json stire and iterate through each datasource whilst doing a lookup with an offset.
Each time completing a batch of points, increment the number of points tagged and update the json store file as well to track
once all points tagged are equal to the total points available, move on to the next datasource
That's pretty nice, I was actually wondering if it was possible to do something like that. I have some ideas on using a point value to do things to other elements, which would add a lot of value to the dashboards.
@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?
@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.
@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.