Current QCST Features That Are Not Customer-Facing Workflows

This article clarifies that SLA policy UI, automation-rule UI, API-token management, webhook management/delivery UI, saved-view builders, and conditional-form builders are not current normal customer screens despite retained code/tables.

Where this fits in QC Support Ticket

Official documentation follows the customer-facing interface that actually exists in QCST 1.0.42. The source can retain schema, migrations, capability names or service classes for compatibility/future work without those internals becoming supported administrator workflows.

Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.

Do not document these as current customer screens

  • SLA policy management UI
  • Automation-rule builder UI
  • API-token management UI
  • Webhook management/delivery UI
  • Saved-view builder UI
  • Conditional-form builder UI

The current source may retain tables, capability names, migrations or service code for architectural continuity/future work. Official customer documentation follows the actual 1.0.42 screens and supported workflows, not every database table or internal class.

Current-version note

This documentation is based on QC Support Ticket 1.0.42, the package currently deployed on the QuantaCade production site. The behavior described for Current QCST Features That Are Not Customer-Facing Workflows should be checked against the current screen labels before applying instructions to an older QCST release.

Why this boundary matters

Documenting an internal table or service as if it were a supported screen sends customers looking for controls that do not exist and can encourage unsafe database-level workarounds. When a future release exposes one of these capabilities through a normal supported UI, that release should be re-audited and the documentation updated from the new source; until then, keep these items out of customer procedures.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.