Entry Point Navigation

The extension indexes SFCC extension points so you can find runtime entry points from code instead of searching folders manually

Route completionHook treeCustom API panel

storefront

Intellij SFCC

Explorer

B2C MCP

Log Center

Hooks (3)

Custom API (1)

int_loyaltyAPI: 1 | Paths: 2 | Impl: 2

loyalty(2)

v1/pointsGET

GET

v1/rewardsGET

Steptypes (1)

Credentials

Intellij SFCC Account

Product.jsloyalty.jsscript.js

cartridgesint_loyaltycartridgerest-apisloyaltyscript.js

1'use strict';

2

3var RESTResponseMgr = require('dw/system/RESTResponseMgr');

4

5exports.getPoints = function () {

6 var profile = customer.profile;

7 var points = profile ? profile.custom.loyaltyPoints : 0;

8 RESTResponseMgr.createSuccess({ points: points }).render();

9};

10exports.getPoints.public = true;

11

12exports.getRewards = function () {

13 RESTResponseMgr.createSuccess({ rewards: [] }).render();

14};

15exports.getRewards.public = true;

mainSFCC JavaScript

Supported Areas

• SFRA route completions and route endpoint navigation
• Hook name and hook function completions
• Hook tree views with raw and grouped modes
• Custom API folder, endpoint, method schema, API JSON, and script navigation
• Steptype JSON source navigation
• Template and resource completions that depend on indexed cartridges

Keeping the indexes current

There is nothing to refresh by hand. The indexes follow your files: saving, creating, renaming, or deleting a route file, hooks.json, steptypes.json, or a Custom API folder updates the views and completions, and linking a cartridge or picking another B2C Scope re-reads the cartridge order

If a view still shows an old entry, for example after a branch switch outside VS Code, save the file once or run Intellij SFCC: Refresh B2C Commerce Library from the Command Palette, then wait for indexing to finish