Asset Family Configuration: Form Editor Guide
This guide covers the form-based editors for configuring Product Link Rules, Naming Conventions, and Transformations on Asset Families.
All three editors are accessible from the Product Link Rules tab (for PLR and Naming Convention) and the Transformations tab on an Asset Family's edit page. Each editor includes a Form / JSON toggle, allowing you to switch between the visual form editor and the raw JSON editor at any time.
Naming Convention
The naming convention automatically extracts structured information from asset codes or filenames to populate asset attributes.
Empty State
When no naming convention is configured, you will see an Add naming convention button.
Configuring a Naming Convention
Click Add naming convention to display the configuration form. The form contains:
| Field | Description |
|---|---|
| Source property | Select Code or the main media attribute to extract the naming pattern from. |
| Channel | Only shown if the main media attribute is scopable. Leave empty if not needed. |
| Locale | Only shown if the main media attribute is localizable. Valid locales are filtered based on the selected channel. |
| Pattern | A regular expression with named capture groups, e.g. /(?P<product_ref>.+)_(?P<attribute_ref>.+)/. Capture group names must match existing asset attribute codes. |
| Abort asset creation on error | When set to Yes, assets will not be created if the naming convention fails to match. |
Note: When Code is selected as the source property, the Channel and Locale fields are automatically cleared and hidden, since asset codes are neither scopable nor localizable.
Removing a Naming Convention
Click the X button in the top-right corner of the naming convention card to clear all settings. The configuration will be reset to empty, and you can save the asset family to persist the change.
Product Link Rules
Product link rules automatically link assets to products based on configurable conditions. You can define up to 2 rules per asset family.
Empty State
When no rules are configured, you will see an Add rule button.
Adding a Rule
Click Add rule to create a new rule. Each rule has two sections:
Product Selections
Product selections define which products will receive the asset. Multiple selections combine with AND logic.
| Field | Description |
|---|---|
| Field | The product field to filter on (e.g. sku, categories, family, enabled). |
| Operator | The comparison operator: =, !=, IN, NOT IN, EMPTY, NOT EMPTY, STARTS WITH, CONTAINS, DOES NOT CONTAIN. |
| Value | The value to compare against. For IN/NOT IN operators, enter multiple values as tags. You can also select an asset attribute using the {{attribute_code}} syntax to dynamically match. This field is hidden when the operator is EMPTY or NOT EMPTY. |
| Channel | Optional. Specify if the product field is scopable. |
| Locale | Optional. Specify if the product field is localizable. Valid locales are filtered based on the selected channel. |
Click Add selection to add additional product selection conditions within the same rule.
Assign Assets To
This section defines which product attribute receives the asset and how. The attribute dropdown is populated with available asset collection type attributes. If no asset collection attributes exist, a warning is displayed with a link to create one (if the user has attribute creation permissions).
| Field | Description |
|---|---|
| Attribute | The product attribute (must be an asset collection type) to assign assets to. Selected from a dropdown of available asset collection attributes. |
| Mode |
add appends assets to existing ones. replace overwrites existing assets. |
| Channel | Only shown if the selected attribute is scopable. Valid locales are filtered based on the selected channel. |
| Locale | Only shown if the selected attribute is localizable. |
Click Add assignment to assign assets to multiple product attributes from the same rule.
Sorting Options (feature flag)
When the enable-asset-manager-plr-sorting-enhancement feature flag is active, each assignment includes a collapsible Sorting options section. This section auto-expands if any sorting value is already set.
| Field | Description |
|---|---|
| Sorting direction |
asc or desc. |
| Sorting attribute | The product attribute to sort by (free text). |
| Sorting fallback |
code, updated_at, or created_at. Used when the sorting attribute value is empty. |
Dynamic Locale/Channel Assignment (feature flag)
When the enable-asset-manager-plr-dynamic-locale-channel feature flag is active, each assignment includes a collapsible Dynamic assignment section. This section auto-expands if any value is already set.
| Field | Description |
|---|---|
| Assign locale from attribute | A product attribute whose value determines the locale for the assignment. |
| Assign channel from | A product attribute whose value determines the channel for the assignment. |
Multiple Rules
You can add up to 2 rules. Each rule card displays its rule number and has its own X button to remove it. When two rules are defined, the Add rule button is hidden.
Removing Rules
- Click the X button on a rule card header to remove that individual rule.
- Removing all rules results in an empty configuration (
[]), which can be saved without errors.
Transformations
Transformations automatically generate media variations (e.g. thumbnails, resized images) from source files. You can define up to 10 transformations per asset family.
Empty State
When no transformations are configured, you will see an Add transformation button.
Transformation Card
Each transformation is displayed as a collapsible accordion card. Click the card header to expand or collapse it. The card header shows the transformation label and a summary of its operations (e.g. "Scale, Colorspace").
Drag-and-Drop Reordering
Transformations can be reordered by dragging the handle on each card header. The order determines the processing priority — transformations are applied in the order they appear.
Configuring a Transformation
An expanded transformation card contains the following sections:
Label
A name for the transformation, used in error messages (e.g. "Thumbnail_160x160").
Operations
One or more image operations applied in sequence. Available operation types:
| Operation | Parameters | Description |
|---|---|---|
| Resize | Width (px), Height (px) | Resizes without maintaining proportions. |
| Scale | Width (px), Height (px), Ratio (%) | Resizes while preserving proportions. At least one parameter required. |
| Thumbnail | Width (px), Height (px) | Generates a thumbnail with cropping to maintain proportions. |
| Colorspace | Colorspace (RGB, Grey, CMYK) | Converts the image colorspace. |
| Resolution | Resolution X, Resolution Y, Unit (PPI, PPC) | Changes image resolution. |
| Optimize JPEG | Quality (1-100) | Converts to JPEG with quality control. Should be the last operation. |
| ICC Strip | (none) | Removes ICC color profile data. |
| Remove Background | Background color (Transparent, Black, White), High precision (Yes/No) | AI-powered background removal. |
| Aspect Ratio | Ratio (preset or custom). Presets: 1:1, 2:3, 3:2, 4:5, 5:4, 9:16, 16:9. Select Custom to enter any ratio. | Adjusts aspect ratio by adding white borders. |
| Auto Crop | (none) | AI-powered margin removal around main subjects. |
| Prompt | Prompt text (max 1000 characters) | AI-powered image transformation based on a text prompt. |
Note: The list of available operation types is dynamically loaded from the backend. New operations added server-side automatically appear in the dropdown without frontend changes. If an operation type does not have a dedicated form, a raw JSON parameter editor is shown as a fallback.
Click Add operation to add another operation to the transformation. Each operation card has an X button in its top-right corner to remove it (when more than one operation exists).
Source
Select the source media file attribute and optionally specify a channel and locale. Channel and locale fields only appear if the selected attribute is scopable/localizable respectively. Valid locales are filtered based on the selected channel.
Target
Select the target media file attribute where the generated variation will be stored. Once set as a target, the attribute becomes read-only in the asset edit form. Channel and locale fields behave the same as for the source.
Filename
Configure a prefix and/or suffix for the generated file. At least one must be set. Defaults to suffix _transformed. For example, a source file packshot.jpg with suffix _thumb generates packshot_thumb.jpg.
Removing Transformations
- Click the X button on a transformation card header to remove it.
- Removing all transformations results in an empty configuration, which can be saved cleanly.
Form / JSON Toggle
All three editors include a Form | JSON toggle in the section header. This allows you to:
- Use the Form view for guided, visual editing.
- Switch to JSON view to see or edit the raw JSON configuration directly.
Changes made in one view are reflected in the other when you switch.
Saving Changes
After making any configuration changes, click the Save button in the page header. The page will display an "Unsaved changes" indicator when modifications have been made but not yet saved.