| MS-22400 |
Blocker |
[LogicMonitor.DeviceGroupList] AutoMapper error |
The [LogicMonitor.DeviceGroupList:] macro now does not give unexpected error. |
| MS-22325 |
Blocker |
NCalc: [List.GroupBy:] should not have different behaviour in 4.0 than 3.28.289 (QA Core Regression tests) |
Improved List.GroupBy condition handling guidance by standardizing numeric Count comparisons to use numeric values (for example 0) instead of empty-string checks, preventing invalid-expression outcomes in newer builds. |
| MS-22318 |
Blocker |
LogicMonitor DataMagic: TimeSeriesDataAggregations table should not store infinity against any column |
The LogicMonitor DataMart's TimeSeriesAggregations tables will not contain any "Infinity" double values, but rather use null instead (or appropriate value). |
| MS-22382 |
Blocker |
[LogicMonitor.xxxx:] macros should not give a system error in 4.0.239 and 4.0.252 |
Various [LogicMonitor.xxx:] macros now do not give unexpected system errors. |
| MS-22299 |
Blocker |
ReportMagic 4: Signal R update / subscription messages do not appear to be working on PS (and Prod) environments |
Resolved an issue whereby ReportMagic v4 Batch Jobs, Report Studio and the Report Schedule pages were not updating in real time during job execution. |
| MS-22401 |
Blocker |
NCalc: Regression Issue: [Calculate: value=`where(BillingCardData, 'b', 'itemAtIndex(b,4) == TGlobeId' )`,=>GlobeIdEntries] |
Fixed an Ncalc issue when itemAtIndex was returning item types inconsistently between Report Studio and Ncalc101 apps. |
| MS-22450 |
Blocker |
Macro feedback for: [Calculate: value=`where(BillingCardTransactions, 'T', 'itemAtIndex(T,0) == \'Correction\' && itemAtIndex(T,1) != \'\'' )`,=>CorrectionBillingCardTransactions] |
Fixed an NCalc issue with itemAtIndex which was failing to return the indexed item. |
| MS-22288 |
Blocker |
NCalc: [List.Select:] macros should not give Ncalc system error in Core Regression Tests (QA regression Schedules) |
Fixed an issue with the NCalc expression options being set ONLY to ExpressionOptions.OverflowProtection, thereby breaking behaviour of the [List.Select:] macro (and possibly others). |
| MS-22451 |
Critical |
isNullOrEmpty should work in a [Calculate:] macro |
isNullOrEmpty nows works in a [Calculate:] macro |
| MS-22287 |
Critical |
NCalc: Various Calculate macros should not give Ncalc failures in PPTX Regression & Core Regression Tests (QA regression Schedules) |
Fixed overflow handling for isNaN() and isInfinite() in Calculate macros, so divide-by-zero cases now behave consistently when overflow checking is disabled. |
| MS-22447 |
Critical |
Graphs should not experience Document Wrapper Exceptions (3.28 issue) |
Fixed an issue that should prevent transient graph macro failures. |
| MS-22453 |
Critical |
Regular users (without Tenant Admin rights) should be able to view the Report Library and not see an error pop-up |
Fixed an issue where regular users could not view the ReportMagic 4 Report Library page, and would see a pop-up error message. |
| MS-22360 |
Critical |
NCalc: HealthCheck v4 -> Comparing an empty string JValue variable to an empty string ( '' ) should evaluate to true not false |
Fixed an issue when using Schedule forms, where the form values that were sent in as JValues would cause macro issues that use NCalc evaluation. JValue basic types (float, string, int, boolean, etc) are now converted to common run time equivalents. JArrays / JObjects etc. are left as-is. This fixes issues in the library reports, such as the LogicMonitor HealthCheck. |
| MS-22452 |
Major |
NCalc sum() with lambda should use the lambda function |
NCalc sum() with lambda now uses the lambda function |
| MS-22181 |
Major |
The [HaloPsa.List:] macro should not create empty unknown variables (when there are no results), but instead should produce an empty JArray |
The [Halo.PsaList:] macro, when there are no results, instead of creating an empty and unknown variable, the macro now creates an empty JArray variable. |
| MS-22412 |
Major |
[LogicMonitor.Image:] should not give system error about libskiasharp |
Various Image processing/library issues have now been fixed. |
| MS-22410 |
Major |
[LogicMonitor.Dashboard:] should not give "image size" errors and cause regressions in the QA Regression Schedules |
Various Image processing/library issues have now been fixed. |
| MS-22392 |
Major |
Schedules should not give "The type initializer for 'SkiaSharp.SKAbstractManagedStream' threw an exception." System errors for schedules when they do not have any system errors in them |
Various Image processing/library issues have now been fixed. |
| MS-22391 |
Major |
[File.Image:] should not error with "SkiaSharp.SKData" errors and cause regressions in the QA Regression Schedules (pptx regression tests) |
Various Image processing/library issues have now been fixed. |
| MS-22390 |
Major |
[Web.Screenshot:]/[File.Image:]/[Web.Image:] should not give "image size" errors and cause regressions in the QA Regression Schedules |
Various Image processing/library issues have now been fixed. |
| MS-22105 |
Minor |
NCalc sum() function of form `sum(list(1, 2, 3), 'n', 'n * n')` not working correctly |
Fixed an issue with the sum() NCalc function. |
| MS-21505 |
Minor |
Macros that fail should not show as using Legacy Mode if they ran using Normal mode |
Fixed an issue where most macros would show as being in legacy mode, upon failure. |
| MS-22183 |
Minor |
[HaloPsa.List:] help example should not error with invalid type |
Fixed the broken [Halo.PsaList:] macro help example. |
| MS-22456 |
Trivial |
Progress Page job duration in excess of 60 minutes should not contain spurious closing bracket character |
Fixed an issue where the report duration on the progress page could contain an unnecessary closing bracket character, if the report ran for over 1 hour. |
