Magic Suite 3.12

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

ReportMagic

New Features

• The [ReportMagic.SetReportProperty:] macro now supports the outputFileTypes value for the property= parameter (not applicable in Report Studio) which allows different types of output files to be selected during a report, dynamically. Note that for XLSX output, the XLSX tab MUST however be enabled on a Schedule if you want to output XLSX.
• Added the optional 'clientApiId' parameter to the [CloudHealth.AvailableReportOptions:] macro.
• Added the optional 'apiClientId' parameter to the [CloudHealth.AvailableReportDimensions:] macro.
• Added the [CloudHealth.AvailableReportDimensions:] macro.
• Various [List.XXX:] macros now support the condition parameter

Improvements

• LogicMonitor connection status (red/green) is returned within seconds (near instantaneously when the connection is not valid).
• The Files Preview panel now provides a preview of .zip files, presenting a table describing the name, size, and compressed size of each item inside the zip archive. Only files less than 25 MB will be previewed. Files larger than that displays a suitable reason why the preview is unavailable.
• The Preview panel in the Files browser now supports Powershell (PS1), SVG, PDF (first page shown as an image), and XML files.
• The Files Preview panel now shows the contents of json, png, and jpg files.
• The [LogicMonitor.PropertySourceList:] macro now supports multiple properties.
• The [LogicMonitor.UnmonitoredDeviceList:] macro now supports multiple output properties in the 'properties' parameter.
• In Normal Mode, invalid string properties (in the property/properties parameter) for the [LogicMonitor.WebsiteList:] macro now almost immediately result in a macro error (and helpful message of which are incorrect, and available options) instead of waiting for the macro to fetch its data first. I.e. if it should fail, it fails much quicker and is more helpful.
• When a property or properties parameter is specified with invalid value e.g. property=I DO NOT EXIST, the resultant error message (which lists available properties on an object) now orders them alphabetically.
• The [LogicMonitor.LogicModuleMetadata:] macro now supports multiple properties. In Normal Mode it now emits a JObject that contains property names and values. Updated help examples.
• The [LogicMonitor.LogicModuleUpdateProperty:] macro now supports multiple properties.
• The [LogicMonitor.LogicModuleUpdateList:] macro now supports multiple properties.
• The LogicMonitor.NetscanGroupList macro now supports multiple properties (Legacy Mode / Normal Mode).
• The LogicMonitor.NetscanGroupProperty macro now supports multiple properties. In Normal Mode it now emits a JObject with property names and values.
• The [LogicMonitor.NetscanList:] macro now supports multiple output properties via the properties / property parameter.
• The [LogicMonitor.NetscanProperty:] macro now supports multiple properties. In Normal Mode, it now emits a JObject with property names and values.
• The [LogicMonitor.NewUserMessageProperty:] macro now supports multiple properties using the 'properties=' parameter. In Normal Mode, it now emits a JObject with property names and values.
• The [LogicMonitor.PortalVersion:] macro now supports multiple properties. The BuildAt and ResultKey properties were added. In Normal Mode it now emits a JObject that contains property names and values.
• The [LogicMonitor.PropertySourceProperty:] macro now supports multiple properties, and in Normal Mode now emits a JObject that contains property names and values.
• The [LogicMonitor.RecipientGroupList:] macro now supports multiple properties. The Recipients property is now delimited by | instead of ^ in Legacy Mode.
• The [LogicMonitor.RecipientGroupProperty:] macro now supports multiple properties, and in Normal Mode emits a JObject with property names and values.
• The [LogicMonitor.RecycleBinItemList:] macro now supports multiple properties.
• Emails sent to notify of a new user awaiting approval for ReportMagic now includes the environment.
• The [ReportMagic.Version:] macro now supports multiple properties. In Normal Mode, it now emits a JObject with property names and values. Also added the 'AllAsJObject' value that can be used in the property parameter.

Bug Fixes

• Fixed an issue where the Configuration, Description, Username and Password fields in the edit/create dialog may not behave as expected.
• The Admin => Connection Roles create/edit dialog now behaves as expected.
• Opening a Word (.docx) file from a SharePoint drive, in Report Studio, now works as expected - i.e. converts to HTML then displays it in the editor.
• Double-clicking a Word document (.docx) in the Files browser now downloads the file instead of opening to edit in Report Studio.
• PDF and Word files that are previewed in the Files browser no longer prevent the files from being deleted.
• Fixed an issue where in the Files browser preview panel, when selecting PDF files in a SharePoint location, the automatically-generated preview would cause an error pop-up and fail to preview the file.
• In the Files browser, selecting a file without a file extension no longer causes an error.
• The [LogicMonitor.Threshold:] macro help page lists the supported properties.
• Fixed an issue where the [LogicMonitor.RoleList:] and [LogicMonitor.RoleProperty:] macros would always generate a Macro Error.
• Fixed an issue where the [LogicMonitor.UserList:] and [LogicMonitor.UserProperty:] macros would always generate a Macro Error.
• When various UI tasks might be cancelled in relation to updating the URL in the browser, there is now no longer exception pop-ups.
• Fixed an issue where the My API Tokens page would not display JUST My Tokens for TA/SA/UA users.
• It is now possible to add/edit description in the API Token create/edit dialog.
• In Normal Mode, [List.Complement:], [List.Union:] and [List.Intersection:] macros now produce the correct output when the input values are JArrays or JObjects, etc.
• Fixed a regression in the [List.xxx:] macros in Normal Mode where a null was being output when it should have been empty strings.
• Fixed an issue where Tenant Admins were not able to manually create new users.
• Updated the LogicMonitor API nuget to better detect rate limiting messages.
• Fixed an issue where, when the HubSpot API key was invalid, and the Refit API Exception was not handled, it would prevent a new user registering properly on a new Tenant.
• Fixed an issue where the [LogicMonitor.ReportList:] macro would, in Legacy Mode, produce incorrect output.
• Fixed an issue where the [Graph.DeleteData:] macro would not correctly update the embedded XLSX file (the data linked to the chart object), and also generate a macro error. Despite this, the chart looked OK when opened in PowerPoint, BUT by clicking 'Edit' on the chart, the erroneous data would be revealed and PowerPoint would automatically update the chart with those wrong values.
• Fixed an issue where the [LogicMonitor.SdtList:] macro, in Normal Mode, would not output the correct values when the property 'AllAsJson' / 'AllAsJObject' were used.
• It is now not possible to create a Macro Default with the type 'Unknown'.
• Fixed LogicMonitor.SdtProperty that was reporting a system error on a device when property=DeviceGroupFullPath.
• Fixed an issue where cancelling a running batch job wouldn't always complete the cancellation process.
• Fixed an issue where notify on XXX settings that cause an email to be sent (notify only, not stop) should not say in the email that the report has stopped.
• Fixed an issue with the [LogicMonitor.AlertStatus:] macro where a device with a warning status would fail to output correctly when outputType=Int32.
• Fixed an issue where a user could not choose a Tenant (when multiple Tenant domains are relevant) when attempting to sign in.
• Fixed an issue with Schedules, where an incorrect batch variable would be created (formatted as JSON / JObject) when the HTML form is empty (e.g. just used as a trigger and only contains the Cancel / Submit buttons).
• In Normal Mode, the [LogicMonitor.JobMonitorList:] macro now emits a JArray of JObjects ecah of which contains property names and values. Multiple properties are now supported.
• In Normal Mode, the [LogicMonitor.JobMonitorProperty:] macro now emits a JObject that contains property names and values. Multiple properties are supported.
• In Legacy Mode. the [LogicMonitor.DashboardWidgetList:] macro now outputs the entire output in one set of json tags when requesting properties=AllAsJson.
• When adding a new macro default for Agent.Connection, it is now correctly added as an Agent.Connection type and not the deprecated AccountProperty type.
• Fixed broken [LogicMonitor.LogicModuleUpdateList:] macro due to changes in the LogicMonitor API.
• Fixed an issue with the [LogicMonitor.Dashboard:] macro where the shapeId parameter was used (for DOCX output) but the shape was not being filled with the dashboard image.
• Fixed an issue where the imageWidthCm and imageHeightCm parameters had no effect for Word / HTML output when using the [LogicMonitor.Dashboard:] macro.
• The [Json.Item:] macro now results in a macro error rather than a system error, when the jsonPath parameter is incorrectly specified.
• When using NCalc expressions in parameter values, and the expression attempts to use a predefined variable that does not exist, there is now a macro error rather than a system error.
• In Normal Mode, the [LogicMonitor.RecycleBinItemProperty:] macro now emits a JObject with property names and values. Multiple properties are also supported in Legacy Mode and Normal Mode.
• The [LogicMonitor.ReportGroupList:] macro now supports multiple properties via the properties parameter. In Normal Mode, it now emits a JArray of JObjects that each contain property names and values.
• The [LogicMonitor.ReportGroupProperty:] macro now supports multiple properties via the properties parameter. In Normal Mode, it now emits a JObject that contains property names and values.
• In Normal Mode, the [LogicMonitor.ReportList:] macro now emits a JArray of JObjects each containing property names and values. It also support multiple properties in Legacy / Normal modes.
• In Normal Mode, the [LogicMonitor.ReportProperty:] macro now emits a JObject that contains property names and values. It also now supports multiple properties (in all Legacy / Normal mode).
• The [LogicMonitor.RoleList:] macro now supports multiple properties via the 'properties' parameter. In Normal Mode, it now emits a JArray of JObjects that each contain property names and values. Also removed the 'unknown' property that served no purpose. Also added the propertyDelimiter and subListDelimiter for Legacy Mode only.
• The [LogicMonitor.RoleProperty:] macro now supports multiple properties. In Normal Mode, it now emits a JObject that contains property names and values.
• The [LogicMonitor.SdtProperty:] macro now supports multiple properties. In Normal Mode, it now emits a JObject that contains property names and values.
• The [LogicMonitor.SingleSignOnProperty:] macro now supports multiple properties, and in Normal Mode now emits a JObject that contains property names and values.
• The [LogicMonitor.SnmpSysOidMapList:] macro now supports multiple properties. In Normal Mode, this macro now emits a JArray of JObjects each of which contain property names and values.
• The [LogicMonitor.SnmpSysOidMapProperty:] macro now supports multiple properties. In Normal Mode, it now emits a JObject that contains property names and values.
• The [LogicMonitor.UnmonitoredDeviceProperty:] macro now supports multiple properties, and in Normal Mode outputs a JObject that contains property names and values. Updated help examples.
• The [LogicMonitor.Threshold:] macro now outpts a JArray with JObjects with name/value pairs in normal mode.
• The [LogicMonitor.UserApiTokenList:] macro now supports multiple properties. Also outputs a JArray of JObjects.
• The [LogicMonitor.UserApiToken:] macro now supports multiple properties via the 'properties=' parameter. It also now emits a JObject that contains the requested property names and values.
• In Normal Mode, the [LogicMonitor.UserList:] macro now emits a JArray with JObjects with property names and values. It also (both modes) supports multiple properties.
• The [LogicMonitor.UserProperty:] macro now supports multiple properties. In Normal Mode, it now emits a JObject with property names and values.
• In Normal Mode, the [LogicMonitor.WebsiteProperty:] macro now emits a JObject that contains property names and values.
• In Normal Mode, the [LogicMonitor.WebsiteGroupList:] macro should emit a JArray of JObjects that contain property names and values. Multiple properties should also be supported.
• The [LogicMonitor.WebsiteGroupProperty:] macro now emits a JObject that contains property names and values in Normal Mode. It also now supports multiple properties.
• The [LogicMonitor.WidgetStatus:] macro now outputs a JObject in Normal Mode, which contains 2 property names / values: StatusCode and Message.
• In Normal Mode, the [Meraki.DeviceProperty:] macro now emits a JObject that contains property names and values.
• In Normal Mode, the [Meraki.NetworkProperty:] macro should emit a JObject that contains property names and values.
• In Normal Mode, the [Meraki.OrganizationLicenseStateProperty:] macro now emits a JObject that contains property names and values.
• In Normal Mode, the [Meraki.OrganizationProperty:] macro now emits a JObject that contains property names and values.
• When an Admin level user is searching the Audit Logs it is now possible to cancel the search.
• [File.Execute:] now does not not cause // corruption due to the / character and processes all macros behind </json>
• The [ReportMagic.SystemProperty:] macro now supports multiple properties (and added AllAsJObject property). In Normal Mode, it now emits a JObject with property name / value pairs. In Legacy Mode, each property is delimited by a semicolon and output as a string. This macro no longer requires a ReportMagic Connection to work.
• "Please complete the highlighted fields to continue" added to Schedule edit/create dialog to ensure you know there is a field left to complete before saving
• The Macro Results page filters now work as expected.
• Skip and take parameters now work correctly with the [Slide.Repeat:] macro.
• When there are duplicate Devices (same IP / DNS name) erroneously configured in the LogicMonitor portal, the [LogicMonitor.HistoricSdtList:] macro (and any others that use deviceName) now produce a macro error rather than a system error.
• Fixed an issue that caused an error to be reported when clicking between Admin menu items.
• The [Meraki.OrganizationDeviceLicenseList:] macro does now not not generate a system error (rather, a macro error) when specifying an organization ID that does not support per-device licensing.
• Bold now renders in first iteration of a ForEach loop
• Fixed broken [LogicMonitor.WebsiteGroupList:] and [LogicMonitor.WebsiteGroupProperty:] macros, when using any of these properties in legacy mode: AlertDisabledOn, ChildWebsiteGroups, or CustomPropreties.
• Regular users can now delete their own API tokens.
• Fixed an issue which was causing [LogicMonitor:XXX] macros to fail.

AlertMagic

New Features

• Added an endpoint to allow AlertMagic to sent metrics.
• Fixes for Incident Spec Mapping form.
• Fixes to incident spec comment form.
• Fixes to edit incident spec action in Alert Studio.
• Fixes to Incident Spec edit form.
• Removed the Scope property from the EventManagerConstant entity.
• It is now possible to view, edit, and create Cached Snippets in the Alert Studio => Inputs => Cached Snippets tab / table. Changes are saved to the database when the Version is saved.
• The Inputs => Snippets tabs works as expected.
• The Alert Studio -> Inputs -> Fields tab now shows the names, types, and values from detected fields in the Inputs -> Payload tab.
• Alert Studio -> Inputs -> Payload tab is now functional.
• Added the Inputs sub-tabs on Alert Studio's Inputs tab.
• It is now possible to publish / active an EventManager version using Alert Studio.
• Fixed an issue where an EventManagerVersion with Calculations (cached snippets) could not be saved / saved as new version.
• The Deployment Targets page has been implemented.
• Initial screen layout of Alert Studio. Also implemented some basic mobile-view responsiveness (which is not perfect, but acceptable for now). Icons may change.
• The AlertMagic UI now correctly uses the AlertMagic favicon in the browser, rather than the default Blazor one.

Improvements

• Fixed a security vulnerability where the integration credential generation endpoint was susceptible to XSRF attacks.
• AlertMagic now generates stronger, more secure passwords for integration credentials with increased entropy.
• Removed "IntegrationName" from the EventManager entity.
• Removed unnecessary automapper calls in startup project for the Web.Api.
• Moved the AlertManagementSystemId and IncidentManagementSystemId (and navigation properties) from EventManagerVersion to EventManager, as well as Constants.
• The Integrations created / edit screen cannot be navigated to when there is not at least one AMS, IMS and Deployment Target (Instance). The New button is disabled, and a pop-up is shown with links to those pages.
• Charts on the Metrics page now auto-update every 2 minutes.
• Added Actions to EventManagerProblemSpec via a migration.

DataMagic

Improvements

• The title of the Create dialog on the Admin => DataMagic Syncs page is now "Create new DataMagic Sync" rather than "Create new DataMagicSyncViewModel".

Bug Fixes

• The Admin => DataMagic Syncs create dialog now behaves as expected.
• Report Schedule triggered by DataMagic Sync now uses the specified Batch Variables rather than the DataMagic Sync definition
• When a DataMagicSync is the target chained sync for another DataMagicSync, and it is deleted, the referring one should have its chained sync ("DataMagic Sync to Trigger") set to null / none
• When a DataMagicSync has been cancelled via the UI, any chained Schedules or DataMagicSyncs will not be triggered.
• The DataMagic Sync Executions can now be successfully cancelled.