The power company EnergyCo uses a PRPC-based Incident Management application with a single work type defined in the framework (class: EnergyCo-FW-IncMgt-Work-Incident). EnergyCo has four divisions (DivA - DivD). DivD has a new requirement: Solar Panel related incidents are stored in a separate table from other incidents. There is no Solar Panel specific class. In order to meet this new requirement, is it necessary to add a Solar Panel class? (Choose One)

• A. No; a add a Solar Panel specific database table instance to the EnergyCo-DivD-IncMgt-Work-Incident class
• B. Yes; it should only be added to the implementation layer (e.g. "EnergyCo-DivD-IncMgt-Work-Incident-SolarPanel")
• C. No; it is possible to circumstance based on an IncidentType property
• D. Yes; it should only be added to the framework layer for greater reusability (e.g. EnergyCo-FW-IncMgt-Work-Incident-SolarPanel)

All user forms in PRPC display a Submit button for submitting the user action. There is a requirement to change the button label to Confirm on all screens instead of Submit, which of the following is the best approach to handle this requirement? (Choose One)

• A. Change the label of the button in flow actions
• B. Modify the label of the button in the Action section used in the perform harness
• C. Add a pxButton control to the flow action rule
• D. Change the label of the button in the button area of the perform harness

In a Credit card dispute application PRPC connects to an external service to receive the transactions made by the account holder. When the CSR (Customer Service Representative) is working on the dispute they should see only the last twenty transactions made by the account holder. If the transaction that the account holder wants to dispute does not appear in the list then the CSR should perform a search by entering the date of transaction or the transaction amount or the merchant name. The transaction list should display the 20 transactions that satisfies the criteria. In any circumstance the CSR should not see more than 20 transactions in the screen and cannot paginate through results. The external service returns transactions ordered by date of transaction with the recent ones appearing first.
Given the above requirements, which of these approaches is most appropriate and would satisfy both these requirements? (Choose One)

• A. Execute the activity that makes a connector call to get the list of transactions from an external service before the flow action is rendered so that all transactions are available on the clipboard. When a search parameter (transaction date, amount and merchant name) is specified, use a data transform to copy the appropriate subset of the transaction to a new page
• B. Build a thread level declare page which uses an activity as its source. The activity will invoke the connector activity and then copy only the first 20 pages to the declare page. Display the first 20 results of the declare page by using the pagination setting "First X" results
• C. Execute the activity that makes a connector call to get the list of transactions from an external service before the flow action is rendered. Write a data transform to copy the connector result to a declare page. Create a repeating grid layout using the declare page as its source. Display the first 20 results of the declare page by using the pagination setting First X results
• D. Build a thread level declare page that uses an activity to invoke the connector activity and then copy only the first 20 pages to the pagelist property defined in the declare page; this property is used as a source for the repeating grid. A when rule would be used to control when the results are fresh based on the values of the search parameters (transaction date, amount and merchant name)

Which of the following statements are most accurate about the Split-For-Each and Split-Join shapes? (Choose Two)

• A. Both shapes create separate Threads for sub-processes they create
• B. Split-For-Each can only be used when iterating over a list of work objects
• C. Split-Join allows you to execute different sub-flows whereas Split-For-Each calls the same process on different pages
• D. Both shapes allow you to continue processing when ANY or ALL of the sub processes complete
• E. Split-For-Each allows you to execute different sub-flows whereas Split-Join calls the same process on different pages