菜单
Practical guide for using WebDAV in Salesforce B2C Commerce Cloud for IMPEX transfers and log access. Use this when setting up WebDAV clients, debugging WebDAV permission issues, or designing automation that reads/writes files via WebDAV.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide for using the evaluate_script tool to execute JavaScript on SFCC instances via the script debugger
Guide for creating and maintaining user-facing agent skills
Mandatory preflight for MCP server design/review/audit tasks. Defines production best practices for architecting, securing, testing, and operating TypeScript MCP servers, including transport design, schema validation, error handling, and deployment.
Register SFCC hooks via cartridge package.json and hooks.json. Use when adding hooks or troubleshooting hook registration.
Guide for implementing logging in Salesforce B2C Commerce scripts
Unified caching playbook for SFCC (page cache vs custom cache vs service response cache). Use this when improving performance, reducing external calls, designing cache keys/TTLs, or debugging stale cache behavior.
| name | sfcc-webdav-workflows |
| description | Practical guide for using WebDAV in Salesforce B2C Commerce Cloud for IMPEX transfers and log access. Use this when setting up WebDAV clients, debugging WebDAV permission issues, or designing automation that reads/writes files via WebDAV. |
WebDAV is SFCC’s “remote filesystem over HTTP”. It’s central to:
This skill focuses on practical workflows and the most common permission and path pitfalls.
[ ] Confirm which auth path you are using: BM user (Basic Auth) vs API client (client-id/secret token)
[ ] For IMPEX, ensure the BM role includes File Transfer Manager access
[ ] If using API client auth, generate credentials in Account Manager
[ ] Verify directory permissions are configured in Business Manager for the exact folder(s)
[ ] Avoid overlapping WebDAV client permission paths (SFCC restriction)
[ ] Don’t expect write access to restricted folders (e.g. security logs)
[ ] For automation: scope access to the minimum folders required
/catalogs/* or “all other folders”) grant access to future subfolders automaticallyThese vary by project, but the patterns are stable:
| Folder | Typical use | Read/Write? |
|---|---|---|
/impex/src/ | Upload import feeds, export results | Usually read/write |
/impex/src/logs/ | Some log exports and job artifacts | Often read |
/Logs/ | Log files (application logs) | Usually read |
/catalogs/ | Catalog assets (shared library content, images) | Often read |
/cartridges/ | Code deployment via WebDAV (teams vary) | Usually read/write for deployment users |
WebDAV_Realm_Access, WebDAV_Manage_Customization, WebDAV_Transfer_Files./catalogs/* or “all other folders”), permissions apply to future subfolders automatically unless sub-permissions are set explicitly.client_id → permissions array of { path, operations }.Operations typically include: read, read_write.
SFCC does not allow different WebDAV client permission paths to overlap.
Example of what to avoid:
/impex/src/impex/src/fooDesign your permission model so each client owns a non-overlapping subtree.
Some directories are effectively read-only for security reasons (for example, security log directories). Expect permission errors even if you attempt to grant write.
Create separate API clients for:
/Logs/)/impex/src/)This keeps credentials and blast radius smaller.
When storefront requests can’t write files, a common SFCC pattern is:
/impex/src/ (or another allowed folder)(See also: sfcc-platform-limits for storefront file I/O constraints.)