Skip to Content

2026.3.8

New features

B2C Doctor

B2C Doctor finds what nothing in your linked cartridges uses, says why each piece is dead, and removes it as one command that Undo takes back. Open it from More → B2C Doctor or its button on the right tool window bar. See B2C Doctor.

B2C Doctor finds the files, code, routes, resource keys, hooks, tags and metadata nothing in your linked cartridges uses, says why and what is safe to remove, and removes it as one command that Undo takes back. Its Errors page lists what the inspections and the server logs find, and agents get the same scan over B2C MCP
  • Overview: What is Ready to remove and what to Check first, by type and by cartridge, and the live files with the most unused code.
  • Findings: Unused scripts, templates, forms and JSON files, unused functions, variables, requires and exports, commented-out code, routes nothing links to, resource keys, custom hooks and tags, custom attributes and custom object types. Each one says why it counts as dead, next to its code.
  • Remove: A selection goes as one command. A resource key goes from every locale file of its bundle, and a file the server logs show running starts unticked.
  • Errors: What the plugin’s error-level inspections find in your cartridges, and the errors Log Center found in the server logs, at their lines.
  • Live: It scans again as you edit and switch branches. Script editors gray out unused code, and a dead file shows a banner.
  • Share: Saves the Overview as an image or copies it, for a ticket or a team chat.
  • Agents: Two B2C MCP tools give AI agents the same scan. They read the counts first, also per type, cartridge, folder or file, then only the findings they need, and plan a removal that runs as one command Undo takes back.

B2C Doctor needs an active license or trial.

Site preferences your metadata does not define

getCustomPreferenceValue('id') with an ID that no site preference in your metadata defines is now an error, in scripts and templates, like a script path that does not resolve. An ID the code builds is checked when its value is known. A project with no site preference metadata reports nothing.

What each file holds, in B2C Metadata

Each file in B2C Metadata now opens into what it defines: services, profiles and credentials, jobs, preferences, custom objects, slot configurations and library content. A metadata file lists the custom object types it defines and the system objects it extends.

B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, open a file into what it defines with its usages in code, keep only what no code names, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
  • Types: A system object or a custom object type opens into Custom Attributes, Groups and Attributes, as the Metadata Editor lists them. Each attribute shows its name, its type and its usages in code, and each group lists its attributes. Attributes holds the system attributes the file changes, with the key of a custom object type first.
  • Usages: An entry or a custom attribute that code names shows how many places use it. Click the count to list them.
  • Unused in code: The filter in the header keeps only the entries that no script or template names.
  • Search: Finds entries, attributes and groups by their IDs. A group found by its own ID lists all its attributes.
  • Open: Double-click a row or press Enter to open its file on that row, such as an attribute in the Metadata Editor. Right-click it for Show Usages and Copy ID.
  • Icons: Metadata XML files have their own icon, in B2C Metadata and on the Metadata Editor's tab.

Usage counts of custom attributes need an active license or trial, as in the Metadata Editor.

In the XML of your site archive files, each ID that code names shows its usages at the end of its line, such as 3 usages: services and credentials, site preferences, content assets, slot configurations, custom object types, customer groups, campaigns and promotions, payment methods, sorting rules, catalogs and categories, price books, inventory lists, coupons and stores. Click the count to list the scripts, templates and site data that name the ID. See Usages and links in the XML.

  • Links: Cmd+Click / Ctrl+Click on an ID that names another element opens it, such as a service's profile and credential, a slot configuration's content asset or category, or the product of a category assignment. Completion lists the IDs of your project. A system attribute that an attribute group lists goes to its definition and to its Script API property.
  • Through constants: A service or credential ID that code keeps in a constant, such as constants.REFUND_SERVICE from a module it requires, counts at the call that uses it. Before, such a service showed no usages.
  • Paths: The usages list names files outside your cartridges by their path in the project, such as sites/AcmeUS/services.xml. A place in XML opens on the Text tab when you clicked from there.

The usages and the links need an active license or trial.

Large site archive files

The IDE indexes no file above 2.5 MB. Intellij SFCC now reads large catalogs, price books, inventory lists, libraries, slot configurations and metadata itself, one element at a time, so they work as small files do. B2C Metadata lists what they define, their IDs count usages, scripts, forms and log links go to what they define, and B2C Doctor and the B2C MCP tools read them.

Improvements

A clearer What’s new card

The What’s new card in the status bar names the release in its title. The line under it shows the version you have, when that is another one, and the release date. The card has no icons and no animation.

Under Release notes, each version has one row: the version, what it is to you (Installed, Available or Major release), then Read, which opens the notes in an IDE tab, and an arrow that opens them in your browser. The notes of the major release come second when they are another page. Blog posts follow under their own caption, with their whole titles.

At the bottom, Read anytime from More → All Release Notes opens More Intellij SFCC actions in the main toolbar with All Release Notes selected, or the release notes window when that button is not shown. See Release announcements.

Between the popup and the status bar

Switch back to popup on the card turns the What’s new popup on again and opens it for this release at once, and What’s new leaves the status bar. Before, unticking the box on the card and clicking Save dismissed the release, so it showed in neither place.

The box in the popup acts at once too. Tick Show new releases in the status bar instead and the popup closes, and the card opens over What’s new in the status bar. It stays until you point at it, click elsewhere or nine seconds pass.

At the bottom of the popup, More → All Release Notes is a link too. It opens the same place as on the card.

Bug fixes

  • Getting Started: In 2026.3 IDEs, when Getting Started opens, errors that other parts of the IDE hit at the same time, such as the Git log, are no longer reported as Intellij SFCC errors.
  • B2C ODS and B2C Credentials dialogs: Errors that another plugin hits while one of these dialogs is open are no longer reported as Intellij SFCC errors: adding or editing an ODS configuration, Add Sandbox, closing a B2C ODS tab, and editing an account.
  • Connect Agent with a screen reader: With Support screen readers on, Connect Agent… in B2C MCP opens without an IDE error and keeps the agent's Tools choice. Before, opening it set the agent's tools to Global.
  • Log Center in the editor: In 2026.3 IDEs, opening an editor, such as the console of a Git operation, no longer causes an IDE error from the Log Center counts at line ends.
  • Code checks in B2C MCP: The B2C MCP tools that check code and preview quick fixes report the plugin’s inspection problems again. Before, they reported every file as clean.

What's new in 2026.3

On this page