| 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-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-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-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-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-25196 |
Major |
Correct the Meraki Connections help page: wrong defaults for MaxAttemptCount and HttpClientTimeoutSeconds, and obsolete ApiNode guidance |
The help page for Meraki Connections has been corrected. It previously gave the wrong default values for the retry limit and the HTTP timeout, and recommended the ApiNode setting, which no longer has any effect since Cisco withdrew shard-direct API access in September 2025. If you have ApiNode in a Connection's Configuration, you can safely remove it. The page now also explains how to generate a Meraki API key in the Meraki Dashboard, which failures are retried and which are not, why a single Meraki call can run for several minutes if the retry settings are left at their defaults, and how rate limiting keeps you within Meraki's own limits. A new worked example gives a sensible starting configuration for a new Meraki Connection. | 4.4.900 |
| 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 |
| MS-24356 |
Trivial |
Docs: the macros count in the tree node (ReportMagic > Macros section) should be readable (white text) when the node is selected |
In the documentation tree, the item count shown next to a node - for example "Macros (566)" - is now white when the node is selected, making it easy to read against the blue highlight in both light and dark modes. | 4.4.318 |
