2.2.6.4 release notes

 2.2.6.4

• Issue 2290 - Significantly overhauled the way that reported deployment errors are presented to the user in both the Illuminated Cloud > Problems view and the Messages view:
  • Reported errors are partitioned into three categories:
    • Failures - Standard failures that are typically directly attributable to the metadata/source file that raised the error.
    • Transitive failures - Failures in a metadata/source file that are the result of a failure elsewhere, e.g., ClassA references ClassB which references ClassC which contains a syntax error. Transitive failures are resolved when the underlying root cause failures are addressed. Whenever possible, transitive failures are hyperlinked to the associated root cause.
    • Unexpected errors - Affectionately known as GACKs, these are Salesforce internal server errors with very little actionable diagnostic information. Resolving the standard failures will often resolve them as well, and any remaining instances typically require input from Salesforce.
    This partitioning should provide a much better signal-to-noise ratio when deployment fails in a seemingly catastrophic fashion, though often due to a very small number of actual underlying issues. The true issues should be included in the Failures section of the deployment error report in either view.
  • The Illuminated Cloud > Problems view now provides new toolbar buttons for results filtering and navigation including:
    • Previous/next problem navigation
    • Expand/collapse all tree nodes
    • Expand only actionable (i.e., Failures) tree nodes
    • Show/hide transitive failures (shown by default)
    • Show/hide unexpected errors (shown by default)
• Implemented a workaround for yet another Salesforce CLI regression, this one being a breaking change to how conflicts are reported by the force:source:push command. IC2 will once again properly notify the user of failure due to conflicts and prompt to retry with the -f flag, but details about the specific conflicting metadata will not available until this regression is addressed. Note that conflict detection in the force:source:pull command is unaffected by this regression and should work properly.
• Improvements to the IcApexDoc custom Velocity templates integration added in the previous release:
  • In IntelliJ IDEA Ultimate Edition, the module created for the custom Velocity templates directory is now automatically ignored by the IC2 module validator.
  • In non-IntelliJ IDEA Ultimate Edition, provided additional assistance with association of *.vm files with the custom Velocity template file type.
• Added XML file type associations for OmniStudio metadata file extensions when used in metadata format projects.
• Added automatic exclusions for a few known directories which could contain ambiguous source files.