VDM's now has a built-in self-correction process for Duplicate Appointments that would sometimes cause errors when people are using the Scheduler. (Task 1631)
We have adjusted how the selection process works in the Scheduler - Job creation so that you no longer need to select an execution to have access to the execution options (Add Wizard, Edit Wizard, etc.). (Task 1639)
We have removed the legacy folders (Maps / VDMDB) that were being created when installing VDM. (Task 1642)
#51: Don't start (and stop) the ObjectScript and Python monitors if there are no ObjectScript/Python routines being tracked respectively, fixes error from trying to start/stop the %Monitor.System.LineByLine with no routines
ENH: The licensing system has been updated to fix issues with error code 28 based on a disabled network adapter (PART2)
The activation process needs to read all of a computer’s components to get an accurate “fingerprint” of the computer, and this includes all real (aka non-virtualised) network adapters attached to the computer.
#29: As a consequence of this change, the minimum supported platform version is 2022.1
Added
#29: Track code coverage for embedded python methods in .cls files
#42: Added a listener interface and manager with an associated user parameter, allowing the user to broadcast output on test method/case/suite completion.
#39: Fixed bug where results viewer gave divide by zero error when there were 0 executed methods in the covered code
#41: Now the code strips leading and trailing whitespace from coverage.list, so "PackageName.PKG " will still be loaded properly
Fixed .js files in other namespaces' /itemsetsourcelink web app being editing during ##class(pkg.isc.codetidy.Utils).RunAll (#45)
Fixed .js files being re-exported without edit during ##class(pkg.isc.codetidy.Utils).RunAll() even though ESLint is disabled so no reason to export (#44)
This is the latest release available to match the current VDM release (2024.7.26) as of 7/26/2024.
We always recommend that the latest (matching) version of VDM and WebReports are installed.
WebReports's now has the added functionality so we can call {DrillThrough} directly from Advanced Query like we can with {PivotExecute} and {MDXExecute}. (Feature 1637)