Illuminated Cloud Announcements

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 f...

2.4.2.7 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 file's type and the Node.js executable is found, a file-level annotation will be displayed to help instal...

2.4.2.6 Issue 3007 - Winter '27 / API v68.0 update Updated the SOAP client for API v68.0. Updated the API version used for primary communication with Salesforce APIs to 68.0. Added 68.0 as an available API version number for configured connections. Updated metadata.xsd based on the API v68.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Winter '27. Updated the bundled completions?type=apex Tooling REST API response to be based on the API v68.0 REST endpoint. See below for more information about support for the new Apex Symbol API. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '27 changes. Updated the bundled SLDS CSS and SVG icons to 2.264.1. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for the new Apex Symbol API when generating project offline symbol tables. This featur...

2.4.2.5 Issue 3029 - Fixed an issue with aer-based Apex debugging where the aer DAP server wasn't being started with the correct working directory. The fix is not in IC, though, and is instead an accepted and merged pull request against the corresponding LSP4IJ bug . Once that new build is available, it should resolve the associated issues with relative paths and finding .aerrc . Fixed an issue with the Apex recursive call line marker provider incorrectly adding line markers for calls to the same method on other instances. Fixed issues with quick-fixes that use templates in batch inspection runs. Those with complex templates are no longer available in batch mode. Those that require selection of a single value from a common list of values now prompt for that value once and apply the quick-fix to all selected instances, e.g., the sharing mode modifier that should be added to all selected classes without a sharing mode.

2.4.2.4 Issue 2980 - IC now displays the project's .aerrc file contents, if present, in the Apex test run configuration editor so that it's obvious exactly what command-line options will be used when executing Apex tests via aer. It's still possible to configure additional aer command-line options on a per-run config basis in the run configuration editor as well. Issue 2924 - Added a new deployment Apex test level, RunDependentTests , that is conceptually similar to RunRelevantTests , but the set of tests to be executed is computed by IC before deployment — and then executed using the RunSpecifiedTests test level — instead of being computed by the Salesforce server. There are notable differences in how IC computes transitive dependents vs. how Salesforce computes them (at least at present): IC specifically computes dependent relationships with member-level granularity whereas Salesforce computes them with class-level granularity. This means that if an intermediate dep...

2.4.2.3 Issue 2885 - Added support for additional decomposed metadata types . As with the underlying feature, this support is beta . If you encounter issues with it, consider disabling optional decomposition and please report those issues to Salesforce or IC as appropriate. Issue 2936 - Added support for both types of edition values in project-scratch-def.json files. Values are still written in the documented form when scratch org definition files are written by IC. When Apex Execution Runtime (aer) is used for Apex code coverage, IC now uses the covered line information instead of computing its own set of executable lines. The tooltip for the Salesforce skills Update button in the Agentforce configuration tab now includes details about the nature of the recommended update, e.g., the installed and available version date/time stamps. Improved the offline symbol table generator's support for ExternalServiceRegistration classes which can sometimes yield HTTP 500/Internal Serve...

2.4.2.2 Issue 3011 - Prospective fix for an IDE freeze during initial dynamic file type determination. The Apex Unresolvable Reference code inspection now verifies property accessor visibility based on the reference context with write expressions being checked against the property setter and read expressions being checked against the property getter. This becomes particularly useful in Winter '27 where the Apex Symbol API includes property getter and setter visibility information for properties of system types. The Apex Annotation and Modifier Agreement code inspection now flags property accessors with higher visibility than their containing properties as errors with quick fixes to adjust the property or property accessor visibility to a valid value relative to the other.