ReportMagic 3.4

Overview

ReportMagic 3.4 is now released and contains new features, improvements and bug fixes.

New Features

  • Added the [List.Dequeue:] macro which can be uses to process FIFO lists.  
  • The [ForEach:] and [RepeatRow:] macros now work when items contains a backtick. 
  • The regression test feature's diff.png.zip output now shows metrics where pages differ and the severity.
  • The [Shape.SetProperty:] macro now sets Word shape properties.
  • Workers now display heartbeat information including time last detected and a warning triangle when a thirty second threshold is breached.
  • Graph macros now support the axis style controls xAxisLineWidth, xAxisLineColor, xAxisLineStyle, yAxisLineWidth, yAxisLineColor and yAxisLineStyle macro parameters.
  • The API subscriptions endpoint is now available.

Improvements

  • The [ServiceNow.List:] macro will now attempt 5 retries (with 10 second delay between each) if the server responds with resource temporarily unavailable.
  • Added more [List.Table:] help examples that show use of the includeCondition parameter. 
  • Removed the redundant references to v3 from URLs generated by the feedback form.
  • Updated the Meraki Connections help page to state that 2FA must not be enabled on your account in order to use the [Meraki.ReportXXX:] macros.
  • The Report Jobs page now limits the message length on screen, thereby preventing columns from becoming hidden due to too much information on-screen. 
  • Variable text is now smaller with reduced padding to fit more in view on the Progress Page. 
  • Removed obsolete topics from the Help pages

Bug Fixes

  • Search Results dialog now automatically closes when selecting results.
  • Create/Edit Macro Parameter Defaults  now won't save unless  mandatory parameters are present.
  • The user no longer sees the "Run again" button when a Schedule has been deleted.
  • Admin users can once again use the delete button to remove a user.
  • Fixed an intermittent issue which caused two report jobs to run simultaneously from one Schedule.
  • System Errors are no longer reported when running regression schedules.
  • A number of fixes have been made to the handling of SharePoint files:
    • The API now returns all files (was previously limited to 200).
    • Folder copying issues have been resolved when source folder is empty and also when copying to a higher folder on the same drive.
    • Moving a folders between ReportMagic and and SharePoint locations no longer leaves a rogue, empty folder in the source location.
  • Help has also been updated:
    • [Blogger.Page:] and [Blogger.Property:] macro examples.
    • [Web.Image:] help examples.
    • [List.Sort:] help examples
    • Linux Agent installation
  • RM Script fixes:
    • Macro parsing when closing square bracket appears on a new line.
    • Additional error handling to aid debugging when switching loaded RM Script to rich text mode.
  • Fixed broken macro shorthand ( [-: ) for decrement macro, which meant that negative numbers were not being displayed with the minus sign.
  • Numerous Report Studio macro fixes, including:
    • The coloured background of the [Calculate:] macro errorFontBackgroundColor parameter did not fit the vertical height of the text.
    • [Table:Format:] was not always being applieddue to the presence of newline characters.
    • The [Table,Graph:] palette parameter is now properly applied to the resulting graph.
    • The opacityPercent parameter is now properly applied to the [LogicMonitor.Graph:] output.
  • Fixes have been made to the [Table.Save:] macro as follows:
    • Support for hyperlinks that are not URLs.
    • Support for insertion of styled cells.
  • [ForEach:] macro fixes include:
    • Honouring the specified delimiter, also reflected on the updated help page.
    • Listing the internal macros via [List.DequeueInternal:] for each loop iteration, making it easier to spot any processing errors.
  • Fixes to [If:] / [Else:]  / [EndIf:] include:
    • The presence of a hyperlink at the end of paragraph no longer causes all macros enclosed by the [If:]/[Else:] to execute.
    • A parsing error no longer occurs when a table containing some empty cells is encountered. 
  • Various fixes to the [List,xxx:] macros:
    • [List.Union:] orderDirection now works properly using numeric sorts. It was only doing alphanumeric sorts. 
    • Fixed broken [List.GroupBy:] macro for the Min aggregation type, when any of the columns contain blank values.
    • Fixed an issue whereby using any non-numeric values in [List.SummaryValue:] macro would throw a system error and stack trace, rather than a macro parameter error.
    • [List.SummaryValue:] macro now outputs to 2 decimal places (format=F2) by default, and now supports the calculate parameter. An additional help example was added to demonstrate the use of both. 
  • Fixed a regression in the [Calculate:] macro where too much precision was being shown when the format parameter is not set.
  • Fixed an issue whereby the [EmailReport:] could generate a System Error.
  • Fixes to the [LogicMonitor.SummaryValue:] include:
    • A fix when the storeAs parameter as a variable which was incorrectly giving one value only when multiple aggregations used.
    • When using the excludeSdt=true parameter, a fix has been made to mitigate permission restrictions on the device groups the LogicMonitor account has access to when checking current and historical SDTs.  Such device groups are ignored and no longer cause a macro error.
  • The [LogicMonitor.Graph:] and other graph macros no longer hang upon certain combinations of graph setting parameters.
  • [LogicMonitor.DashboardWidget:] updates to the Help and improved error message when setting widgetId parameter to reflect that graphType=DashboardWidget must also be set.
  • [Agent.SqlTable:] output does not now cause output document corruption when no rows are returned.
  • The [Agent.SqlGraph:] and [Database.SqlGraph:] macros now generate a macro error when there is no data, rather than producing a system error.  Use the noDataText parameter to insert text into the output document to avoid seeing this error.
  • Fixed the broken [Toggl.TimeEntryProperty:] macro parameters property=ProjectName and property=ProjectId.
  • Word output from [Web.Table:] now contain the correct characters rather than unicode.
  • [Snmp.EnterpriseProperty:] macro now generates a macro error rather than a system error when a  'Forbidden' response is encountered.

Comments