Magic Suite 3.15

Magic Suite 3.15 has been released with the following changes across all products.

ReportMagic

New Features

• ReportMacroResult daily ageing is now done by ageing out the dated partition rather than removing n records from the ReportMacroResult table. This takes milliseconds rather than the many minutes it used to take previously.
• Minor capitalization changes made in the v3 and v4 LogicMonitor Healthchecks in the Library
• Added the [Microsoft.EntityPropertyList:] macro.
• The [Unset:] macro has been put in place to replace the suggested [Scope:] / [EndScope:] macros
• [MicrosoftDataverse.EntityList:] macro is present and functional
• New Tenant.MerakiDataMagicWidgetToken columns is now in the tenant database table
• Minimal Monitoring section now properly reports on those devices matching certain applies to function criteria,
• Health Check now only reports on Dynamic Device Groups that are empty,

Improvements

• Updated "Storing and Retrieving Variables" help page.
• Added various additional List.XXX macro help examples.
• [Meraki.OrganizationProperty:] now supports licensing in the property paramter
• Various Logic Monitor parameters are now deprecated
• Updated the default value for the properties parameter for all Meraki macros.
• User approval emails now add a Notification to the database which can be viewed in the Notificatons tables in the UI.
• The [MicrosoftDataverse.EntityList:] macro does now not include the entity "Properties" (just "Name") by default. They can be included by using the new parameter 'includeProperties' e.g. includeProperties=true.
• Intermittant LogicMonitor erro no longer happens with various 5 day increments.
• [LogicMonitor.DeviceCount:] speed improvement for groups with a large number of devices and no filters are applied.
• Various macros that do not work with PowerPoint and RM Script input documents now indicate that in the help.
• The [LogicMonitor.DeviceSlaWidgetProperty:] macro should now has a valid example.

Bug Fixes

• Fixed a minor issue with lifelong learner badge text.
• Fixed an issue with the use of the DatabaseConnectionID override in a LogicMonitor connection configuration (used by the DataMagicSync feature).
• The [Email:] macro now does not ignore the connectionName parameter
• New Toggl Connections now use the v9 API URL.
• Fixed an issue with the update of ReportMacroResults table partitions.
• Fixed an issue with [LogicMonitor.Dashboard:] macro when using expandWidgetLegends=true, which would fail if there just happened to be no legends on the Dashboard.
• Fixed an issue where it was not possible to submit Feedback when not logged in.
• Reinstated width and height dimensions in files browser preview panel for SVG files.
• In the Files browser, only image files previewed (in the preview panel on the right) show the "Dimensions" details (image width and height).
• Fixed various [List.XXX:] macros in light of stricter NCalc operation.
• Notifications Page help has been added to the 'Seeing How Your Report Ran' help page
• Help: embedded links now open page as expected when not in the macro help
• The [ReportMagic.SetReportProperty:] macro has an additional help example that describes how to use the property=outputFileTypes parameter (and values). Tweaked text in the help to describe valid Report Studio properties. Corrected help text / comments that mentioned incorrect values for the stopOn property.
• Embedded help links in the macro "Purpose" section now always point to the local system (and NOT always production i.e. reportmagic.net)
• The [File.Insert:] macro help now clarifies there in the file system the SVG files can be located.
• Updated help for the widgetId parameter for the [LogicMonitor.DeviceSlaWidgetProperty:] macro.
• The properties parameter for the [LogicMonitor.DeviceSlaWidgetProperty:] macro is now optional and defaults to "AllAsJObject",
• Restricted Macro help page now immediately loads without a refresh when link is clicked from the Connection Role Security help page
• DataMagic sync create/edit page now shows some help.
• The API now supports Overwriting a file if it was specifically requested
• Updated internal PDBlazor library which now has code to prevent the null object errors.
• Fixed an issue with the Variables / Details panel in Report Studio's Progress Page where it was not possible to scroll to view all the variables / details etc. in the list.
• Malformed macros are now properly shown on the progress page, with a macro error, rather than not showing up at all.
• The "file output icons" on the progress page (not in Report Studio, but just for Schedules) now show the correct tooltips indicating the name of the output file (the file extension is now correct).
• When a user is controlled by RBAC to only see certain schedules, the Batch Jobs page and the Report Jobs page are now also controlled by that RBAC so the user now only sees the Batch Jobs and Report Jobs information which relate to the schedules the user has access to.
• Fixed an issue where the Monaco editor did not work properly when setting the ReportMagic theme to dark / light.
• In dark mode, the Report Studio File menu's drop-down items now have a more suitable highlight colour (instead of almost white) which makes it MUCH easier to see the text.
• Fixed an issue where malformed macros would not be shown as a macro in the progress page / database, and would also not cause the report job to register the macro error, possibly just showing success (depending on what other macros were in the report).
• Fixed an issue where a Guid could not be output properly / formatted (even when hidden).
• [LogicMonitor.DeviceGroupList:] now returns expected results
• Fixed an issue where the [LogicMonitor.DeviceGroupList:] macro would not return the correct properties.
• Added some mitigation code to DocMagic to resolve timeout issues with the [LogicMonitor.Dashboard:] macro.
• NCalc min() now outputs as expected
• NCalc max() now outputs as expected
• The [ReportMagic.ReportConnectionSummary:] macro can now correctly output LastModifiedDateTimeUtc. The ReportJob object is no longer supported. Note that the [ReportMagic.ReportJobProperty:] as a result now also supports LastModifiedDateTimeUtc as a property.
• Fixed an issue where the [LogicMonitor.EscalationChainDestinationProperty:] macro's index parameter was not working as expected.
• The [MicrosoftDataverse.EntityList:] macro now outputs as expected into the output document.
• Fixed an issue where the search everything toolbar would have a horizontal scrollbar.
• [ReportMagic.ReportMacroCount:] macro now allows the count to be stored as a variable
• When a table is empty and EmptyTableText is used, when the spreadsheet is not produced, the warnigs for WriteToSpreadsheet and WorksheetName paraameters are suppressed.
• Updated help for [LogicMonitor.DeviceGroupList:] macro to clarify usage of property parameter in Normal Mode with type=service.
• [List.Table:] does not cause an error in PowerPoint when used with the includeCondition parameter.
• The [LogicMonitor.DeviceProperty:] macro when outputting AllAsJson now correctly reports alertDisableStatus as strings.
• Stricter NCalc evaluation has now been implemented regarding curly brackets (i.e. { }). Some previous macros which may be present in your reports may not run as they previously would have if they have incorrect NCalc with curly brackets. For example, it is no longer valid to enclose numbers in curly brackets (i.e. x>{3}) and additionally, it is no longer valid to leave stray curly brackets in the expression (i.e. x>3}). This is documented in the 'Storing and Retrieving Variables' help page.
• Fixed an issue where the [MicrosoftDataverse.EntityList:] did not indicate the correct type in the variables panel in the progress page.
• Search form text no longer scrolls behind inputs.

AlertMagic

Improvements

• On AlertMagic, the Metrics page is the only page accessible if you are a Tenant Admin.
• Homepage for logged in users has been added

Bug Fixes

• "You do not have permissions to access this page" page is shown when trying to access a page a user does not have access/permission to.

DataMagic

Bug Fixes

• A DataMagicSync database is created automatically when a suitably configured DataMagicSync is executed for the first time. Subsequent DataMagicSyncs can be executed as required to update device data source instance data points, time series aggregations and other data. The LogicMonitor connection associated with the DataMagicSync must be appropriately configured in JSON format with a valid definition of items to sync. The Cache: Server Instance, Cache: Server Password, Cache: Server Port and Cache: Server Username global settings must be properly set and create database rights granted (a PanoramicData SuperAdmin level user must do this). The database can then be queried using the [Database.XXX:] macros once a suitable connection to the DataMagicSync database has been created in ReportMagic.