Knowledge check
Wizard Mode
10 questions in pool · live exam draws 5
B07
Q1 multiple-choice · concept What is Wizard mode’s primary purpose in CAPP?
Explanation: Wizard mode simplifies the full Capture interface (B06) into a sequential, step-by-step UI optimized for high-volume production lines and junior operators. The wizard designer pre-configures everything; the operator just follows the prompts.
Q2 multiple-choice · roles Who typically creates wizards in CAPP?
Explanation: Wizard design is a workflow-engineering task — Studio Managers design wizards for their team’s daily production, PhotoRobot consultants design custom wizards for advanced customer workflows, and integrators script wizards as part of ERP/PIM integration projects. Operators run wizards; they don’t create or modify them mid-shoot.
Q3 multiple-choice · step-types How many wizard step types does CAPP support?
Explanation: CAPP supports 5 wizard step types : create-item, select-item, capture-folder, import-images, liveview. A production wizard typically chains 3-5 of these to cover one item’s full workflow.
Q4 multiple-select · validation · weight 2 Which of the following are valid reasons CAPP blocks a wizard from launching? (Select all that apply.)
Explanation: CAPP enforces 3 launch validation requirements : presets must be assigned, workspace must be complete, and folder names referenced in steps must match folders that exist or will be created. Wizard names, step counts, and design assets are flexible and do not block launch.
Q5 multiple-choice · step-types-application A studio imports 500 items via CSV at the start of each day, then operators photograph them one by one. Which step type should appear FIRST in the wizard?
Explanation: When items are pre-imported (via CSV), operators don’t need to create new items — they need to select from the pre-existing list. The select-item step shows the existing item list and lets the operator pick one. Use create-item only when operators need to define items on the fly (e.g., scanning unknown barcodes).
Q6 true-false · scripting Operators can modify a production wizard’s steps mid-shoot to handle edge cases.
Explanation: Wizard modification is a designer task (Studio Manager / consultant), done in CAPP Settings → Wizards. Operators run wizards but cannot edit them. If an operator hits a real edge case that the wizard doesn’t cover, the fallback is to switch that one item to Full Capture mode — not to modify the wizard live.
Q7 scenario · when-to-use · weight 2 A studio’s senior photographer shoots one-off luxury campaign products with unique angles per item. Each shoot requires creative decisions about composition and lighting.
Explanation: Wizard mode is optimized for repetitive workflows with consistent execution. Creative / one-off shoots need the full Capture interface so the operator can make per-item decisions about angles, lights, and folders. Senior photographers + creative work = Full Capture. Junior operators + production line = Wizard.
Q8 multiple-choice · design-patterns A wizard designer wants the operator to visually confirm camera framing before triggering a hero-shot capture. Which step type should be inserted before the capture-folder step?
Explanation: The liveview step shows the operator a live camera feed — no capture happens, just visual confirmation. Use it before high-stakes captures (hero images, regulated photography) so the operator can verify framing / focus before committing to the actual capture sequence.
Q9 multiple-choice · json-format In a capture-folder step’s JSON config, which field specifies which folder the captured images will be saved into?
Explanation: The dirName field on a capture-folder step specifies the destination folder name (e.g., "Spin", "Stills", "Stills-Top"). The name must match a folder that exists or will be created in the item. Other relevant fields: title (header shown to operator), note (instruction text), optional (skip-able flag).
Q10 multiple-choice · cross-product Which PhotoRobot product is wizard-driven natively, where every workflow uses the same wizard step infrastructure as CAPP?
Explanation: PhotoRobot Touch is fundamentally wizard-driven — every Touch workflow uses the same step types as CAPP wizards (create-item, capture-folder, etc.), just rendered for iOS. Studios that adopt Touch are running wizards even if they never open CAPP’s wizard config UI. Module B18 covers Touch in detail.
Ready to commit? You can review and change your answers before submitting. Once submitted, this attempt is final and we'll show you your score, correct answers, and explanations.
Submit final answers