when a customer submits a credit card dispute, the application connects to an external service to retrieve all transactions made by the customer. the external service returns transactions ordered by date of transaction, in a descending, chronological order. when a case worker reviews the dispute, the application displays the 10 most recent transactions. if the case worker does not see the disputed transaction in the list, the case worker can search for additional transactions. the case. the case worker can filter search results on transaction date, the transaction amount or the merchant name the search results display the 10 most recent transactions that satisfy the filter criteri
- the case worker cannot paginate through the results.
how do you configure the data page to satisfy all the requirements in the scenario? - create a node-level data page that uses a connector as its source.
- create a thread-level data page with parameters that uses a connector as it source.
- create a thread-level data page that uses a report definition as its source.
- create a node-level data page with parameters that uses a report definition as its source
Answer(s): B
Explanation:
To configure the data page to satisfy all the requirements in the scenario:
Create a thread-level data page with parameters that uses a connector as its source (Answer B):
A thread-level data page ensures that the data is specific to the current user session and not shared across multiple sessions. Using parameters allows for flexibility in filtering and retrieving the required transactions. The connector source ensures data is fetched from the external service as needed.
Reference:
Pega's data page documentation highlights the use of thread-level data pages for user- specific data and the use of connectors to integrate with external services dynamically.
Reveal Solution Next Question