Automatically Link Assets

In the Administration > System > Automatic links page, you can use Quable’s rule engine to specify the conditions for automatically linking uploaded assets to your existing documents.

❗️

An automatic link only works for a single document type. You must create individual automatic links for each document type that you want to automatically link your assets to.

Naming Convention

Automatic links require that your assets use a specific naming convention. This naming convention is interpreted by the defined rule to know which documents to link the assets to. Therefore, all assets that should be linked via a specific automatic rule must follow the same naming convention.

👍

To make the process as easy as possible, we highly recommend keeping your naming convention simple. Your Quable PIM Product Manager can provide you a template to help you create your own naming convention.

In order to link an asset to a document, Quable PIM needs one piece of information in the asset's name:

Example 1

You need to automatically link assets to your product document type with the product_main_pictures link type. Your Quable PIM administrator has created an automatic rule to look for this naming convention:

The rule looks for:

• segments with specific data types,
• separated by underscores ( _ ), and
• a file extension.

The following table provides a breakdown of the segments in this example.

To comply with this rule for an automatic link, your assets could be named:

As long as the name of the assets are in the correct format and include the document type code and the number 1, the assets will automatically be linked to the correct documents.

Example 2

You need to automatically link assets to to your product document type with the product_pictures link type. Your Quable PIM administrator has created an automatic rule to look for this naming convention:

The rule looks for:

• segments with specific data types,
• separated by parenthesis ( ( ) ) and a hyphen (- ), and
• a file extension.

The following table provides a breakdown of the segments in this example.

To comply with this rule for an automatic link, your assets could be named:

Create Automatic Link Rule

🚧

Prerequisite

Coding skills may be required since the process includes creating a regular expression (regex) and two JSON (JavaScript Object Notation) statements.

Step 1: New Rule Form

In the Administration > System > Automatic links page, click the New Rule button. A form is displayed to define the automatic link rule.

Step 2: Rule Name

Define a name for the automatic link rule. The name should be as descriptive as possible.

Step 3: Rule Event

When an asset is imported into Quable PIM, it's a mediaupload event. This is the type of event that triggers the initiates the automatic link rule.

Step 4: Rule Conditions

Define a JSON statement with the conditions that must be met for the rule to apply:

Step 5: Rule Action

Define a JSON statement with the action to take if the conditions defined in the Rule if statement are met:

Example

You have a product document type with an attribute whose code is color. The attribute has two possible values (red, blue). To link the blue.jpg asset to all documents of the product type with blue as the value for the color attribute, your rule would look like:

This is a closer look at a Rule if statement:

{
    "target_document_type": "product",
    "target_value_type": "eav",
    "target_value": "color",
    "rule": "equal",
    "from_value_regex": "\/^([a-zA-Z0-9]*)\\.[jpg|png]\/",
    "from_value_type": "originalfilename",
    "from_value": ""
}

This is a closer look at a Rule then statement:

{
"action": "createXObject",
"document_type": "article_images_media",
"side_entity": "target"
}

Use Cases

1. Link to multiple documents

{
    "target_document_type": "finished_product",
    "target_value_type": "eav",
    "target_value": "design",
    "rule": "equal",
    "from_value_regex": "/^([a-zA-Z0-9]*)+_[a-zA-Z0-9_]*\\.[mp4|wav]/",
    "from_value_type": "originalfilename",
    "from_value": ""
}

{
"action": "createXObject", 
"document_type":"picto_image", 
"side_entity": "target"
}

2. Link to document and variant

2.a Use specific link

3. Link to multiple document types