Connecting to systems of record
The Payment Exception Resolution application comes with several Data Pages rules that are in simulation mode. Copy each data page rule into your implementation layer (ruleset) and update the data source information for each appropriate system of record.
Pega Foundation for Financial Services
The following table lists the data page rules and its purpose in the Payment Exception Recovery application.
Data Page rules
| Data Page name | Lookup class | Purpose |
| D_GetAccountDetails | PFSA-PER-Data-Account | Retrieve account details |
| D_GetAccountsList | PFSA-PER-Data-Account | Account search results |
| D_FetchDepositAcctLinkedToCard | PegaFS-Data-AcctCardXref | Retrieve account linked to a card |
| D_GetTransactionList | PFSA-PER-Data-Transaction | Transaction search results |
| D_Transaction | PFSA-PER-Data-Transaction | Retrieve transaction details |
| D_GetCreditedTransactions | PFSA-PER-Data-Transaction | Retrieve credited transactions for an account |
| D_GetDuplicateTransList | PFSA-PER-Data-Transaction | Retrieve duplicate deposit transactions |
| D_GetDepositTranSummary | PegaFS-Data-Transaction-Deposit | Retrieve deposit transactions |
| D_CCTranSummary | PegaFS-Data-Transaction-Card | Credit card transaction search |
| D_Payor | PFSA-PER-Data-Party-Payor | Retrieve payor (customer) details |
| D_PayorBank | PFSA-PER-Data-Party-PayorBank | Retrieve payor’s bank details |
- In the header of Dev Studio, search and select the data page rule. For example, D_GetAccountDetails.
- Save the data page rule into your implementation layer ruleset.
- Configure the data source using the source deemed appropriate for the SOR.
- Perform steps 1-3 for the other data page rules listed in the table above.
Previous topic Customizing correspondence templates Next topic Customizing application attributes