A hospital edits customer-service copilot customizations directly on the live case form. A recent edit changed the summary families hear about, and no sandbox copy exists. How should those customizations ship?
Select an answer to reveal the explanation.
Short Explanation
You do not repaint the ward door while families are reading the sign. You ship the customer-service copilot customizations as a solution from a sandbox. Editing the live case form makes production the only copy.
Full Explanation
Customer-experience copilot customizations belong in the application lifecycle, not in an edit on the live case form. The hospital should build the change in a sandbox and ship it as a solution, so test can see the summary before families do and production is updated by that solution. Keeping the edits on the live case form each time a request arrives repeats the incident and leaves no sandbox copy to compare. Pasting the customization into a personal view that the release does not carry hides the change from the solution, so the next environment will not receive it. Rebuilding the customizations as a separate agent that hides the case form abandons the in-app copilot and the form the customization was meant to ride on. Exam caveat: a solution from a sandbox is the shipping path. Pasting the same text into a personal view that the release does not carry is not that path. Operational check: make the next summary change in the sandbox, export it in the solution, and confirm the live case form changes only when that solution is imported.