Release notes: Jan 17th - Jan 18th, 2026

It has been implemented to optimize the export process through a revised logic for selecting entities to be exported, ensuring improved accuracy, efficiency, and consistency in the output.

It has been implemented so that a refresh option is available in the workflow query list within the qualification rule, enabling users to update and retrieve the most current data dynamically without the need to reload the entire interface.

It has been implemented so that the workflow history table now supports standardized date formatting and configurable custom date filters, enabling more accurate data interpretation and efficient temporal querying.

It has been implemented so that the edit function under Category has been changed from inline row editing to a pop-up-based interface. In addition, locales are now arranged alphabetically to facilitate easier navigation and editing in both the pop-up and grid views.

It has been implemented so that the Workspace add/update modal has been updated to align with the new UI and now includes a Configuration type with available subtypes of Control Center and Workflow. In the Control Center view, only workspaces with the Control Center subtype are displayed. Additionally, on the Entity Overview page, links are now sorted according to the Control Center sort order.

NB! Important Notes:

• Required permission: ManageSharedWorkspaces

It has been implemented so that the Shopify adapter now supports product-to-product relationships.

It has been implemented so that, in Brand Store v2, entity link data can be shared with store users through the Link Entity mechanism. Customers using the Link Entity concept in the PIM portal can now include data stored on the relationship between two entities when sharing information with the store.

This enhancement allows additional parameters defined on entity relationships—such as attributes describing how two products or objects are related—to be shared and made visible to store users, providing a more complete and accurate representation of product data.

Previously, only entity-level data could be shared, which limited the visibility of relationship-specific details. With this implementation, all relevant contextual data, including attributes defined on the link itself, can now be shared and consumed in the store.

It has been implemented so that, in Brand Store v2, Store Configuration Templates can be created and managed by Brand Store administrators for reuse across multiple stores that share the same base configuration for models and data fields.

This enhancement enables common settings—such as entity types, link types, resource configurations, and shared fields—to be defined and maintained centrally, while still allowing individual stores to differ in data assortment, search and filter behavior, or language settings.

By introducing reusable configuration templates, managing multiple stores becomes more efficient and consistent. Configuration updates only need to be performed once and are automatically applied to all stores using the template, reducing manual effort and minimizing the risk of configuration drift.

It has been implemented so that, in Brand Store v2, the Storefront filter panel now includes a Clear All option, allowing all active filters to be reset in a single action. Both taxonomy-based and field-based filters are cleared simultaneously, automatically refreshing the search results and resetting the view. This enhancement enables users to quickly start a new search without the need to remove filters individually.

It has been implemented so that, in Brand Store v2, Storefront filters now display only relevant options based on the data shared within the store. Filter selections are limited to values present in the current store dataset, ensuring that every chosen option returns results and making the filtering experience more intuitive and reliable.

It has been implemented so that, in Brand Store v2, Storefront cart items can now be sorted by Display Name or Display Description in either ascending or descending order. The selected sorting is consistently applied in the cart view as well as in generated outputs, including files and PDF catalogs, providing enhanced control over the organization and presentation of product data.

It has been implemented so that, in Brand Store v2, Storefront cart items can now be reordered using drag-and-drop functionality. This allows users to manually arrange products in the desired sequence, with the custom order immediately reflected in the cart and preserved in generated outputs, including files and PDF catalogs, providing full control over the presentation of product data.

It has been implemented so that, in Brand Store v2, users can now select specific resource formats when exporting resources as URLs from the Store. This ensures access to URLs for the transformed versions of media assets, providing greater flexibility in resource exports and aligning the functionality with the behavior previously available in Content Store.

It has been implemented so that, in Brand Store v2, PDF downloads now support custom page sizes. This allows metatag settings to be applied and page dimensions to be overridden with user-defined height and width, providing greater flexibility in document layouts and ensuring that PDFs meet specific formatting requirements within the Brand Store.

It has been implemented so that, in Brand Store v2, PDF template previews in Store Admin are now generated using the same rendering engine as the Storefront. This ensures consistency with the final PDF output and allows previews of PDF templates even before they are saved, providing a reliable and aligned preview experience in both the PDF Template Admin and cart PDF preview.

It has been implemented so that, in Brand Store v2, the Store Admin wizard now tracks the last modified step, enabling draft stores to automatically open at the most recently updated step when accessed. To support this functionality, draft stores no longer permit unrestricted navigation between steps, ensuring a clearer and more controlled configuration workflow.

It has been implemented so that, in Brand Store v2, Store Admin users can now add multiple search and filter fields in a single operation within the Data step of the Store wizard. The modal remains open while fields are added and can be closed once finished, reducing repetitive interactions and streamlining the store configuration process for greater efficiency.

It has been implemented so that, in Brand Store v2, the Data step in the Store wizard now displays entity type information more prominently for each field. This enhancement improves readability, making it easier to distinguish between fields with the same name across different entity types and providing a clearer, more consistent Store Management experience.

It has been implemented so that, in Brand Store v2, Store Admins can now add users directly within the Access step of the Store wizard. If a user is not listed, there is no need to exit the wizard to add them, streamlining store setup and making the process faster, smoother, and more efficient.

It has been implemented so that, in Brand Store v2, the user list in Central User Management now displays each user’s last active date. This information is updated with every sign-in, enabling Store Admins to more effectively monitor active users, manage access, and maintain up-to-date user lists.

We have applied a solution to ensure that localized category names are correctly displayed by prioritizing the model language, falling back to the master language, and defaulting to the category ID if needed.

We have applied a solution to ensure that retrieving all available fieldsets via the REST API (/api/v1.0.0/model/fieldset) returns the most up-to-date data after a field type has been removed from a fieldset (/api/v1.0.0/model/fieldset/{fieldSetId}/{fieldTypeId}), preventing stale or inconsistent results.

We have applied a solution to ensure that users with the Customer role are automatically redirected to the Portal login page two seconds after successfully confirming their email or updating their password on the "Change Your Password" page, streamlining the workflow and enhancing the overall user experience.

We have applied a solution to ensure that, in the REST API, the PUT /api/v1.0.0/entities/{entityId}/specificationvalues endpoint now validates the request payload and returns a 400 Bad Request response when one or more specificationFieldTypeId values are invalid or do not exist for the entity being updated.

We have applied a solution to ensure that, in the REST API, simultaneous calls to the POST /api/v1.0.0/entities:upsert endpoint that result in a unique constraint violation now return a clear, user-friendly error message instead of the previous generic internal_server_error response.

We have applied a solution to ensure that Inspire Drawer unmounting warnings are prevented by properly nullifying references, while also improving event management and implementing an event reset mechanism to avoid multiple event triggers within the Inspire Drawer.

We have applied a solution to ensure that, in Inspire Table View, generated text is no longer treated as a valid CVL value.

We have applied a solution to ensure that users can navigate the visual workflow builder to any viewpoint beyond the original view and can also return to the starting position or previously selected elements as needed.

We have applied a solution to ensure that, in Brand Store v2, the Cart button is now correctly displayed in the mobile view, resolving the issue where it was previously not visible.

We have applied a solution to ensure that, in Brand Store v2, HTML template compatibility issues between Content Store and Brand Store v2 are resolved, and PDF rendering now behaves consistently with Content Store.