This month’s update focuses on stronger data control, clearer API output, and more flexible configuration options across Struct PIM.
This changelog introduces a set of improvements designed to give teams better visibility, stronger governance, and improved organization as product setups grow in complexity.
Here’s what’s new this December.
New features
Global control of fallback visibility on entity attributes
Fallback values play an important role when working across languages, markets, and shared data structures. With this update, you can now control fallback visibility globally on entity attributes.
A new toggle has been added to the top-right corner of the entity view, allowing you to enable or disable the display of fallback values across all attributes at once.
This makes it easier to:
- Review data in the current language or market without inherited values
- Quickly switch context when validating localized or market-specific content
- Identify missing values and assess attribute completeness more efficiently
Instead of adjusting fallback visibility on individual attributes, teams can now change how data is presented with a single action.
Enhancements
Support for rendered values from browse endpoints
Browse endpoints now support rendered, human-readable values.
This enhancement improves how data is exposed through the API, making responses easier to understand and work with - especially when dealing with complex data structures.
By returning rendered values directly, teams can now reduce the need for additional processing and interpretation.
You can learn more about how to use the endpoint here.
New and improved conditions added to business rules
Modified by and created by conditions
When setting up a business rule, you can now use “created by” and “modified by” as conditions.
This allows workflows and validations to react directly to user actions by taking into account who originally created data and who is currently making changes. The conditions can be used to distinguish between different types of users, such as system users and manual editors, and to control rule behavior accordingly.
By adding user context to rule logic, it becomes easier to build automations that better reflect real operational workflows and governance requirements.
Multiselect support for category condition
When setting up a condition that checks whether an entity is classified in a category, it is now possible to select multiple categories within the category tree.
This allows a single rule to apply across several categories and their subcategories, making it easier to cover complex or overlapping catalog structures. Instead of creating separate rules for each category, rules can now be defined once and reused across multiple product groups.
This provides greater flexibility when defining category-based rules and reduces the need for creating multiple, duplicate configurations.
Nested folders for global lists
Global lists can grow quickly in larger setups, making structure and overview increasingly important. With this update, global lists can now be organized using nested folders.
When creating or editing a global list folder, you can assign a parent folder, allowing folders to be structured in multiple levels. To support this, additional context has been added to the interface:
- A full path column on the Global list folders page
- A folder path column on the Global lists page
The folder hierarchy is also reflected in the Global lists tree overview, making it easier to navigate, understand, and maintain structured collections of global lists.
To see all the changes and learn more about Struct PIM, explore the full December changelog in our documentation here.
