Magic Suite

ReportMagic 2.23 is released as a bug fix and maintenance release with a few small changes.   We continue to progress with a new 3.0 user interface, which offers significant scalability and architecture benefits,  Improvements The [LogicMonitor.SummaryValue:] macro now supports the aggregation types minDateTime and maxDateTime as values for the aggregation parameter.  These report the time that either the lowest or highest data point was encountered for the specified reporting period.  To aid readability of .rmscript files it is now possible to split a macro definition over several lines.  Comments may also be added, denoted by // on a line.    The execution of report templates can be restricted by the use of a regex within a report schedule.  This is only available to those report schedules that use the file protocol. Bug Fixes and Other Work  There have been fixes to the rendering of the Table of Contents and Table of Figures during re...

ReportMagic v2.22 is released.  This a bug fix and maintenance release with a few small changes.  Work continues with the new 3.0 user interface, which offers significant scalability and architecture benefits. Improvements Some changes have been made to the wording presented during the user registration process.  The [Table.Save:] macro has been extended to allow multiple tables to be saved to a single Excel worksheet by specifying the start cell. Feedback ticket IDs now use the prefix RM. Bug Fixes and Other Work [Toggl:] macros stability improvements Improved detection and handling of special symbols and control characters in report templates. Fixed an issue affecting the [ElseIf:] macro. Fixes to macros that handle Excel data.  The [File.Xlsx.Row:] macro is now retrieving specific cell data correctly and the various [File.Xlsx.xxx:] macros now respects system defaults when the worksheetName parameter is omitted.

As we continue to progress with a new 3.0 user interface, with significant scalability and architecture benefits, ReportMagic 2.21 is released as a bug fix and maintenance release with a few small changes. Improvements A newly registered user who has confirmed their email address now receives a more reassuring message when their account has yet to be approved by their Tenant Administrator. A Security link is now available to non logged in site visitors, enabling the viewing of the security policy without the need to register. The API has been decoupled from the installer.  This seamless change ensures the API remains available in the usual way. Bug Fixes and Other Work There have been fixes to some graph macros.  The yAxisIsLogarithmic parameter is now better supported by the [LogicMonitor,Graph:] macro and the [List.Graph:] macro handles poorly specified donut chart data more gracefully. The progress page no longer presents message, status and macro breakdown statistics entir...

As we continue to progress with a new 3.0 user interface, with significant scalability and architecture benefits, ReportMagic 2.20 is released as a bug fix and maintenance release with a few small changes. Improvements In Files, the 10-file limit at any one time has been relaxed. You can now upload or download up to 100 files at once. More detailed help is included showing our method of determining which alerts to include in macros, and why alert counts may differ to the those shown in LogicMonitor. When you create or edit Schedules, there is now an additional Description field shown. The LogicMonitor HealthCheck template has been updated. Bug Fixes and Other Work  A bug was fixed in the LogicMonitor HealthCheck stopping the portal URL being correctly obtained. You are no longer able to clone or update a Schedule which you then cannot read due to RBAC.

Improvements LogicMonitor macros now pause during LogicMonitor portal upgrade, and retry every 10 seconds until the service is available. You can change this, the default behaviour, by setting waitDuringUpgrades for your LogicMonitor connection in Macro Parameter Defaults. You can also set this as a parameter on all LogicMonitor macros, which overrides any other defaults. You can redact the results of macros that produce textual output by setting the new redact parameter to true (default is false). This replaces substituted macro text and output macro text in the results, user interface and database with the word REDACTED. You can set a a clean up age (days) for the output folder of your Schedules. Any files in that folder / sub-folders are deleted if older than the specified value. You can of course set them not to age, or use a Tenant-level default (set by a Tenant Admin). [ReportMagic.ReportScheduleProperty:] and [ReportMagic.ReportScheduleList:] macros now allow you to specify mult...

New Macros Many, many new Meraki macros! [Meraki.NetworkClientList: ] [Meraki.WirelessNetworkDevicesLatencyList: ] [Meraki.WirelessNetworkDeviceLatencyList: ] [Meraki.WirelessNetworkClientsLatencyList: ] [Meraki.WirelessNetworkClientLatencyList: ] [Meraki.WirelessNetworkDevicesConnectionStatsList: ] [Meraki.WirelessNetworkClientsConnectionStatsList: ] [Meraki.WirelessNetworkConnectionStatsProperty: ] [Meraki.WirelessNetworkDeviceConnectionStatsProperty: ] [Meraki.WirelessNetworkClientConnectionStatsProperty: ] Also: [ReportMagic.ConnectionStatusProperty:] macro determines the status of a ReportMagic connection so you can avoid running a section of a report if the remote system is unavailable. Improvements It is now possible to clean up old files from the output folder on Report Schedule execution. API: It is now possible to determine the status of a connection. [ReportMagic.ConnectionList: ] now supports skip and take parameters ReportMagicClient nuget package now makes a PUT request i...

Introducing... RM Scripts! With the released of ReportMagic 2.17, it is now possible to move many of the hard-to-read macros out of your Report Template (.docx or .html) document and into one or more "RM Script" files. We hope that this new feature provides a much better development experience for power developers. Script development To develop a new RM Script: Create a new file in your Input folder with an ".rmscript" file extension (e.g. "test.rmscript") Right click on the file and click "edit in Report Studio" Develop the script: Enter macros, one or more per line You can add any whitespace, including tabs, spaces and newline characters, these are all stripped out before execution You can add any other characters between the macros - these are also stripped out when executing. To test, press the play button.  Note that there is no output, but the variables in the variables are updated. Script usage To use the RM Script: In your Report Template...