Precedence of filter configurations when both content connector and the project template defines filter configurations for document file import
Reference Number: AA-00794 Created: 03-03-2016 12:13 Last Updated: 03-03-2016 12:13 0 Rating/ Voters

Title: Precedence of filter configurations when both content connector and the project template defines filter configurations for document file import

Description:   In some situations, a customer may define filter configurations for files imported in content connector (i.e. choose to import all *.xml files with a specific filter configuration) but also work with project templates which provide a similar feature to choose the filter configuration. It is not trivial which of the two takes precedence in projects that are both content connected and template based.

Rules:   

In short, the template has precedence when both content connector and the active project template defines a filter configuration for a file. The following are the rules that define this:

1. If there is a filter defined in the template, that should be used even if there is a filter defined in the CC filter page. (ie. Template filter should override the CC filter)
2. If there is no filter defined in the template, but there is a filter in CC, the CC filter should be used.
3. If there is no filter in either the template nor the CC, the file should use the default memoQ filter, or if there is no such filter (eg. *.rc) then file should be skipped.
4. If the project is not template based, the filter in CC should be used, if there is no filter, the default filter should be used, if there is no default, file should be skipped.
Rss Comments (Please do not post support requests here.)
  • There are no comments for this article.
Info Add Comment
Nickname: Your Email: Subject: Comment:
Enter the code below:
Quick Jump Menu
Info Missing an article? Let us know!