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

To determine the recommended meal plan based on the number of people in the household and dietary restrictions, you can use a decision table and a decision shape. A decision table is a rule that derives values that have one of a few possible outcomes, where each outcome can result from a test of a condition that includes multiple variables. A decision shape is a shape that you can add to a flow to branch the flow based on the result of a decision rule, such as a decision table. Reference: https://academy.pega.com/topic/decision-tables/v1

Optional actions are actions that users can perform at any time during a stage in the case workflow. They are not required to advance the case to the next stage or step. Optional actions can be used to allow customers to update any of the user profile pages individually during the order placement stage. Reference: https://community.pega.com/knowledgebase/articles/case-management/88/configuring-optional-actions