Create a Draft QCDR Rule from Discovery

After selecting frontend output in Discovery, you can hand the selection to the Administrator Rule editor. QCDR opens a prefilled Draft; it does not silently save, enable, or publish a transformation.

The Discovery authorization must still be valid, and the administrator must also have permission to manage QCDR Rules.

Prepare the Selection

  1. Select the exact visible element or phrase in the private Discovery session.
  2. Review and, if necessary, narrow the QCDR find value.
  3. Optionally enter Change it to. You can also leave the replacement blank and finish it in the Rule editor.
  4. Review the Source evidence and Target Fingerprint so you understand what scope QCDR can prefill.
  5. Choose the action to create/open the Draft Rule.

QCDR refuses the handoff if there is no find value or if the short-lived Discovery authorization is missing/expired.

What QCDR Prefills

The server creates an unsaved Rule-editor object with conservative defaults:

  • State: Draft.
  • Operation: Replace.
  • Find: exact rendered-output matching using the selected text/HTML/URL type.
  • Replacement: direct value from the Discovery proposal, if supplied.
  • Occurrences: All, with no additional per-Rule replacement cap.
  • Audience: Everyone.
  • Request scope: Frontend.
  • Page scope: the selected page URL when QCDR can safely normalize it.
  • Extension scope: the observed site module or component when the fingerprint identifies an installed current target; otherwise All.
  • Internal notes: Discovery page/context and fingerprint summary.
  • Discovery fingerprint: saved for advisory Rule Health drift checks after you save the Rule.

Discovery Parameters Are Removed from Page Scope

When QCDR builds the page URL pattern, it removes its private Discovery/Preview query parameters. The resulting Rule is scoped to the real frontend route rather than to a one-time diagnostic URL.

Review Before You Save

The handoff is intentionally a starting point. Check the operation, content/output context, replacement type, page/extension scope, audience, schedule, occurrence settings, protected-area behavior, and Stop Processing before saving. A selected HTML or URL fragment can require different replacement/output settings than simple text.

Saving Is the Point of Creation

Discovery opens the Rule editor in a new Administrator tab through an authorized POST. The Rule does not exist in the QCDR database until you save it. Keep it in Draft while you review the generated scope, then use Preview/Rule Health before changing the state to Enabled.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.