2021.12.0 - June 9, 2021

Environments

Preview, Admin-FTS

Virtual Photographer

Composite assets are used to set up layered rendering to dramatically reduce the number of renders for complex products and to improve the performance for end users. Now, Composite assets have been decoupled from Catalog Items so that they can be reused with multiple Catalog Items.

Composite assets can be associated to Items using the the new Composite reference field on Catalog Items:

Composite assets can be created from the Assets sections of the platform:

Composite assets can be previewed with Catalog Items using the preview dropdown:

Attributes can be associated with Composite assets by going to the Logic tab and adding Global Attributes that are also associated with the Item(s). Then, the attributes can be associated with layers:

Composite assets can use Logic for granular and dynamic control. For example, a Composite asset can behave differently depending on the Item that's referencing it:

Existing Composite assets

Existing Composite assets will continue to work and can be migrated to the decoupled Composite assets

Editor

Meshes can now be merged in the Editor to simplify asset node structures. Nodes can be multi-selected using shift + click. Right click and select the Merge meshes.

Merged meshes can be renamed:

Merged meshes will appear at the bottom of the node tree:

Bugs/Cases

  • GL6374 - On the preview asset page, the metadata is in edit mode even you didn't click edit button

  • GL6972 - Get hiddenValues and dsiabledValues array back on attribute data

  • GL6995 - Can't open the render page of an item, high CPU usage

  • GL7034 - App call not taking existing query params into account

  • GL7059 - 500 error when click Render button on an item

  • GL7061 - Material Instances do not propagate Template Override correctly

  • GL7068 - Metadata Rule in Assets don't work as expected

  • GL7071 - The value with feet symbol ' can't be queried in datatables rules logic

  • GL7078 - Data Table queries - Global Attributes not selectable using the UI in the where clause

Last updated