sections in the article
This article provides an overview of the Plan & Release functionality in inriver.
About inriver Plan & Release
The Plan & Release functionality allows you to monitor the content sent to outbound channels and publications.
On the dashboard, you will find the following navigation menu options:
Takes you to the channel where you can start working on it.
Creates a bookmark on the start page of Enrich and moves the channel first in the Plan & Release dashboard.
Open in new tab
Opens the channel in Enrich in an entity overview, in a new tab.
Open in enrich
Opens the channel in Enrich in an entity overview.
Prevents the channel from being published via a connector.
Removes the channel and all the links to its content.
You also have seamless access to your Tasks in the task widget.
Channels and publications
A Channel is basically an organized collection of entities that you want to publish. Entities are a core concept in an inriver solution. By associating a channel to an outbound connector, your product information will be published to different receiving systems.
A Publication is similar to a channel, except that the information will be set up for Print via an InDesign connector. Read more about the inriver Print Plugin in this article.
Both Channel and Publication entities are created in inriver and support FieldTypes and LinkTypes the same way as other entities.
You can create a new channel or publication in the top navigation toolbar.
Selecting a channel brings you to the Channel completeness tab. From here you can easily view the channel readiness, also known as completeness.
Selecting the Structure tab on the channel is where you manage channel nodes in a selected channel. They can be added, moved, or removed.
In the field to the left, you can open a work area just like in Enrich or quick search. This is very useful when populating a channel.
In the field to the right, you can manually add products or create link rules/queries to build out the channel node.
To leverage the full potential of your inriver solution, it is important to create a Data model that makes product enrichment both easy and efficient. Plan & Release lets you build a channel structure that supports the way an outbound system expects to consume the product information. If your channel structure is large, use the filter search box to find different channel nodes.
Warning: Limit the number of products within each Channel Node to less than 2000 products. The performance will significantly reduce as the number of entities within channel nodes increases.
When working with a channel you can utilize the entity toolbar at all times. The options are:
Creates a bookmark of the channel on the start page of Enrich and moves the channel first in the Plan & Release dashboard.
Edits fields in a pop-up widget.
Open details in enrich application
Takes a shortcut to Enrich where you find the selected channel in the entity overview.
Locks the entity so that no other user can work on it.
System info about the channel.
Allows or prevents the channel from being published via a connector.
Rebuilding or synchronizing a channel
It is possible to rebuild or synchronize a channel when the structure or content is out of sync or corrupt. This is not something that you should do often.
You can read more about Missing channel nodes for instructions on how to rebuild or synchronize a channel.
Will try to resolve and rearrange the entities within a channel. If the structure is corrupt, this will not fix the problem and you will have to use Rebuild Channel.
Will completely remove the channel structure and build it up again from scratch, based on the actual links. This can take time and should be used with caution.
Warning: Do not run both jobs at the same time.
Caution: Do not use extensions to rebuild channel structure. This can lead to sync issues if updates to the channel aren't pushed. Rebuilding should be done rarely and only by using the options provided by the user interface.
Caution: Using Rebuild Channel is not part of a normal workflow. It is a disaster recovery method in case something goes wrong with a channel structure. It is a large and time-consuming process that causes performance loss.