Language Support in K2

By default all K2 design time and runtime elements display in English. If there is a need to design solutions that accommodate other languages then it is important plan appropriately. This involves understanding what language support the K2 platform offers as well as which areas must be accommodated within solution design.

K2 Language Packs

The K2 platform offers Language Packs that can be downloaded and installed separately from the base K2 product installation. Full technical details on the language packs can be found here:

In short, the Language Packs affects runtime behavior of the K2 smartforms and K2 View Flow components with some limited change to the browser based design tooling. Specifically it changes the experience from one language to another for embedded/static text values that are not accessible by someone creating a SmartForms based solution. Examples of such components include:

  • Columns of the worklist control
  • SmartForms generated error messages
  • Labels within reporting controls

The language packs will not change every element on a page. For more details on that refer to the Multilingual Forms section below.

As of K2 version 4.6.10, K2 provided language packs for the following languages:

  • French
  • German
  • Simplified Chinese
  • Traditional Chinese
  • Afrikaans
  • NOTE: K2 plans to expand the number of provided language packs over time. Please refer to the K2 software download page in the K2 portal to see what packages are currently provided.

For languages where there are variants, then it is important to understand how the K2 language works with them. An example is German. If the user’s browser is set to German-Austria (de-AT) or German-Switzerland (de-CH) locale and that user browsers to a K2 smartforms page, K2 will attempt to fall back to display the base language, German (de). If the German K2 language pack is installed then it will change the specific embedded text within K2 components to the German equivalents. If no language pack is installed, then it will fall back to the “invariant” resources – which in our case is English (US). Below shows the fall back logic in the context of the German languages.

Whilst Language Packs are distributed and installed separately from the K2 software installation, they are K2 version specific. Thus Language Packs usually ship at, or shortly after, the release of a new K2 version. They can be accessed from the download page on the K2 portal.

The process of creating and building a new Language Pack encompasses translation tasks (where known terms are translated to the targeted language) and build tasks (compilation of software resources). The K2 platform requires these resource files to be built into K2-signed dlls. As such this must be done by the K2 product team; it is not possible for an external party to create a new language pack. If interested, an external party could assist with the term translation to a new language assuming there are resources with appropriate language skills as well as a focused time commitment.

Multilingual Forms

It is important to understand that multilingual forms and Language Packs are not the same thing. As mentioned above, the Language Pack will only affect static text embedded within runtime product controls that are outside of the ability of a SmartForms developer to change. The Language Pack will have no effect on the SmartForms developer accessible properties of a control. For example, it is common for a SmartForms developer to use a label to describe a text box. The display value of that label is manually typed into the Text property at design time. The K2 Language Packs will not affect this value.

If there is a need to create a single form that has a completely different language experience (and not just K2 embedded product text) based upon a selected value or parameter then that is considered a multilingual form and will need to be factored into the solution design by the implementation team. For example, instead of using a standard Label control, a Data Label control could be used and then upon form load the appropriate language can be determined by referring to the Browser Culture property within the SmartForms design time context window. With this a SmartObject call could then be made against a database table that stores translated terms in order to determine what term to display. There is some concept work available on the K2 Community Site that provides some additional ideas around creating a multilingual form experience.

K2 Platform Technical Enablement

It is important that resources tasked with implementing a K2 solution for the first time have the ability to properly learn the platform. We offer a comprehensive training program to help clients achieve maximum value from their investment, which is organized into five technical competencies, allowing for focus on particular aspects of the solutions, or the entire story.

Common Technologies Overview

Common usage scenarios for some of the most utilized technologies seen within the greater K2 community.

Solution Structure and Governance

An overview of best practices for naming conventions, teams with multiple developers, solution deployment and solution versioning.

Data and Integration Planning

Learn more about K2 database practices, SmartObjects and reporting.

Process Design

This section provides more information on process design tools, design best practices, destination rules best practices, workflow design patterns, line rule considerations, and external system call backs to K2 workflows.

K2 and Mobility

The K2 platform provides the ability to interact with K2 applications on mobile devices.  The K2 mobility story falls into two categories: mobile resident applications and mobile friendly forms development.  This section covers these two areas in more detail and highlight content that can provide more specific technical details.

K2’s SmartForms Design

These SmartForms design considerations and performance tuning guidelines will help you get the most out of your forms.