Mango Automation's JSP views did not provide a native way to retrieve arbitrary historical data in the documented product state. This limitation applied to both M2M and MA. The evidence does not identify a software version or date, so verify the behavior in the exact release under evaluation.
Confirm the JSP history limitation
JSP views could not request arbitrary point history directly. The unresolved design requirements included whether a future interface should return point values only or also attributes, and whether it should return one point at a time or collate values from multiple points.
| Requirement | Evidence-supported status |
|---|---|
| Arbitrary history from JSP views | Not available in the documented state |
| Single-point history | Proposed requirement; no implementation confirmed |
| Collated multi-point history | Proposed requirement; no implementation confirmed |
| Point attributes | Scope under discussion; no implementation confirmed |
| Alarm object for custom formatting | Requested capability; no implementation confirmed |
Choose an integration path
The demonstrated workaround used an external PHP script to query the same database and generate JSON. Client logic then treated the JSON history as a rolling stack: append values received from ScriptPoint updates and remove older values from the front. This path adds a separate database-access layer and does not satisfy the stated preference to route queries through Mango's queue.
- Define whether the dashboard needs one point or synchronized values from multiple points.
- Define whether returned records must include attributes in addition to values.
- If using the external JSON workaround, implement explicit append-and-trim logic for live ScriptPoint updates.
- Verify that the resulting time order, point association, and retained history window remain correct after repeated updates.
Treat the proposed API as unconfirmed
An MA API module was being considered, with REST and RPC discussed as possible designs. The intended direction was broad programmatic access comparable in scope to import/export, but the evidence does not confirm an API release, endpoint, request format, or supported object model. Do not design a production dashboard around that proposal until the installed release documents the required interface.
Check Dojo compatibility separately
The bundled Dojo library had reportedly been updated during the summer and was described only as relatively recent; no exact version was provided. AMD support was not completed. Loading a later Dojo version caused conflicts in the reported dashboard, so identify the bundled version and test modal components without assuming that newer documentation matches it.
FAQ
Can Mango Automation JSP pages retrieve arbitrary historical data?
Not in the documented M2M or MA product state. Because no release number is identified, confirm this limitation against the exact version being evaluated.
How can I display Mango historical data on a custom HTML5 dashboard?
The reported workaround queried the database through PHP, returned JSON, appended ScriptPoint updates, and trimmed old values from the front. It requires a separate database interface and rolling-buffer logic.
Was a REST API available for Mango Automation?
The evidence only shows that an API module was under consideration, with REST and RPC as possible approaches. It does not establish that either interface was released.