DWithEase Insights & Guides https://dwithease.com/resources/ DWithEase brings faster navigation, persistent sessions, useful shortcuts and productivity tools directly into your everyday Salesforce Commerce Cloud workflow. en-us Mon, 05 Oct 2026 10:00:00 GMT <![CDATA[What Should You Test After Updating an SFCC Storefront?]]> https://dwithease.com/resources/test-after-updating-sfcc-storefront/ https://dwithease.com/resources/test-after-updating-sfcc-storefront/ Mon, 28 Sep 2026 10:00:00 GMT Site Development > Code Deployment` | Testing an inactive version; staging running last week's build while production targets new code. | | **Cartridge Path** | `Administration > Sites > Manage Sites > [Site] > Settings` | Misordered cartridges causing overridden ISML templates or controller scripts to resolve unexpectedly across the entire site. | | **Data Import** | `Merchant Tools > Site Import & Export` or specific catalog pages | Catalog, price books, inventory, or promotions imported with schema validation warnings or missing product assignments. | | **Site Preferences** | `Merchant Tools > Site Preferences > Custom Site Preferences` | Missing environment-specific API keys, incorrect service credentials, or misconfigured feature flags. | | **Page / Partial Cache** | `Administration > Sites > Manage Sites > [Site] > Cache` | Cache not invalidated; testing stale responses or verifying fixes that haven't actually propagated to edge nodes. | > **Pro Tip on Site Cache**: Always invalidate the page cache for your test site immediately after deploying code or importing data. Testing a page served from cache is the #1 reason broken releases pass QA and working releases appear broken. --- ## 2. The Core Transactional Smoke Path Regardless of the release scope, every deployment requires running the transactional spine of the storefront. This test is quick, deterministic, and fails loudly when foundational templates or controller pipelines break: 1. **Homepage & Navigation**: Verify global header rendering, category flyouts, search input autocomplete, and footer link assets. 2. **Category / Search Results (PLP)**: Load a top-level category. Confirm product grid rendering, refinement facet filtering (size, color, price), pagination, and sort order. 3. **Product Detail Page (PDP)**: Test both a simple standalone SKU and a **variation master** with multiple attributes (size, color, width). Verify price book calculation, inventory availability messaging, and product image gallery swapping. 4. **Cart Operations**: Add products to cart, increment quantity, update variation attributes in-cart, remove an item, and apply a test promotion coupon code. 5. **Guest Checkout Flow**: - Shipping address validation (postal code lookup). - Shipping method selection and rate recalculation. - Sandbox payment processing (credit card 3DS challenge, PayPal/Apple Pay sandbox). - Order review and submission to order confirmation receipt. 6. **Registered Customer Flow**: Account sign-in, saved address pre-fill, profile edits, and order history lookup. ### Testing Beyond the Default Locale If your storefront operates across multiple sites, currencies, or locales (e.g., `en_US`, `de_DE`, `fr_FR`), never conclude testing on default English alone: ```bash # Verify raw HTTP status and cache headers across locales with curl: curl -I -s -A "Mozilla/5.0" "https://staging.yourbrand.com/on/demandware.store/Sites-YourSite-Site/de_DE/Home-Show" | grep -E "HTTP/|x-dw-|x-sf-cc" ``` A controller or ISML template change that runs cleanly on the default locale can trigger an unhandled exception when resolving a missing locale-specific resource bundle or currency formatting rule. --- ## 3. Where SFCC Breaks Quietly (The Hidden Failures) The production bugs that harm revenue rarely crash the storefront with an HTTP 500 error. Instead, they manifest in background processes, indexing drift, and subtle caching bugs: ### Search and Indexing Drift A catalog import or attribute definition update does not immediately reflect on the storefront. Until the search index is rebuilt under `Merchant Tools > Search > Search Indexes`, newly imported products may be online, orderable, but completely invisible in search and category pages. ### Over-Aggressive Caching & Personalization Leaks ISML caching directives (``) control time-to-live at the page and component level. ```html
Hello, ${pdict.CurrentCustomer.profile.firstName}!
``` If a developer places an aggressive cache directive on a template containing personalized customer data or geolocation logic, the first shopper's session details can be cached and served to every subsequent visitor. ### Promotion and Ranking Collisions Promotions interact in non-obvious ways. A new tier discount (`Buy 2 Get 20% Off`) may unintentionally combine with an existing brand exclusion rule or coupon code. Always test: - The newly updated promotion. - An existing active promotion alongside it to ensure exclusivity rules and promotion ranking (`Merchant Tools > Online Marketing > Promotions`) operate as designed. ### Content Assets vs. Content Slots vs. ISML Templates When a banner or promotional block renders improperly on the storefront, troubleshooting usually wastes time determining who owns the markup: - **ISML Template**: Hard-coded structural markup governed by developers in the cartridge repository. - **Content Slot**: Dynamic rendering container defined in template code, configured in Business Manager (`Merchant Tools > Online Marketing > Content Slots`). - **Content Asset**: Raw HTML, text, or rich media authored by merchandisers (`Merchant Tools > Content > Content Assets`). > **Using DWithEase**: Instead of inspecting DOM trees or guessing cartridge paths, toggle the **Highlight Content** shortcut in the [DWithEase Business Manager toolbar](/docs/business-manager/#highlight-content). It visually highlights all active slots and assets directly on the live storefront, letting you jump straight into the corresponding Business Manager record with a single click. --- ## 4. Environment Parity: "Works on My Sandbox" Testing on a local On-Demand Sandbox (ODS) with twenty mock products and no active third-party integrations does not prove readiness for production. | Test Environment | Best For | Limitations | | :--- | :--- | :--- | | **Developer Sandbox** | Rapid feature iteration, ISML layout tuning, controller logic debugging. | Small mock catalog; no real payment gateway traffic; empty promotion rules. | | **Shared Staging Instance** | Full end-to-end regression, tax calculations, payment gateway webhooks, inventory sync jobs. | Shared environment; potential collisions with concurrent developer releases. | | **Production Preview** | Final pre-go-live sanity check with real production catalog data and live cache clusters. | Live environment; orders must be carefully placed using test credentials or canceled immediately. | When reporting test results in pull requests or release notes, always declare the exact test environment: *"Validated on Staging (Build 24.8.2) with full catalog data sync"*, not *"Tested locally"*. --- ## 5. What to Automate vs. What to Keep Manual Running a 40-step manual checklist for every deployment consumes hours of engineering time each week. Under deadline pressure, manual checklists inevitably get truncated—testers verify checkout on desktop and skip mobile, or test the primary locale and skip secondary markets. The proven strategy of high-performing SFCC teams separates testing into two distinct tracks: ``` ┌─────────────────────────────────────────────────────────────┐ │ SFCC TESTING STRATEGY │ ├──────────────────────────────┬──────────────────────────────┤ │ AUTOMATED REGRESSION │ HUMAN EXPLORATORY │ │ (Runs on every deploy) │ (Focuses on new UX) │ ├──────────────────────────────┼──────────────────────────────┤ │ • Smoke path end-to-end │ • Visual polish & animation │ │ • Guest & user checkout │ • Edge-case customer flows │ │ • Coupon application tests │ • Complex promotion mixes │ │ • Multi-currency rounding │ • Third-party tag validation │ │ • Service endpoint health │ • Device ergonomic testing │ └──────────────────────────────┴──────────────────────────────┘ ``` Automating your baseline regression suite ensures that every release satisfies the transactional requirements, freeing your team to focus on the nuanced customer experience. --- ## Post-Deployment Release Checklist Before marking any SFCC release ticket as resolved, verify these final operational checks: - [ ] **Active Code Version**: Verified under `Administration > Site Development > Code Deployment`. - [ ] **Cache Invalidated**: Cleared site page cache on target instance. - [ ] **Search Indexes**: Rebuilt and validated index status (`Merchant Tools > Search > Search Indexes`). - [ ] **Transactional Spine**: Successfully completed guest checkout to order receipt page. - [ ] **Error Logs Monitored**: Inspected recent log files under `Administration > Site Development > Development Setup > Log Files` (`error-*`, `customerror-*`) for unhandled exceptions. - [ ] **Third-Party Services**: Verified active service status for payment, tax, and inventory feeds under `Administration > Operations > Services`. ]]> <![CDATA[Your SFCC Catalog Is Organized. Can Customers Find the Right Products?]]> https://dwithease.com/resources/sfcc-catalog-organized-can-customers-find-products/ https://dwithease.com/resources/sfcc-catalog-organized-can-customers-find-products/ Sun, 20 Sep 2026 10:00:00 GMT <![CDATA[Is Your SFCC Storefront Visible to AI Agents?]]> https://dwithease.com/resources/is-your-sfcc-storefront-visible-to-ai-agents/ https://dwithease.com/resources/is-your-sfcc-storefront-visible-to-ai-agents/ Mon, 05 Oct 2026 10:00:00 GMT <![CDATA[From Faster SFCC Development to Safer Releases]]> https://dwithease.com/resources/faster-sfcc-development-safer-releases/ https://dwithease.com/resources/faster-sfcc-development-safer-releases/ Tue, 15 Sep 2026 10:00:00 GMT <![CDATA[Your SFCC Changes Are Live. Now What?]]> https://dwithease.com/resources/sfcc-changes-are-live-now-what/ https://dwithease.com/resources/sfcc-changes-are-live-now-what/ Thu, 10 Sep 2026 10:00:00 GMT <![CDATA[You've Managed the Catalog. But Is the Product Data Good Enough?]]> https://dwithease.com/resources/managed-the-catalog-is-product-data-good-enough/ https://dwithease.com/resources/managed-the-catalog-is-product-data-good-enough/ Sat, 05 Sep 2026 10:00:00 GMT <![CDATA[Your SFCC Store Works for People. Does It Work for AI Agents?]]> https://dwithease.com/resources/sfcc-store-works-for-people-does-it-work-for-agents/ https://dwithease.com/resources/sfcc-store-works-for-people-does-it-work-for-agents/ Fri, 02 Oct 2026 10:00:00 GMT <![CDATA[Less Clicking in Business Manager: Shortcuts SFCC Teams Actually Use]]> https://dwithease.com/resources/less-clicking-in-business-manager/ https://dwithease.com/resources/less-clicking-in-business-manager/ Fri, 28 Aug 2026 10:00:00 GMT Sites > Manage Sites > [Site] > Cache` | Clearing static/page cache after code or data changes. | 1-Click toolbar action or direct bookmark with site parameter. | | **Code Deployment** | `Administration > Site Development > Code Deployment` | Activating new build versions, inspecting release timestamps. | Pinned shortcut or Command Palette jump. | | **Cartridge Path** | `Administration > Sites > Manage Sites > [Site] > Settings` | Reordering cartridges, adding plugin cartridges, debugging overrides. | Direct bookmark to site settings. | | **Search Indexes** | `Merchant Tools > Search > Search Indexes` | Rebuilding product and content search indices after catalog imports. | Single-click status monitor from developer bar. | | **Custom Site Preferences** | `Merchant Tools > Site Preferences > Custom Site Preferences` | Updating integration credentials, third-party API keys, feature flags. | Direct group selection shortcut. | | **Content Assets** | `Merchant Tools > Content > Content Assets` | Authoring merchandising HTML, editing modal copy, policy pages. | Storefront-to-BM deep link via visual inspector. | ### Three Levels of Navigation Optimization 1. **URL Bookmarks with Site Context**: Business Manager URLs contain unique site and object identifiers. You can bookmark the cache page for your primary sandbox. *(Limitation: Fails to scale once you work across three or more sandboxes, because hostnames differ).* 2. **Business Manager Quick Search**: The search bar in the top navigation matches module names. Typing `"cache"` or `"code dep"` and pressing Enter is significantly faster than hovering four levels of dropdown menus. 3. **Persistent In-Context Toolbar**: The [DWithEase Business Manager extension](/docs/business-manager/) injects a lightweight toolbar directly into every BM screen. Cache invalidation, code version switching, and search index rebuilds remain one click away—without causing you to lose your place on the record you are currently editing. --- ## 2. Leverage Native & Injected Keyboard Shortcuts Most users treat Business Manager as a purely mouse-driven interface. However, save-heavy workflows—such as editing content assets, adjusting sorting rules, or tweaking site preferences—benefit dramatically from keyboard navigation. | Shortcut | Scope | Action Performed | | :--- | :--- | :--- | | Ctrl + S / Cmd + S | Form & Preference Pages | Triggers the **Apply** / **Save** button immediately without scrolling to the footer. | | Alt + X | Form Pages | Cancels current edit and returns to previous module view. | | Ctrl + L / Cmd + L | Content Asset Editor | Locks or unlocks the current content asset for exclusive editing. | | Ctrl + D / Cmd + D | Content Asset Editor | Downloads the asset definition directly as clean XML. | > **Pro Tip**: In DWithEase, a small keyboard badge appears in the bottom corner of supported pages. Hovering over it displays all context-aware shortcuts available for that specific screen. See the [full keyboard shortcut documentation](/docs/business-manager/#shortcuts). --- ## 3. Fix the Input Fields That Fight Back Certain legacy Business Manager inputs introduce significant manual overhead. Resolving them at the browser level transforms frustrating multi-step tasks into instant operations: ### Minified JSON in Custom Site Preferences Modern SFCC cartridges store complex configuration objects as raw JSON inside standard text attributes. By default, Business Manager renders JSON as a single, unbroken string: ```json {"enabled":true,"apiKey":"pk_live_09481a8c","timeout":5000,"endpoints":{"auth":"https://auth.gateway.com/v1","checkout":"https://api.gateway.com/v2"},"retryPolicy":{"maxAttempts":3,"backoffMultiplier":1.5}} ``` Hunting for an unescaped double quote or missing closing brace in a 1,000-character single-line input causes unnecessary delays. DWithEase automatically identifies JSON fields and embeds an in-place code editor with **syntax highlighting, bracket matching, and real-time JSON validation**. ### Minified HTML in Content Assets Third-party content migrations and rich-text imports frequently strip line breaks from content asset markup. Reformatting minified HTML with 1-click beautification lets you inspect DOM hierarchy and inline ISML markup instantly. ### In-Place Content Asset XML Export Normally, sharing a content asset across sandboxes requires setting up an export job in `Administration > Operations > Site Import & Export`, configuring an export data unit, downloading the archive from WebDAV, and unzipping it. With the DWithEase asset download shortcut, clicking the **Download Asset** icon on the asset editor exports the raw XML snippet directly to your local machine in under two seconds. --- ## 4. Solve "Where Does This Come From?" on the Storefront One of the largest time sinks in SFCC development is diagnosing unexpected content on the storefront. When a banner, disclaimer, or promotional element renders incorrectly, you are forced to ask: - Is it an **ISML template** hard-coded into the cartridge? - Is it a **Content Slot** assigned to a specific category or schedule? - Is it an independent **Content Asset** embedded via an `` tag? ``` ┌─────────────────────────────────────────────────────────────┐ │ STOREFRONT MARKUP DETECTIVE │ ├─────────────────────────────────────────────────────────────┤ │ ISML Template ──► Governed in cartridge repository code │ │ Content Slot ──► Configured in BM: Online Marketing │ │ Content Asset ──► Authored in BM: Content Management │ └─────────────────────────────────────────────────────────────┘ ``` Guessing requires searching cartridge code repositories, inspecting network requests, or hunting through Business Manager slot configurations. ### Visual Content Inspection (Highlight Content) Toggling **Highlight Content** in the DWithEase toolbar overlays clear visual borders over the live storefront: - **Blue outlines** denote Content Slots. - **Green outlines** denote Content Assets. - **Clicking any highlighted boundary** opens the corresponding record directly inside Business Manager in a new tab. This transforms a ten-minute code search into an instantaneous two-second jump. --- ## 5. Prevent Session Expiry from Derailing Flow Business Manager sessions default to strict timeout windows (often 15 to 30 minutes). When you are testing templates in your IDE, inspecting logs, or reviewing pull requests, returning to Business Manager often presents an expired session screen. Re-authenticating requires: 1. Entering your two-factor credentials or SSO. 2. Selecting your site context again. 3. Navigating back to the exact record you were editing. 4. Re-entering any unsaved changes lost during the timeout. Enabling **Session Keep-Alive** and **Automatic Login** in the [DWithEase Sandbox Options](/docs/options/) sends lightweight background heartbeat pings while your browser tab remains open. Your session stays active for up to 24 hours, ensuring that when you return to Business Manager, your form inputs, filters, and editing state remain intact. --- ## The 5-Habit Summary Adopting these five habits eliminates dozens of unnecessary interruptions every working day: 1. **Stop drilling menus**: Use the DWithEase persistent toolbar or top search bar for Cache, Code Versions, and Search Indexes. 2. **Keep hands on the keyboard**: Use Ctrl + S to save changes instantly across preference and content screens. 3. **Format before editing**: Utilize in-browser JSON/HTML beautification to avoid syntax syntax errors in custom preferences. 4. **Inspect storefronts visually**: Use **Highlight Content** to jump from storefront elements directly to their Business Manager records. 5. **Protect your focus**: Enable session keep-alive to eliminate mid-day authentication loops. ]]> <![CDATA[Working Across SFCC Sandboxes Without Losing Your Place]]> https://dwithease.com/resources/working-with-sfcc-sandboxes/ https://dwithease.com/resources/working-with-sfcc-sandboxes/ Thu, 20 Aug 2026 10:00:00 GMT