We've done a new production deployment with following updates:

This release contains bug fixes and performance improvements.

Saved compositions and pre-built components are now automatically migrated when product rules change. If a product is updated — for example, a material or accessory is removed — existing saved plans stay valid rather than breaking. Managers can define replacement rules in advance, and when needed, end users can be prompted to select a replacement directly in the planner.

This applies to both saved end-user compositions and pre-built components: pre-builds are migrated automatically when the product is regenerated or when an existing pre-built planner is opened.

When adding new parts to a composition while an animation is active (for example, a door is in the open state), newly added parts now immediately match the current animation state. Previously this caused mismatched states where some parts appeared open and others closed.

The navigation bar in UPC has been redesigned and moved to the left side of the screen, making better use of vertical space on desktop displays. The update includes refreshed icons, VividWorks branding, clear active-state highlighting, and a visible indicator for the active tenant alongside the tenant selection link.

The category structure editor now displays options and categories in scrollable columns, replacing the previous layout where the entire page would grow with the content. The options list also uses a consistent UI style with thumbnails and contextual menus, matching the rest of the management interface.

When previewing a product in the management-embedded planner in development mode, you can now select a specific site configuration from a dropdown. This lets you verify that tag-based visibility rules, themes, SKUs, and other site-specific settings behave correctly for a given site — without needing to publish first.

Only site configurations containing the product are available in the selector. The default (no site selected) preserves the existing test-mode behavior.

This release completes the third phase of site configuration capabilities. Phase 1 introduced per-site planner UX customization, Phase 2 brought SKU mapping per site, and Phase 3 now adds tag-based product variant control — enabling manufacturers and their resellers to each have a distinct product offering, all driven by the same underlying product logic.

Tags are the core mechanism: define them once in the Product Library, then use them to control what's available on each site.

For full documentation, see .

You can now use the new built-in function in product scripts to extract a specific property value from each object in an array. This makes working with collections of product components in scripts significantly easier — for example, reading a property across all items in a row, shelf, or group in a single expression. If an item doesn't have the requested property, is returned for that position rather than causing a script error.

The configuration — which lets you cap how many components can be placed in a structure — is now available for all structure types: grid, free placement, and multi-connector. Previously this was only supported in linear structures, requiring workarounds for other layout types.

Starting Plume production deployment. The deployment includes asset data migration so it might take some time for the tenant level asset view to get populated.

We've redesigned the AssetPicker

We have done a production deployment with the following updates:

We've made production deployment today with following updates:

We've added ability to define Grid component rotation rules

We've done a production update.

We have done a small fix deployment on 16.2. with the following content: