Impact analysis and guidance : Retail case table updates<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Retail Case Table Made Abstract – Customer Impact We have made improvements to the data model in the latest version of the Retail Core application; the Retail Case table will be made abstract when you upgrade to our latest Yokohama or Zurich release which may require customers to make changes to their existing implementation. Note: This change will affect your implementation only when you upgrade to version 5.1.0 (Yokohama) or 5.2.0 (Zurich) of Retail Core. Why are we making this change? An abstract case (or abstract case type) refers to a base configuration of a case that is not meant to be used directly but is instead designed to be extended by specialized case types. The abstract Retail case(sn_retail_case) will include only the shared logic such as common fields, Business rules, flows, UI policies, and access controls (ACLs). Each specific case type will then extend this base and focus solely on its unique logic. Why this matters: Cleaner architecture: Case types won’t carry unrelated or unused logic, keeping each implementation focused and easy to manage. Easier to scale: As new use cases emerge (like Recall Case or Audit Case), they can be added without the risk of impacting existing logic, eliminating the need to refactor or untangle shared components. Tailored experiences: You can configure dedicated Workspace experiences per case type, avoiding the complexity and clutter of one-size-fits-all layouts. We’re confident this change will make your system more robust and future-ready, while simplifying ongoing configuration and support. Additionally, we are also shipping out of the box case types that can be readily used for various use cases. Please review the impact below to assess any changes needed for your current implementation. Summary of Change What Changed: The Retail Case table (sn_retail_case) has been marked as abstract by setting its Create/Update ACL to nobody. Purpose: This enforces best practices by ensuring customers extend from the Retail Case table rather than directly creating records on it. When: This change will affect your implementation only when you upgrade to version 5.1.0 (Yokohama) or 5.2.0 (Zurich) of Retail Core. Impact Areas Component Impact Level Details & Required Action Direct Usage of Retail Case Table Major If a customer is directly creating or managing records in the sn_retail_case table (not recommended or supported), these operations will now fail as the table is abstract. Action: Migrate all data and operations to a properly extended table (e.g., x_retail_mycase). And define explicit ACLs on the extended table. Access Control Lists (ACLs) – Inherited Minor If customers rely on inherited ACLs from sn_retail_case, they may lose Create/Update access due to the table becoming abstract. Action: Define explicit ACLs on the extended table to retain functionality. Access Control Lists (ACLs) – Customer-defined No Impact If customers have already created their own Create (C) and Update (U) ACLs on the extended table, no impact is expected. Suggest to do sanity testing to confirm no issues. Recommended Actions for Customers Review Extensions: Ensure that all usage is on extended tables, not directly on sn_retail_case.Update ACLs: If relying on inherited ACLs, define explicit Create/Update ACLs on your extension tables.Check Retail Portal Widgets and pages. Support If you need help adjusting to this change, our support team can assist in: Identifying affected areasUpdating ACL configurationsRefactoring navigation and portal usage