sections in the article
Intelligent linking allows you to automatically include or exclude Links between Entities, based on predefined rules and queries. This saves you from having to link Entities manually since you can apply predefined criteria for when a Link should exist.
About intelligent linking
Intelligent linking allows you to automatically create Links between Entities, based on predefined rules and Queries. This saves you from having to link Entities manually since you can apply predefined criteria for when a Link should exist.
You can work with this functionality in the following areas:
- Enrich
You can use this functionality when working with Entities' Includes tab.
- Plan & Release
The most common area to work with intelligent linking. Based on rule conditions you can link Products or any other Entity type to relevant Channel Nodes.
- Through the DataService API.
Both rules and Queries can be used to specify if and when a Link should be created. Rules use Field values to trigger the Link creation, while Queries define dynamically which Entities should be linked to a parent Entity.
In Plan & Release this allows us to have Nodes that use two linking methods:
- Nodes that use manual linking
- Auto-configuring Nodes that use intelligent linking
You can link more than one Entity type to a Channel Node.
Manual linking
Using this approach, you drag and drop Entities into the Channel Node to create the Link. A customized Extension can also perform a similar operation.
Unlinking all relations
You can delete all Links to a particular Link type by using the Remove all relations option available in the Link type menu.
This option is only available for users with appropriate permissions. Ask your system admin for details.
You cannot unlink all Entities to Link types that have Link rules / Link rule Queries. Remove the Link rule / Link rule Query first before unlinking all Entities from this Link type.
In Plan & Release > ... > Structure
do the following:
- Select a Node from the structure
- Navigate to the Content tab
- Click (Link type menu) > Remove all relations
The Confirm remove relation of ALL related entities modal appears.
- Click OK
The relations removal is added on Jobs.
Intelligent linking allows for auto-configuring Nodes
In each Channel Node, you can set a rule that determines which Entities should be automatically linked to the Node based on the specified criteria. This makes the Nodes auto-configure and lets inriver decide when an Entity has been completed and is Channel-ready.
Auto-configuring Nodes let you define where a Product should be used. Several Channel Nodes can be defined for any Product.
Configuring intelligent linking
The configuration is defined per Entity and outbound LinkType.
In Plan & Release > ... > Structure
do the following:
- Select a Node from the structure
- Navigate to the Configure tab
- Use the available configuration options to specify when a Link should exist.
Create rules to specify that a Field should have a certain value.
Create queries to define which Entities should be linked.
Click (Save) when you are done.
DataService API Linkruledefinitions
Intelligent linking can be created through the DataService API by adding LinkRuleDefinitions.
LinkRuleDefinition AddLinkRuleDefinition(LinkRuleDefinition definition)
This creates a LinkRuleDefinition, which is a container with a list of rules and a list of queries.
After setting up intelligent linking, make sure you run the job Update Link Rule Definitions in Control Center. See Jobs in Control Center for more information.
Link rule limitations
An auto-configured Node can only manage one Entity type. It would be impossible to create a rule or query that includes both Products and Category Info. Therefore, you must manage additional Entity types using the standard Enrich interface. You can add rules for additional Entity types in the Includes tab in Enrich. See Intelligent linking in inriver Enrich.
It is not possible to combine the two methods of linking. As soon as you create a rule or Query for a Node, the system will prevent you from manually linking Entities to it. If you try to drag any type of Entity into the Contents tab of the Node, it will not accept it.
Integration considerations
It is also necessary to ensure that the integration solution is designed to manage different Entity types in one Channel Node.
Further reading
Rules and queries in inriver Plan & Release
Intelligent linking in inriver Enrich using rules and Queries
Comments
0 comments
Article is closed for comments.