2021.10.0 - May 13, 2021
Last updated
Last updated
Environments
Preview, Admin-FTS
Global attributes are now available to centralize attribute management and drastically improve Catalog Item to Assets workflows.
To add Global attributes, use the Attributes sub-menu item in the Catalog section:
Global attributes of varying types can be added and are listed on this page:
Note that Boolean attributes can now be used on Catalog Items.
Global attribute settings reflect existing attributes and can be used the same way.
For Part Reference Attributes, setting the Asset Type at the creation step insures Item-to-Asset compatibility. Note that this attribute type's values filter to Catalog Items only.
To add Global attributes to Catalog Items, use the new Global attributes dropdown:
Note that Global Attributes can be used alongside non-global attributes and they can be reordered using the existing drag-to-order feature.
Global attribute Default Values can be overridden on a per-Item basis. You can use the View Attribute button at the top right of each Global attribute to view the attribute settings and modify them.
Note that changes to Global attributes will be reflected everywhere they are used, including Items and Assets.
Global attributes can be added to Assets the same way. The Logic Editor’s Attributes and Rules panel has been made wider for easier management.
Note that Global Attributes are backwards compatible and do not affect any live or projects in progress.
Item Rules can use Tags for conditions and for actions. You can check if an Attribute's value is tagged with a certain tag or tags in Conditions and you can set an Attribute's available values by tag or tags. You can also enable or disable values by tag.
Rules and their actions can be reordered using drag and drop in the same way Attributes can be reordered. Note that Asset Rules and their actions can also be reordered.
Item Description translations are now available in bulk, individual translation exports/import and via APIs.
Note that if you are using a cached version of the Threekit player, you need to reset the cache to see changes to translations. This can be done client side or by re-publishing Items within the platform.
Metadata queries have been added to provide access to Item and Asset Metadata within Asset Rules. You can use Metadata as “read-only” properties to manipulate Product configuration.
In this example, Metadata on a Fabric Catalog Item is used to hide/show a Sofa product part. A Metadata property called “skirt” is added to a Catalog Item with a value of “n”:
In the Model asset for the Sofa Product, the new Metadata Query is used to read the value of this Metadata on any Fabric applied to the Sofa. If this condition returns a match, then the following action is triggered to hide a “node” within the Asset:
The conditions reads as:
For the Fabric attribute
Query metadata
Of the Item setting its value
For the skirt metadata key
That has a value of n
The advantage to this setup is that the Catalog drives the business rule to hide or show the part and the Asset doesn’t need any new attributes and only one Rule.
Metadata queries can also be used as an Action to set a value from a Metadata property. In this example, the value of a Metadata key can be returned and used to set the value of an Attribute within the Asset:
The action reads as:
Set the value of Fabric Lightness
Using metadata value
Set by the Fabric attribute
By searching the metadata of the Asset “Fabric” attribute sets
For the metadata key light
And returning it’s value
The advantage of this setup is that metadata values can be used to drive attribute value for use-cases like positioning elements within a scene or model or sizing.
Set Material action can now create a new instance of a material so that it can be manipulated independently of other instances. In the Set Material action UI, you will see a Link and Unlinked button. By default, all instances are shared, or linked.
Render hours are displayed in a new report in the Analytics section so that Customers can track their render hours daily, monthly, and annually.
Translations can be fetched using the new player.getTranslations() method to build translatable configurator experiences.
Configuration manifests provide improved initial load times and have been automatically added to all projects. Note that an initial configuration needs to be set for this improvement to take affect.
GL6894 - Jobs prioritization added
GL6895 - Unable to select options for number attributes on the Create Render Page
GL6883 - Failed VRay renders
GL6562 - Material assets are now created with two Physical Operators instead of 1.
GL6834 - UI not displaying all configurations
GL6863 - Image operator/configuration rules error
GL6868 - 3D export not showing color/material
GL6882 - The configuration change is not applied after the initialization
GL6897 - Data-table importing values in reversed order
GL6908 - Renders downloaded as jpeg have teal background
GL6926 - Custom Script text color is too light
GL6923 - AR Missing materials when double sided
GL6935 - Configurator prefetch doesn't support number attribute
GL6937 - Rule to limit attribute value not being displayed correctly
GL6942 - Value 0 of the number attribute is not passed into the configuration of AR export
GL6955 - Asset Types got removed in Logic Editor
