Knowledge

A Language Pack is a collection of language-specific rulesets provided by Pega to support the localization of an Application. A Language Pack provides field value rules that localize the buttons, prompts, and labels for the application portals.

A language pack zip file contains one or more language packs needed to localize a specific version of an application or layer.

Pega provides these core language packs at no cost. The table below displays core language pack availability for each app version.

• Click Download to get and import a Language Pack to your environment.
• If a Language Pack you need isn't listed or shows N/A, use the Pega Platform's Localization Wizard to create your own LP.
• For Language Packs marked as REQ, contact your Account Team to create a request. "Please note that a 'request' doesn't guarantee automatic approval; it's subject to internal review and approval processes."

Available Language Packs

Pega Knowledge Language Pack

NOTE: This Language Pack is a cumulative of 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 8.23, 24.1 and 24.2 versions. It will work on all 8.x.x, 24.x, 25.x versions.

Install Instructions
Log in to the Pega Platform (https://<hostname>:<port>/prweb) by entering administrator@pega.com and the password that you specified when you installed this server.

Platform Language Pack
1)Import Pega Language Pack .jar (01-PegaPlatform\Rules\*language_LanguagePack_Prpc.jar) via  Dev Studio -> Configure -> Application -> Distribution -> Import.

Pega Knowledge Language Pack
1) Install Pega Knowledge Language Pack .jar from (02-PegaKnowledge\Rules\PegaKnowledge_*language_LP.jar) via  Dev Studio -> Configure -> Application -> Distribution -> Import.
2) Stop application server and remove the contents (folders and files) of Pega temp directory in application server (or) Do a clean restart of the application server by removing the PegaRULES_Extract_Marker file. Clear browser cache and login to application and test the scenario.

Post Install Instructions
**Pega Knowledge
1) Login into the system using an Operator ID.
2) In the Operator ID record, Set the Default Locale under the Profile tab.
3) Logoff & Login to see the locale changes.
NOTE: Every user session (Operator ID) should have the locale set to take the affect of the language texts on the user interface.

KNOWN ISSUES
1.Designer studio is not completely localized
2.Sample data not in scope of localization
3.Breadcrumbs not in scope of localization
4.Auto completes are not in scope of localization
5.Dialogs are not in scope of localization
6.Application settings configuration page is not localized.
7.Case Audit Trail is not Localized.
8.KM component in Interaction Portal search categories is not localized.