Illuminated Cloud Announcements

2.4.1.8 Issue 2957 - Fixed an issue where errors could occur when adding/removing Apex offline debugger server-side checkpoints. Issue 3002 - Fixed an issue with @NamespaceAccessible symbols from installed managed packages with the same namespace as the org not being properly rendered into the OST. Note that you must regenerate your OST to see the effect of this fix. Issue 3003 - Fixed an issue where file copy/paste-for-overwrite in the IDE could result in IC prompting to remove the corresponding metadata files from the subscription and org. This is because the IDE actually does remove the original files and create new replacement files. IC now ignores the file removal events in this specific scenario. Issue 3004 - By default large numeric values are returned by the SOQL and SOSL query APIs in scientific notation , and the SOQL Query and SOSL Query tool windows simply show the returned data. Now those tool windows include a configuration option, Convert scientific notation value...

2.4.1.7 Issue 2998 - IC no longer bundles the Salesforce skills. Instead it uses the GitHub repo for Salesforce skills , checking the latest published version against the installed version and, if not yet installed locally or an update is available, cloning the repo into a temp directory and installing those. Note that there are significant differences between the original skills bundled with IC and the latest from that repo, so you might want to remove the existing skills before installing the new ones. Of course, if you've customized those skills and/or added your own, you should reconcile carefully to avoid losing anything. When a project is opened — including as part of IDE startup — IC checks for a plugin update. While the IDE already does this for all installed plugins, it only looks for updates that are compatible with the installed JetBrains IDE. Given that IC maintains compatibility with (roughly) one year's worth of JetBrains versions, currently 2025.2-2026.2, users ...

2.4.1.6 - Hotfix for 2.4.1.5 Issue 3001 - For some reason the compiler marked the catch block for UnexpectedErrorFault as invalid in IC's expired/invalid session handling logic, so I removed it. Sure enough, though, that exception still occurs, and now IC wasn't handling and recovering from it properly any longer. This is a targeted hotfix to restore that handling, albeit in a manner that the compiler no longer flags.

2.4.1.5 Issue 2995 - Fixed several issues with ApexDoc Markdown processing during parsing, conversion to HTML, and formatting. Note that the ApexDoc formatter option to add HTML paragraph break elements on blank lines is now automatically disabled if any of the ApexDoc Markdown-related formatter options are enabled. Paragraph breaks are, of course, added in Markdown with two consecutive blank lines, so it didn't make sense to have both options enabled simultaneously. Improved the background threading behavior changes introduced in the previous build to allow immediate cancelation of read-only API calls. This specifically improves the "hand-off" of progress indicators across background threads, and eliminates (or at least minimizes) unnecessary creation of background/worker threads from existing background/worker threads. Added XSD element definitions for FeatureParameter* and GenAiPromptTemplate metadata. Improved progress indicator feedback when refreshing the org met...

2.4.1.4 Issue 2979 - Implemented several performance improvements around the build options dialog and module subscription editor in projects with very large amounts of org metadata. Issue 2985 - Fixed several issues with metadata types that are either not reported properly by the Metadata API or have insufficient information about parent/child metadata type relationships. This addresses some specific issues, but I'm sure there are other metadata types — specifically those gated by feature flags — that are still unaddressed. I'll be happy to take care of those, but I'll need to know the specific metadata types and enabling feature flags. Issue 2990 - IC application-level settings now try to infer project-level context better when opened via system settings. Added support for the Agent Script Language Server for *.agent files. As usual, LSP4IJ is required, and you must also download the language server distribution and register it with IC. IC will, of course, help insta...

2.4.1.3 Issue 2987 - Fixed several issues with Flow diagrams in 2026.2. While diagrams now render properly, there are still a few remaining issues that seem attributable to the newer version of Mermaid used by the 2026.2+ version of the Mermaid plugin: Icons do not display properly, so they're not included in diagram nodes. The diagram look-and-feel options, e.g., Elk renderer and curve styles, don't seem to have any effect. Fixed several issues with copying Apex string literal contents to the system clipboard that were introduced with Apex multiline string support. A quick reminder that the public issue tracker , user guide , and discussions have been completely migrated from Bitbucket and Google Groups respectively into GitHub. The original public issue tracker and user guide will be removed by Atlassian on August 20, 2026 as part of its sunsetting of Bitbucket Cloud issues and wikis , and the original discussion groups are now read-only historical archives given that the o...

2.4.1.2 The migration of the public issue tracker and user guide from Bitbucket Cloud to Github is now complete. The original resources are now in a read-only mode and will no longer be available starting August 20, 2026. The new resources are: Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note: Some issue numbers have changed, so if you have external references to the originals, you may need to update those not just for Bitbucket vs GitHub, but also for the new issue numbers. The issue titles are (mostly) unchanged, so you should be able to locate the new one easily by title. I've updated all internal links between issues to accommodate for these changes. Unfortunately I wasn't able to attribute migrated issues to the GitHub user IDs corresponding to the original Bitbucket issue creator user IDs, but the original Bitbucket user IDs and creation date/time information are included in the migrated issues for histo...