Pega Process Fabric Hub

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

Platform 24.2 Language Pack        

1) Import Pega Language Pack .jar (01-PegaPlatform\Rules\*language_LanguagePack_Prpc.jar) via  Dev Studio-> Configure -> Application -> Distribution -> Import.
Note::Ignore Rule-UI-Localization related errors while importing platform language pack on versions less than 24.2 These errors do not have impact on the application functionality.

Pega Process Fabric Hub Language Pack

1) Install the Pega Process Fabric Hub Language Pack from (02-PegaProcessFabricHub\Rules\PegaProcessFabricHub_*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 re-start 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 Process Fabric Hub (PPFH) x.x.x
1) Login into the system using your operator and the password that you specified when you installed this server. 
2) In the Operator ID record, Set the Default Locale under the Profile tab. 
3) Logoff & Login same operator 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

a) Breadcrumbs are not localized.
b) Sample data is not localized.
c) Dev Studio is not completely localized. 
d) Auto-completes are not in scope of localization.
e) Sample Products are not localized.
f) Case Narrative Email attachment name not localized.
g) Sample work baskets not in scope of localization.
h) Dashboards and Explore data section is not localized.