API version in Deploy Code
Sandbox 01
version2
RefArch (3)
11 cartridges
1 global module
Staging
API version:
Runs first: npm run build
Deployment Settings....apiversion file forces the code version to run on one B2C Commerce API version, for compatibility: a row's API version picks it for that instance, API version under the list for all, and Not set uploads none. Deploy opens B2C Sync on its Code Deployment tab, one tab per instance, and one notification sums up all of them with the timeDeploy Code has a new API version column. A .apiversion file forces the code version to run on one supported B2C Commerce API version, for compatibility. Click a row's version to pick one for that instance: one of the modes B2C has, newest first, or Custom Version... for any other, such as 23.2. Not set uploads no file. Each pick is saved for that connection in the project.
API version under the list sets one for all instances in place of each row's, and the rows show it in grey. Per instance gives each row its own back.
With a version, the deployment uploads .apiversion right after the cleanup, and the B2C Sync console prints the version under the instance. If the file can't go up, the deployment to that instance stops before any cartridge. Full cleanup of the code version now leaves .apiversion in place. Activate the code version again for a change to apply. See API version.
Quieter release announcements
Turn off Open the What’s new popup for each new release under Settings › Tools › Intellij SFCC, and a new release no longer opens its popup or its pages in editor tabs. It shows a notification and a What’s new item in the status bar, next to the red panda.
Point at What’s new to see the release at once: the version you had and the one it moves to, its release notes and blog posts with Open in IDE and Open in Browser, and Dismiss. Click it to open the release notes. The item stays until you open the notes or dismiss them, also after a restart. The setting is on by default. See Release announcements.
B2C Sync
A deployment's own requests
Deployed 12 cartridges in 0:38
201 Created
.apiversion fileWith no row selected, the request details of Code Deployment show the requests the deployment sent for itself: the connection check, the listing of the code version, the .apiversion upload when an API version is set and, in a full cleanup, the removal of cartridges it doesn't bring. When a whole deployment fails, the error on the status line links to them. See Request details.
File watcher card
The card behind Native watcher at the end of the Code Upload header, and behind the status bar item, is short and clear: one picture of where a change goes, one sentence and a short note, with Try Again and Copy in one row. It opens the moment you point at the label. See File watcher.
Bug fixes
- Request details: When you stop a deployment or a cartridge upload while a zip goes up, the removal of the zip left on the instance now shows in that row's request details.
- Remote development: In split mode, such as remote development over SSH, the connection and code version selectors and More Intellij SFCC actions in the main toolbar open in the JetBrains Client and look like the IDE's own toolbar buttons. So do the instance, credentials and OCAPI version selectors in B2C OCAPI and the preset in B2C MCP. Under Tools › Salesforce B2C Commerce, More Intellij SFCC actions is a submenu.
- License after startup: Deploy Code, Auto Upload and other licensed actions check the license again when you use them, and the license is checked every 15 seconds until it is confirmed. On a remote development backend, which gets the license from the JetBrains Client after it starts, they no longer stay unavailable for up to five minutes.