2.4.2.8 release notes

2.4.2.8

Reissue of 2.4.2.7 with hotfix for Metadata Visualizer not showing visualizations in older IDE versions.

• Issue 3026 - Added support for the Salesforce Metadata Visualizer to show in-IDE previews of supported metadata types, currently Agent Script scripts, flexipages, flows, permission sets, and SObject type definitions.
  • This feature is disabled by default and can be enabled on a per-metadata type basis in Illuminated Cloud | Configure Application | Other | Enable Metadata Visualizer for.
  • The Metadata Visualizer only supports source format metadata files, so this feature is only available in source format projects.
  • The Metadata Visualizer option for Flow files is mutually-exclusive with the Use preview editor for Flow files option. At most one of these options can be enabled for Flow files.
  • IC must find the Node.js executable — node on Mac/Linux or node.exe on Windows — in the system execution path for this feature to be enabled.
  • If Metadata Visualizer is enabled for a file's type and the Node.js executable is found, a file-level annotation will be displayed to help install Metadata Visualizer for the project.
  • Once installed, the IDE's standard text-editor-with-preview will be used for enabled metadata file types with the metadata file displayed on the left-hand side and the visualization displayed on the right-hand side. You can, of course, toggle between the split view, the metadata file, or the visualization.
  • Visualizations update automatically when associated metadata files have been modified and saved to disk. Unsaved changes are not reflected in the visualization.
  • IC's integration of Metadata Visualizer is read-only. Visualization features that offer to change metadata file contents, e.g., the Select to Edit and Select buttons, are not active at present. I will investigate whether it's possible to handle those features in this integration.
• Issue 3032 - Partially fixed an issue that could result in an HTTP 403 with error message INVALID_INPUT: runTestsAsynchronous rejects an empty testMethods array during execution of Apex test classes with a large number of test methods. Previously the asynchronous Apex unit test execution API would fail with an HTTP 500 / Internal Server Error if the request included a test class containing 150+ test methods. IC included a workaround to execute the entire test class when this situation is detected, but in Winter '27 / API v68.0, such a request now results in the aforementioned HTTP 403. The good news is that the original HTTP 500 error that motivated this workaround seems to have been partially resolved, so I've removed the workaround. I've said "partially" twice now because I did observe a few examples of the same HTTP 500 failure in test classes with very large numbers of test methods, and I've provided examples of concrete reproductions to the appropriate folks at Salesforce so that the root cause bug can be resolved properly.
• Fixed an issue that could result in stale project information being used after a project has been closed and reopened.