https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/_Pegasystems_PEGACPSA88V1/page_27_img_2.jpg

To localize correspondence into a language that is unavailable in the Pega language pack, you can

create the Translation rule manually and include the rule in the application ruleset. A Translation rule

is a rule that defines how to translate text from one language to another. You can create a Translation

rule manually by using the Create menu in Dev Studio and selecting Rule > Integration-Resources >

Translation. You can then specify the source and target languages, the text to be translated, and the

translated text. You can also use a decision table or a connector to provide the translated text. You

must include the Translation rule in the application ruleset so that it can be used by the application.

Reference: https://community.pega.com/knowledgebase/articles/integration/86/translation-rules

These two statements are true about insights. Insights are rules that Pega Platform uses to transform

data queries into tables or visualizations that you can then share between users and embed in

landing pages of your applications. Insights can include multiple data items that you can filter, sort,

and group according to your business requirements. You can search for and select the fields that you

want to include in an insight from the data objects that are available in your application. Reference:

https://docs-previous.pega.com/reporting/87/visualizing-data-insights

These two requirements ensure that valid data is used in a case. The data fits the business logic

means that the data values are consistent with the rules and conditions that define the case behavior

and outcome. The data is the correct field type means that the data values match the expected

format and structure of the field properties, such as text, number, date, or email. Reference:

https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/datatypes

https://community.pega.com/knowledgebase/articles/data-management-andintegration/86/field-values

You should consider using a field value when the list of allowed values is mostly static or shared

across all case types. A field value is a rule that defines a single value for a field that is used in

multiple places in an application. Field values are useful when the list of values does not change

frequently

or

when

the

same

values

are

used

in

different

case

types.

Reference:

https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/fieldvalues