Channel configurations

Owned by Natalia Sandovska (Unlicensed)
Last updated: Apr 02, 2018 by Support Ilangl
2 min read

Overview

Localization process can be quite of a challenge considering that several parties are involved. Even those who employ advanced integration solutions face untimely surprises every now and then.

As soon as customer needs to add some extra content to empty slots or developer suddenly decides to modify the layout or install additional module, it will result into a new list of content properties and hence, a new round of localization. At this point you may be facing a dilemma: should you wait for the previously sent content to arrive in order to send a new task (which will be very time consuming) or should you simply resend the whole content for translation?

With ‘Multiple Channel Configuration’ feature, you can create a new channel configuration designated for new (updated) content only.   

What Can Be Done With the ‘Multiple Channel Configurations’ Feature? 

  • Incremental content translation based on properties.
  • Separate workflows can be defined for separate sets of properties within the same content. For example, if you are configuring the metadata properties which are being operated by the SEO workflow, you can also configure other content that is included in the localization workflow.
  • Processing of similar content can be managed in different ways depending on a language. 
  • Each configuration set can be linked with various translation tool templates at the stage of workflow automation.
  • If several localization managers are working with a single data source, personal configuration sets will help you optimize the scope of content for each manager.  

Introduction of the multiple configuration feature on your website can significantly facilitate the workflow. Having a set of different configuration options at hand will help to avoid the possible hiccups which are inevitable if single configuration is used.

Multiple configuration covers a lot of aspects: 

  • Excluded content.
  • Content processing – separate configuration rules for tag and text encoding.
  • Configuration of properties and content types.

Default Behaviors

Usually a business case would require creation of many configurations aimed at specific type of settings. At the same time you still need to update and synchronize available configuration properties. This might be a challenging task since you have to juggle many configurations at once. Every time you change a certain configuration property you need to apply these changes to other relevant configurations. To solve this issue, our system supports default behaviors for excluded content, content type, text and tag encoding settings. You can create a new configuration and mark particular settings as default. In this case our system will use the settings from 'Default Configuration'. You just need to update your "Default Configuration" and these changes will automatically affect all the settings where default behavior is enabled.