Add filter to Localization Framework

[isaac wen]

I would like to leverage the Localization Framework to manage and translate Knowledge Base articles.

The issue is that we have many Knowledge Bases, which each need to manage their translations independently.

From what I can tell, LF Settings are on a per artifact basis, but there is no way to filter in the artifact (ie. to only allow articles from a specific Knowledge Base).

Is there any way to accomplish what I am looking for? Any ideas would be appreciated!

[Alex Coope - SN]

@isaac wen,

You are correct in that the "settings" in the Localization Framework aren't down to the KB level, however it comes down to how you create the requests in given languages. In that if you are creating them manually, you would only need to request what is relevant at that time, if you are creating them in an automated way, it's certainly possible to generate the tasks via a Business Rule where you could do some sort of lookup to determine which languages to make tasks for if so desired.

I would however suggest you raise it as an "IDEA" so it can be considered for potential future versions,

Many thanks,
Kind regards 

[isaac wen]

Thanks for the reply Alex, 

Just a follow up on that note for the manual process:

We would have to do something like this right? 

1. Select articles to be translated and click translate article

2. Create a new Project

3. Add those Items to the Project

4. Start the project

5. Go to the individual tasks to translate? 

It seems like a lot of steps for something that will be an ongoing process. 

I also experimented with creating projects, and tasks with business rules, but there seems to be a lot going on in the background, especially involving tasks (ie. the settings field) which make it hard to automate. 

Do you have any resources or documentation that you think could help? 

[Alex Coope - SN]

@isaac wen,

So the high level thing to think about is that there will always be a need for 1 task per source item per language, as that's what holds the relationship of source text to target language translations (hence the volume of tasks),

Many thanks,
Kind regards

[isaac wen]

Hi @Alex Coope - SN, 

I appreciate your high level explanation, but could you provide some more details about how you would go about implementing it? 

In my experience it's not as simple as just "creating a task" since there is some hidden metadata that is used, such as settings or artifact config. 

Looking in the OOTB script includes I can see that there are many functions, but all of those require many parameters that aren't easy to use.

Thanks!