The importance of intranet localization

I would like to discuss the importance of intranet localization from 3 different perspectives:

• Consumption according to Language
• Changing the framework of an intranet process
• Changing the purpose of a bespoke intranet application

Consumption according to language

The most common meaning behind content localization is to allow companies to present menu systems, commands and content in multiple languages – and to have the intranet system automatically set those according to the users preferences.

Content Localization

Changing the framework of an intranet process

The Claromentis Process Manager is fully localized at the project level. So an e-form process on the intranet that deals with time cards can say “Enter a New Time Card” and not ‘New Ticket”. This is separate to language localization – we are using localization at the application level to configure a process that makes sense to the user.

Localized e-form

Changing the purpose of a bespoke intranet application

In the same way as we localize a process through configuration at the project level, we can use the abstracted visual interface to change an entire application. For example we recently created a version of Policy Manager – which normally manages policies and procedures – to instead manage examination questions for the Royal College of Surgeons.

Indeed in this example we also used the fact that Policy Manager allows custom images to categorize categories of policies – or in this case categories of examination questions – to great effect.

Question Categories

Summary

Although the expense of producing a completely localized intranet codebase from the ground up is far from trivial, localization at all these levels is a fantastic way to focus content and processes to the optimal benefit of the users – without writing a line of additional code at the business logic level…

Intranet-Extranet, Prod-Process, Services localization