Magic Suite

It's here ! ReportMagic 3 has many improvements, the most far-reaching of which are detailed below. New Features Single Sign-On (SSO) ReportMagic Version 3 uses "Microsoft Sign-In" to authenticate you using your existing company Microsoft account and log you in seamlessly.  Please note that we do not support personal Microsoft accounts. As always, new users must be authorised by a Admin from your company. If your email domain is new to ReportMagic, we will create you a starter account on a “Pro Zero” subscription once you have signed the Terms of Service. If you require integration with a different Single Sign On provider, please let us know. SharePoint integration  You can add a SharePoint connection which then appear as a “mount point” in Files. Template and other input files as well as output can be viewed and edited on your local machine from a OneDrive folder. Instructions for your Azure Administrator are here:  https://reportmagic.net/help/connecting_sharepoint ...

ReportMagic 2.28 ReportMagic 2.28 is the last version 2 release before we move to ReportMagic 3 (see below).  Don't worry, though - you will still be able to use version 2 at  https://v2.reportmagic.net/  for at least three months.  The release notes: Bug Fixes  Fixed an issue causing report jobs could execute twice, slowing report output creation Fixed an bug where the [File.Execute:] macro could incorrectly execute .rmscript files Fixes to [LogicMonitor.AlertAnalytics:] macro Fixed a bug preventing .rmscript files from being opened in Report Studio Fixed an issue causing corrupt XLSX output when an output table was empty Fixed an issue preventing [SolarWinds:] macros from executing Help pages - several minor corrections Increased the assigned development priority of customers feedback Retired Features The Dashboard feature has been retired. ReportMagic 3 Introduction ReportMagic 3 is already available for your use at https://v3.reportmagic.net/ .  As...

ReportMagic 2.27 ReportMagic 2.27 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 (see below), which offers significant scalability and architectural benefits. Improvements The LogicMonitor connection cache now supports Postgres connectivity ReportMagic support are now able to e-mail users who have recently logged in The [LogicMonitor.AlertAnalysis:] macro no longer generates an error when no alerts are found Bug Fixes and Other Work  Help has been updated for Microsoft DataVerse and many LogicMonitor macros Addressed case sensitivity issue within certain LogicMonitor macros parameters Reduced the execution time of the [LogicMonitor.DeviceList:] macro [Agent.SqlValue:] back-off / retry fixes improve macro reliability Fixed a issue with the execution of automatic Report Schedules Resolved a transient error with the [LogicMonitor.DeviceList:] macro Fixed an issue with the incorrect inheritanc...

ReportMagic 2.26 ReportMagic 2.26 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 (see below), which offers significant scalability and architecture benefits. Improvements Microsoft Dataverse connectivity and macros are now supported. The condition parameter is now supported by the [Break: ] and [Continue: ] macros within a [ForEach:]. Benefits in retry and error handling introduced by recent changes to the Toggl API have been incorporated into the [Toggl.TimeEntryProperty:] macro. Output from the [LogicMonitor.AlertCalendar:] macro can now be rendered in report documents. Bug Fixes and Other Work  An audit of all [LogicMonitor:] macros and their help examples has been undertaken, with amendments made where appropriate. Fixes to initialisation errors when running certain report schedules. Macros that return multiple outputs now support the use of non-standard delimiters. An updated LogicMon...

ReportMagic 2.25 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 It is now possible to use the [Jira.IssueList:] and [Jira.IssueProperty:] macros to report Jira time tracking data using the additional properties: OriginalEstimateInSeconds RemainingEstimateInSeconds TimeSpentInSeconds The Release Notes page now shows issues resolved since the release of Report Magic v2.20 The new [Table.MergeCells:] macro merges table cells whose content is identical across columns Added RMScript support for multi-line macros A [LinearRegression:] macro has been provided for the analysis of date-value pairs of list data. The [LogicMonitor.AppliesToList:] macro gains skip and take parameter support. The new Macro shorthand feature is now documented Bug Fixes and Other Work  [Toggl:] macros now mitigate the rate limiting imposed by t...

ReportMagic 2.24 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:] now supports two new aggregations: MinDateTime and MaxDateTime, which return the Date Time (UTC) of the first instance of the min/max value. Significant improvements have been made to the alert tuning data handling of the [LogicMonitor.Threshold:] macro.  The introduction of a properties parameter allows for any combination of the Comparator, WarningValue, ErrorValue and CriticalValue to be returned at once.  Other rework means that the macro can now report thresholds at the Global, DeviceGroup, DataSource and DataSourceInstance levels in accordance with the precedence assigned within the LogicMonitor portal. [AutoTask.TicketProperty:] macro now supports many more properties, including CreateDate. ReportMagic RmS...

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...