A retailer wants store exceptions on a custom page in the model-driven app, and a manager must accept the agent's proposed stock transfer inside that same app. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
Put the exception board on the wall and the approval clip on the same wall. You show store exceptions on a code-first generative page, and you let the manager accept the proposed transfer in that app's agent feed. An email for each transfer sends the decision out of the app.
Full Explanation
The retailer needs two surfaces that stay inside the model-driven app: a custom page for the exceptions, and a place for a person to accept the agent's proposed transfer. A code-first generative page shows the store exceptions as code against Dataverse, and the agent feed in that app is where the manager accepts the transfer. A canvas rebuild of the whole store app, plus an email for each proposed transfer, rewrites the application and moves the acceptance out of the app into a mailbox. A topic that only defines the word exception answers a vocabulary question and neither lists the store exceptions nor records the manager's acceptance. A weekly ranking produced after the transfer has already posted is a look back, so the manager is no longer accepting a proposal. Exam caveat: the page and the feed are different surfaces; the page shows the exceptions, and the feed is the review step, and one does not replace the other. Operational check: raise a test exception, confirm it appears on the generative page, and confirm the proposed transfer shows in the agent feed until a manager accepts it.