Legacy and Retired QCDR Rule Options: What Remains Stored but Cannot Be Newly Configured

QCDR 1.1.05 deliberately preserves some older Rule values so an upgraded database is not destructively rewritten, while preventing administrators from newly selecting retired workflows. Preserved legacy data is compatibility state—not evidence that the old feature remains supported.

Retired Options You May Still Encounter

  • Count Only Rule action.
  • Source-file search/editing mode.
  • JSON, XML, and INI Find content types.
  • Retired replacement/output types such as Structured data / JSON, XML, INI / language value, and HTML attribute value.
  • Legacy unsupported extension target identifiers such as plugin or administrator-module isolation.

What “Preserved” Means

When QCDR loads an existing older Rule, the editor can preserve certain retired stored values so simply opening and saving the record does not silently convert it. The editor labels these as legacy/no-longer-available where applicable. New Rules cannot select those retired values, and forged form submissions are rejected or normalized by server-side validation.

Source-File Rules Are Not Current Runtime Rules

Current QCDR is rendered-output only. A pre-existing source-file draft can remain stored until you delete or rebuild it, but QCDR will not accept source-file mode for a new Rule. Do not document or rely on QCDR as a PHP/template-file modification system.

Count Only Is Retained for Compatibility

An old Count Only Rule can remain stored. The current editor does not offer Count Only for new configuration. If you need to understand whether a current Rule matches, use Preview/Rule Health where your plan and ACL allow it rather than creating new Count Only Rules.

Migrate Instead of Expanding a Legacy Rule

  1. Identify what the older Rule was intended to accomplish.
  2. Create a new Draft using current rendered-output Find types and current actions.
  3. Apply current page/extension/audience targeting as needed.
  4. Test the new Rule against rendered frontend output.
  5. Only after verification, retire/delete the obsolete definition according to your change-control needs.

Preservation protects upgrades; it is not a promise that a retired workflow will receive new features or remain a recommended production path.

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.