2.3.3.2 release notes

2.3.3.2

  • Issue 2640 - When a new Apex unit test run configuration is added from the bulk deployment dialog, it is now automatically selected as the active configuration for unit test execution for that deployment.
  • Issue 2645 - A handful of users have been having issues with IC not finding all of their projects' Apex unit test classes after updating to 2.3.3.1. It appears that a full index/cache rebuild via File | Invalidate Caches may help, but I've also implemented a prospective fix for the issue in this build. If you're still seeing this problem in the build or later even after an indexes/caches rebuild, please let me know so that I can work with you to get diagnostic information.
  • Issue 2648 - Fixed an issue that could result in static resources not being shown correctly in metadata format projects.
  • Implemented several improvements to the new Agentforce for Developers feature integration:
    • Made the feature significantly more configurable, specifically in terms of which aspects are enabled/disabled. These configuration options can be found under Illuminated Cloud | Configure Application | Other | Agentforce for Developers. Note that the Other tab was previously called User Interface, but it's now been generalized (perhaps too much?). The Agentforce for Developers inline completion options that were previously under the IDE's Code Completion settings have also been consolidated into this location.
      The following configuration options are available:
      • Dev Assistant - Whether or not the Agentforce for Developers / Dev Assistant tool window is enabled. Defaults to enabled.
      • Apex code generation - Whether or not the Generate | Using Agentforce for Developers action is available. Defaults to enabled.
      • Apex unit test generation - Whether or not Agentforce for Developers code generation options are included in the Generate | Test dialog for Apex. Defaults to enabled.
      • Inline completion - Whether or not Agentforce for Developers inline completion is enabled. Defaults to enabled.
        • Apex/HTML/JavaScript/CSS - Whether or not Agentforce for Developers inline completion is enabled for the respective language. All options default to enabled.
        • Automatically query inline completions... - Whether or not Agentforce for Developers inline completions are queried and displayed automatically after the specified delay. Note that the default delay is now 500 ms when enabled. Defaults to disabled.
        • Show a visual indicator when querying inline completions - Whether or not a subtle inline indicator is displayed when Agentforce for Developers inline completions are being queried from the server. Defaults to enabled.

        NOTE: These fine-grained feature enablement options were added in partial response to Issue 2646. In the default configuration, the Agentforce for Developers APIs are never engaged without explicit end user feature initiation. Also note that while all features can now be disabled in the IDE if desired, organizations which are not permitted to use generative AI tools by policy — whether Agentforce for Developers or otherwise — should restrict the corresponding API calls at the network layer.

    • Tuned the max_tokens parameter for each of the distinct API requests. Hopefully this will help with some of the unhandled server exceptions that have been seen and may also make some of the API calls complete more quickly.
    • Improved error handling and feature enablement when Agentforce for Developers API authentication fails.
  • A bit of UX improvement to the bulk metadata deployment/retrieval/removal dialog.
  • Other related fixes and improvements.