New Features (9)
| Ticket | Severity | Summary | Notes | Version | |
|---|---|---|---|---|---|
| MS-24565 | Blocker | Report Schedule forms should provide the ability to load data from the Cached Values table | Report schedule forms can now load data from cached values and make it available to the form's own JavaScript. This lets a form be driven by data your reports have already produced (for example, populating a drop-down from a cached list) instead of hard-coding it. Values a schedule is not permitted to access are shown as an error within the form and are never exposed. Cached values can be set by macros (such as Cache.Set) in your reports, or in the Admin app via the Products > ReportMagic menu and choose Cached Values. Whilst mostly used for internal reports with forms, you can design your own Schedule forms that make use of this functionality. More details are in the docs app here: https://docs.magicsuite.net/ReportMagic/Reports/ScheduleForms | 4.4.559 | |
| MS-24640 | Blocker | Library Report: Meraki WAN utilization (4.4) | A new Meraki WAN Utilization report is now available in the Report Library. It shows how heavily each of your Meraki WAN uplinks is used against its configured bandwidth limit over the period you choose, separately for upload and download. You get an Excel workbook with two views: how often each uplink was near its limit (the share of the period it spent above 90%, 80% and 70% of the limit) and how close it came at its busiest, with the most stressed uplinks colour-coded and listed first. You can choose the reporting period and have the report emailed to you. | 4.4.850 | |
| MS-12906 | Major | [LogicMonitor.AppliesToList:] macro should support multiple properties | The LogicMonitor.AppliesToList macro now supports returning multiple properties per matching resource. Set property=Id,Name (or any combination) in Normal mode to include more than one field in the output. Legacy mode continues to work as before, using a single property. | 4.4.177 | |
| MS-24648 | Major | The new Schedule Run Metrics Analysis (Compare Runs) should be accessible by Tenant Admins (not just Super Admins) | Tenant Administrators can now use Compare Runs to check the health of a scheduled report. It compares the latest run against the previous one, highlighting changes in duration, file transfer times, and item counts, so you can quickly spot anything unusual without digging through individual batch jobs. | 4.4.603 | |
| MS-16174 | Major | Database macros that encounter an SQL error should provide more useful error messages | When a [Database.XXX:] macro encounters a SQL syntax error, the error message now includes a short extract of the SQL surrounding the problem location. This makes it much easier to identify and fix the issue directly in Report Studio, without having to manually count characters through a long query. | 4.4.177 | |
| MS-24340 | Major | ReportMagic: Schedule Creation Wizard | Creating a new Schedule is now easier with a step-by-step guided wizard. It validates your settings as you go, and shows a summary to review before the Schedule is created. | 4.4.263 | |
| MS-14573 | Major | The [Database.Table:] macro should provide a way to exclude certain columns from the output | The Database.Table macro now supports three new optional parameters (excludeColumns, excludeColumnsExpression, and ExcludeEmptyColumns) to filter out unwanted columns from SQL query results: exclude specific columns by name, exclude columns whose name matches an expression, and automatically exclude columns that contain no data. | 4.4.177 | |
| MS-19095 | Major | The [List.GroupBy:] macro should be able to do Min and Max aggegations on dates | In the [List.GroupBy:] macro when using Normal Mode, Min and Max aggregations now work on dates and strings, not just numbers. | 4.4.318 | |
| MS-2408 | Major | The [Email:] macro should have a new parameter (sendIfContainsErrors) that can prevent it being sent if the report contains errors | The [Email:] macro has a new 'sendIfContainsErrors' option that prevents the email from being sent if an error occurs anywhere within the section between the [Email:] and [EndEmail:] macros. | 4.4.318 |
Improvements (12)
| Ticket | Severity | Summary | Notes | Version | |
|---|---|---|---|---|---|
| MS-15812 | Critical | Batch Jobs should not be able to run indefinitely without a timeout | Occasionally a report could stay shown as Running indefinitely if its processing was interrupted (for example, during a system update), even though it had actually stopped. Magic Suite now automatically detects reports that are no longer being processed and marks them as stopped, so your reports list stays accurate. Reports that are genuinely still in progress are never affected, however long they take to run. | 4.4.381 | |
| MS-24727 | Critical | ReportMagic: a Schedule's chained Schedule should not automatically be triggered in a re-run - it should be an option and default to false | Re-running reports no longer runs a chained Schedule by default, so recipients are not sent an unexpected extra report. When a Schedule is chained, the Re-run dialog now includes a 'Chained Schedule' option (off by default) so you can choose to run it as part of the re-run. Normal scheduled runs and the Run button are unchanged. | 4.4.748 | |
| MS-24740 | Major | Table macros should be able to colour the Excel worksheet tab (worksheetTabColor parameter) | Reports can now colour-code the worksheet tabs of an Excel workbook, so a red tab can flag a sheet that needs attention instead of every tab looking the same. | 4.4.677 | |
| MS-24743 | Major | The [ReportMagic.SetReportProperty:] macro should provide the ability to reposition a named worksheet (move to start / move to end / before / after) | Excel reports can now control the order of worksheet tabs using the [ReportMagic.SetReportProperty:] macro (or MagicSuite.SetReportProperty:] macro. New report properties let you move a named worksheet to the start or end of the workbook, or place it immediately before or after another named worksheet - handy for putting a summary or overview sheet first, even when it is built after the other sheets. Setting a worksheet as the active tab now always resolves correctly too, no matter what order that is combined with a worksheet move. | 4.4.748 | |
| MS-24535 | Major | Add the column-group selector to wide Admin, ReportMagic and shared Notification tables | Wide tables across the Admin app, ReportMagic and the Notifications view now have a 'Columns:' selector above them - including DataMagic Syncs, Notifications, Report Jobs and Batch Jobs. Pick a group of related columns to focus the table on what you need, or 'All' to see everything, instead of scrolling sideways through dozens of columns. The key identifying columns always stay visible whichever group you choose. | 4.4.465 | |
| MS-12838 | Major | The [List.Dequeue:] macro example should be updated (clearer usage, more complete) | Fixed an incorrect help example for the [List.Dequeue:] macro. | 4.4.177 | |
| MS-22812 | Major | [Database.List|Value|Values] macros should return values of given type returned by the DB query (Normal Mode) | The [Database.Value:] and [Database.Values:] macros now support native typed values - so integers, booleans, decimals and dates (and more) can be passed through as their native types rather than being converted to strings. To use this, add `mode=Normal` to the macro. Legacy mode (the default) retains the previous string-only behaviour, so existing reports are unaffected. If you need to force string output even in Normal Mode, add `allAsStrings=true`. | 4.4.125 | |
| MS-24385 | Major | [List.Sort:] macro should offer a Natural sort type for human/version-aware ordering | Lists can now be sorted in 'Natural' order, so text containing numbers sorts the way people expect: Item2 comes before Item10, and version numbers like v1.2, v1.9, v1.10 line up correctly. It is an optional choice available wherever you sort a list, and existing sorts are unaffected. | 4.4.318 | |
| MS-23214 | Major | Admin > ReportMagic > Macro Parameter defaults form should validate the value based on the type of parameter | When setting default values for macro parameters, the form now shows the appropriate input control for the type of value expected - a toggle switch for yes/no parameters, a number input for numeric parameters, and a colour picker for colour parameters - rather than a plain text box for everything. | 4.4.263 | |
| MS-24739 | Major | Report Library Schedules that use a pop-up form should let you pick a Connection from a list instead of typing its name | Report Library forms can now offer a Connection drop-down, letting you pick from the Connections available to you instead of typing the exact name. It is being rolled out report by report, so some forms may still use a plain text box for now. | 4.4.677 | |
| MS-24621 | Minor | The ReportMagic help's macro category list table should show the 'Updated' badge | The 'Updated' indicator for recently-changed ReportMagic macros now also appears in the macro category list on the documentation site and in the Report Studio macro picker, matching the indicator already shown elsewhere in the product. | 4.4.586 | |
| MS-24622 | Minor | The Report Studio macro picker pop-up should show the 'Updated' badge for macros that have been updated | The 'Updated' indicator for recently-changed ReportMagic macros now also appears in the macro category list on the documentation site and in the Report Studio macro picker, matching the indicator already shown elsewhere in the product. | 4.4.586 |
Bugs Fixed (24)
| Ticket | Severity | Summary | Notes | Version | |
|---|---|---|---|---|---|
| MS-24551 | Blocker | The [DocumentBreak: type=LineBreak] macro should not fail on a second call | Fixed a macro error that could occur when two DocumentBreak macros were used next to each other and the second macro's text spanned more than one line in the template. | 4.4.559 | |
| MS-24854 | Critical | ReportMagic: the [LogicMonitor.SdtList:] macro should not fail when an SDT's date time properties from LogicMonitor are invalid or malformed | Fixed an issue where a report could show an error retrieving Scheduled Down Time (SDT) information from LogicMonitor if one of the SDT records had an invalid date. The report now skips the invalid record and continues as normal. | 4.4.883 | |
| MS-24192 | Major | .ncalc Schedule Batch Execution: macro tooltip on progress page should just show the duration | Macro tooltip on progress page when running .ncalc files now just shows the duration. | 4.4.177 | |
| MS-24751 | Major | [List.Dequeue:] help examples should not use "=>StoreAsHidden=X" | Corrected the [List.DequeueMacro:] examples to use the correct shorthand syntax. | 4.4.825 | |
| MS-24811 | Major | DatamartClient: 'SNMP_SYSOID_MAP' from LogicMonitor API should be deserialized correctly | Fixed an issue where LogicMonitor DataMart syncs could fail when the LogicMonitor API returned certain device module types (e.g. SNMP SysOID Map) that weren't recognised during processing. | 4.4.850 | |
| MS-24679 | Major | When the [Web.Screenshot:] macro times out, it should produce a macro error rather than a system error | Fixed an issue where a [Web.Screenshot:] macro that took too long to load was reported as a system error. It's now correctly reported as a macro error, with a clear message explaining that the page timed out. | 4.4.850 | |
| MS-24541 | Major | [Agent.Property:] isConnected should not report True when disconnected / not configured | Fixed an issue where the Agent connection status could incorrectly show as connected, even when the Agent was unreachable or not set up. | 4.4.493 | |
| MS-15895 | Major | In Normal Mode, the [LogicMonitor.SlaWidgetValues:] macro should emit a JArray with jObjects with multiple name/value properties | The LogicMonitor.SlaWidgetValues macro has been updated to work seamlessly in Normal Mode, returning structured data that can be accessed using standard dot-notation (e.g. [.:Items[0].BottomLabel]). Property names can now be renamed inline using the as syntax (e.g. Value as Availability), making it easier to build clean, readable reports. The macro documentation has also been improved with clearer examples and guidance on how to locate Widget IDs in the LogicMonitor portal. | 4.4.125 | |
| MS-24731 | Major | CertificateTemplate document should not error when trying to download the input document via the Report Jobs page | Fixed an issue where the input document for exam-pass certificate emails could not be opened from the Report Jobs page. | 4.4.677 | |
| MS-24101 | Major | The [LogicMonitor.UserList:] macro should not produce a macro error due to internal de-serialization issues (missing members) | Fixed an issue where the [LogicMonitor.UserList:] macro was broken due to changes in the LogicMonitor API. | 4.4.75 | |
| MS-24056 | Major | The [LogicMonitor.UserList:] macro should not generate a Json serialization macro error | Fixed an issue where the [LogicMonitor.UserList:] macro was broken due to changes in the LogicMonitor API. | 4.4.75 | |
| MS-24208 | Major | [Array:] macro should accept the 'storeAs' parameter, and any output variable produce should not be missing from the Progress Page variables list (and database) | The [Array:] macro now accepts the StoreAs parameter, matching the behaviour of other macros such as [String:]. Previously, only the => shorthand worked. Using storeAs= directly would produce an error. Array variables stored by this macro are now also visible in the report progress page. | 4.4.177 | |
| MS-24404 | Major | Macros should not show the unknown (ban) icon in the Docs app and Report Studio macro list / help | Macro help pages now display the correct icon for every macro. Previously a handful of macros (including the SolarWinds Service Desk, Zoho Desk, Google, and ServiceNow macros, among others) showed a generic "no icon" symbol in the macro help and Report Studio macro list; these now show a meaningful icon that reflects what each macro does. | 4.4.318 | |
| MS-12817 | Major | The [Jira.IssueProperty:] macro using tickets which contain macros in the summary should format correctly without ♣/♧ | Fixed an issue where emails sent by the [Email:] macro could show odd symbols (such as the club characters) instead of square brackets when the emailed content included text containing a macro name - for example a Jira ticket summary. Such text now appears correctly with normal square brackets. | 4.4.318 | |
| MS-14050 | Major | Invalid Connections should have an icon (badge) when invalid or partially valid | The Files view now shows a warning indicator on any file system connection that the system has detected as unavailable or degraded. An amber triangle indicates a partially working connection, while a red triangle indicates a connection that is currently invalid - for example, an SFTP server with incorrect credentials. Hovering over the badge shows a tooltip confirming the status. This means you no longer need to visit the Connections page to discover why a file system folder isn't behaving as expected - the issue is now visible at a glance directly in the Files view. Note that the status is checked periodically in the background, so the badge reflects the state as of the last scheduled check (up to around 30 minutes between checks). | 4.4.177 | |
| MS-16510 | Major | ReportMagic: Progress Page table filters (on the Reports table) should work as expected | Eliminated pop-up errors on various report job table filters on the progress page. | 4.4.45 | |
| MS-24490 | Major | Docs: [Meraki.OrganizationUplinkUsage:] help example should use the correct macro | Corrected the help example for the [Meraki.OrganizationUplinkUsage:] macro. | 4.4.399 | |
| MS-24469 | Major | The [MagicSuite.ReportJobProperty:] macro should not give a system error, and should provide a better error message when using an invalid / not present Report Job | The MagicSuite Report Job, Batch Job and Feedback property macros now show a clear error message - including the Connection name - when you reference an ID that does not exist, instead of failing with a system error. | 4.4.381 | |
| MS-24371 | Major | The [AlertMagic.Statistics:] macro examples 1 and 3 should be updated | The built-in usage examples for the AlertMagic Statistics macro have been corrected. Example 1 now shows how to use DateTime macros to set a dynamic date range rather than hardcoded dates. Example 3 now uses the correct property names when referencing statistics output in a report. | 4.4.318 | |
| MS-16929 | Major | [Cisco.SerialNumberProperty:] macro should not error then succeed on next attempt | Cisco macros now automatically retry on transient failures, reducing errors caused by temporary network issues or API timeouts without any configuration changes required. | 4.4.177 | |
| MS-24566 | Major | [LogicMonitor.LogicModuleUpdateXXX:] macros should not fail with "bearerToken may not be null or empty" | BREAKING CHANGE: Because LogicMonitor retired the API that the LogicMonitor Logic Module Update macros relied on, these macros now use LogicMonitor's current module data instead. As a result, some properties have been renamed or removed, and useful new ones have been added - including whether a module has an update available, and whether it is in use or deprecated. Reports that use the LogicMonitor Logic Module Update List or Property macros may need their property names updated. | 4.4.603 | |
| MS-24543 | Minor | ReportMagic: Schedule 'Form HTML File' picker should also list .htm files (currently only .html is selectable) | Fixed an issue on the create / edit Schedule dialog, where choosing an optional HTML form file would only show files that ended in .html rather than allowing both .html and .htm files to be viewed / selected. | 4.4.493 | |
| MS-24571 | Minor | Docs: fatalIf parameter misclassified in Behaviour category (should be Conditional Formatting) | The fatalIf parameter is now classified as conditional formatting in the macro help (docs app) rather than behaviour category. | 4.4.559 | |
| MS-24574 | Trivial | Docs: [MagicSuite.BadgeList:] awardLevel parameter should not be misclassified in the Conditional Formatting grouped section of the help | The awardLevel parameter for the [MagicSuite.BadgeList:] macro is now classified as being in the Output category in the macro help in the Docs app, rather than the Conditional Formatting category. | 4.4.559 |
