Skip to main content
When a product screen changes, first decide whether an HTML edit can represent the current experience accurately. If the layout or state has changed substantially, recapture is often a better starting point. Use safe sample data and check the instructions, targets, and transitions around the replacement.

Recapture an HTML step

  1. Open the demo in the editor and select the HTML step that needs an update. Open its capture editor and choose Recapture.
  2. Check the Recapture page URL. Use a page on the same site and open that exact URL in the active ArcDemo HTML recorder before requesting the capture.
  3. Arrange the source page in the state the viewer should see. Select Request recapture, complete the capture in the extension, and return to the editor to review the new artifact.
  4. Inspect the replacement and the editor’s target information. If a target is missing or ambiguous, use Reselect target and choose the intended element; do not assume that a similar-looking control is the correct one.
  5. Save or discard the capture editor’s pending draft commands as appropriate. Preview the step and the preceding and following steps. Check guides, triggers, and sandbox links that depend on the captured page.
Keep the editor and recorder available while the operation completes. If a request remains pending, check its displayed status before starting another. The editor can cancel a pending request, but a save that already completed may still be reconciled; verify the result rather than assuming it was undone.

Review a batch of replacements

Where Durable recapture is enabled, the recapture panel can prepare one capture, a selection, a collection, or captures in use. Review the scope preview: it shows the captures and linked demos or steps that may be affected. Start the recapture and follow the recorder’s prompts for each source page. Each replacement becomes a reviewable version. Use Compare to inspect a replacement or Reject to keep the active version. The panel offers two different commit choices:
  • Commit versions only saves the reviewed versions without applying them to the linked steps.
  • Commit and apply confirmed links also applies them to the linked steps in the reviewed usage snapshot. If usage changed since the review, follow the prompt to review and confirm again.
Pause, resume, retry failed items, or cancel remaining work using the controls shown for the job. Availability and supported capture types can vary by workspace. If batch recapture is unavailable, the HTML editor can still offer the one-step request described above.

Verify and publish

Check the updated draft from the viewer’s entry point. For HTML, verify the text, imagery, interaction targets, and any edits or variables. For a sandbox, test the connected states and return paths. Review any other linked demos affected by an applied version. A saved replacement does not by itself update the shared demo. Publish the reviewed draft and test the actual shared link or embed. See Keep a demo current for the full maintenance workflow.