Which two approaches can you take to facilitating Mashup interface development in App Studio? (Choose Two)
Setting pxThread.isWebMashup:
In the pyDefault Data Transform for a case, setting pxThread.isWebMashup to True ensures that App Studio users see the same views displayed by a Mashup interface.
Associated Privilege Visibility Conditions:
Using associated privilege visibility conditions allows App Studio users to view and configure sections only shown to external personas at design time.
Reference:
Pega documentation on Mashup interface development in App Studio outlines these practices to ensure seamless integration and development.
Therefore, the correct answers are:
B . In the pyDefault Data Transform for a case, set pxThread.isWebMashup to True by using an Application Setting. App Studio users then see the same views that are displayed by a Mashup interface when it is configured to use the Create a case option.
C . Use associated privilege visibility conditions. At design time, an App Studio user is able to view and configure sections that are only shown to external personas.
A Citizen Developer working on a Claims case type wants to validate the BenefitType property value. This property is located on a Clipboard page named ClaimBenefit of the MyCo-Data-ClaimBenefit class, which is inherited from Data-.
As a Lead System Architect, what do you recommend to make this validation available to the Citizen Developer?
For validating the BenefitType property value, the recommended approach is:
When Rule and Relevant Record (D):
A System Architect creates a When rule in Dev Studio, referencing the ClaimBenefit Clipboard page on the Pages & Classes tab.
The rule is marked as a relevant record, making it available for Citizen Developers to use. This approach ensures that the validation logic is centrally defined and easily accessible for reuse.
Pega Dev Studio Documentation on Creating When Rules
Pega Documentation on Marking Rules as Relevant Records
A decisioning architect wants to use the customer properties income and age in a Filter component. Which decision component is required to enable access to these properties?
To use customer properties like income and age in a Filter component:
Direct Access:
Customer properties such as income and age are directly available for use in decisioning components.
There's no need for additional components to enable access.
Using the Filter Component:
Simply drag and drop the Filter component into the decision strategy.
Use the customer properties directly in the filter logic (e.g., Customer.Income > 50000).
This is because Pega Customer Decision Hub typically provides direct access to commonly used customer properties.
When implementing a Next-Best-Action, the customer Lifetime value Threshold is used to __________ for an offer
Next-Best-Action Configuration:
In Pega, configure the Next-Best-Action strategy to include customer lifetime value as a factor.
Set Thresholds:
Define thresholds for customer lifetime value to determine what constitutes a high-value proposition.
Prioritization Logic:
Implement logic within the strategy to prioritize actions or offers that align with high customer lifetime value.
Reference: Pega documentation on Next-Best-Action and customer lifetime value considerations.
Pega Customer Decision Hub enables organizations to make Next-Best decisions. To which type of a decision is Next-Best-Action applied?
Next-Best-Action (NBA): This concept in Pega Customer Decision Hub involves recommending the best possible action for each customer interaction, which often includes decisions in customer service, marketing, sales, and risk management.
Loan Decision: NBA is frequently applied in financial services to determine creditworthiness and loan approval, leveraging predictive analytics and customer data to make informed decisions.
Reference: Pega Customer Decision Hub documentation outlines the application of NBA in making critical customer decisions, such as loan approvals, to enhance customer experience and operational efficiency (Pega Customer Decision Hub Documentation, Decision Strategies).
