Hidden, Deferred, Legacy, and Development-Only Features
Hidden, Deferred, Legacy, and Development-Only Features
Overview
This guide will help you recognize source-visible functionality that must not be presented as an active production workflow without further evidence.
Unsupported or ambiguous source artifacts are not mistakenly taught as production features.
Static reference for the available development baseline; product-owner/system classification remains required.
Who can do this
You need access to None to read; testing hidden/deferred workflows requires an isolated database and explicit authority.
Before you start
Distinguish compiled source presence, active hub launch, role/feature visibility, reachable system behavior, and product-supported production status.
Where to find it
Help Center → Troubleshooting & Reference → this reference; consult the source coverage ledger internally.
Hidden, Deferred, Legacy, and Development-Only Features
Step 1: Treat a feature as active only when its launch path,
Treat a feature as active only when its launch path, permission, subscription/setting gate, and system operation are verified.
Step 2: Treat commented-out actions as unavailable
Step 3: Treat unreachable forms as hidden/deferred
Step 4: Treat legacy duplicate implementations as unresolved until the runtime selector
Treat legacy duplicate implementations as unresolved until the system selector is known.
Step 5: Label development-only behavior explicitly
Step 6: Obtain product-owner confirmation before customer-facing availability claims
Known examples requiring caution include Purchase Apply Debit, requisitions, four POS implementations, legacy BackOffice/Quick Launch surfaces, auto item barcode, temporary-sale cheque paths, automated temporary-sale conversion, and unfinished WLM conversion surfaces.
Check your work
Every listed feature has a coverage-ledger status and evidence before publication.
If something goes wrong
- Source class existence is not production support.
- A hidden control may also reflect permission or subscription rather than deprecation.
Related guides
- Version, Build, Database Revision, and Release Notes Reference
- Guide Evidence, Verification, and Known Limitations
- Roles, Permissions, Features, and Limits Reference