Research progress
Execution engines & functionality · recorded 2026-10-20
i
Unique research cases across these execution areas. Bring the metadata and data you choose to build or export; VirtualOrg focuses on running it.
- Recorded matches
- 496 / 580
- Additional local passes
- 2
- Work remaining
- 82
- Fully supported
- 1
i
Language execution, control flow and runtime services. Recorded matches cover bounded contracts and profiles; partial support and documented gaps can remain after every selected comparison passes.
- Recorded matches
- 106 / 106
- Additional local passes
- 0
- Cases awaiting a pass
- 0
- Fully supported
- 0
Each match covers a selected contract and profile. Apex cases can retain partial support and documented limits even when all selected recorded comparisons pass. Inspect the contracts and evidence.
i
Query execution, filtering, relationships and aggregation across the recorded query contracts.
- Recorded matches
- 50 / 53
- Additional local passes
- 0
- Work remaining
- 3
- Fully supported
- 0
i
Expression evaluation, functions and typed results. Business validation rules have their own view.
- Recorded matches
- 96 / 97
- Additional local passes
- 0
- Work remaining
- 1
- Fully supported
- 0
i
Native authoring, formula checks, save enforcement, error placement and Metadata API lifecycle. Recorded runtime matches do not establish complete rule authoring or Setup behavior.
- Recorded matches
- 4 / 18
- Additional local passes
- 0
- Work remaining
- 14
- Fully supported
- 0
Validation workflow coverage
These facets reuse the same capability records. Facets can overlap; the area total counts every record once. Required-field and type checks remain separate from business rules.
| Workflow | Recorded matches | Additional local passes | Remaining | Fully supported |
|---|---|---|---|---|
| Discover, author and manage rules | 0 / 9 | 0 | 9 | 0 |
| Formula editing and diagnostics | 0 / 4 | 0 | 4 | 0 |
| Save-time business enforcement | 2 / 2 | 0 | 0 | 0 |
| Error placement and presentation | 1 / 2 | 0 | 1 | 0 |
| Metadata API lifecycle | 1 / 1 | 0 | 0 | 0 |
| Required-field and type validation (separate) | 1 / 1 | 0 | 0 | 0 |
i
Automation execution, interviews and actions. Local passes still need recorded reference comparisons.
- Recorded matches
- 46 / 62
- Additional local passes
- 0
- Work remaining
- 16
- Fully supported
- 0
i
Unique email-specific catalog contracts mapped from the atomic workflow inventory. A recorded template metadata match does not establish rendered mail; local capture and provider acceptance do not establish delivery. Related producer and intake contracts are cross-linked separately.
- Recorded matches
- 2 / 14
- Additional local passes
- 1
- Work remaining
- 11
- Fully supported
- 0
Explore email workflows, authoring, evidence and remaining gaps. Each workflow keeps native authoring, runtime execution and reference comparison separate.
i
Metadata/API comparisons and native authoring use separate denominators. The lifecycle inventory covers design, rendering, activation and persistence. Native local acceptance never establishes a reference match; full visual/CSS parity remains excluded.
- Recorded matches
- 2 / 7
- Additional local passes
- 0
- Work remaining
- 5
- Fully supported
- 0
Native authoring and execution: 39 / 51 contracts with local acceptance (76.5%). 12 remain unimplemented or unverified. This separate measure includes dated native/browser receipts; it contributes no reference matches.
- Authoring and sections: 10/19 native local passes; Native measure.
- Fields and components: 12/12 native local passes; Native measure.
- Rendering and visibility: 7/7 native local passes; Native measure.
- Activation and assignment: 3/5 native local passes; 0/1 recorded metadata/API matches.
- Metadata and APIs: 2/2 native local passes; 2/6 recorded metadata/API matches.
- Persistence and recovery: 5/6 native local passes; Native measure.
i
Includes REST records/query/search/composite, Bulk 1.0 and 2.0, GraphQL, Tooling and UI API, including unfinished layout resources. Matches cover recorded subsets; every partial row has unfinished facets. Metadata, CLI and SOAP are cross-referenced separately in the API workflow inventory; Streaming, Pub/Sub, Connect, Analytics and product APIs keep their own families.
- Recorded matches
- 73 / 84
- Additional local passes
- 1
- Rows without a match
- 10
- Fully supported
- 0
Matched subsets still have unfinished workflows. UI API is included here; Metadata, CLI and SOAP have separate cross-references. Inspect protocol workflows, missing variants and next acceptance cases →
i
Permissions, muting, profiles, users and record sharing. Configuration, enforcement and provider interoperability have separate contracts. The finite muting cell is the only individually admitted full support claim in this snapshot.
- Recorded matches
- 67 / 84
- Additional local passes
- 1
- Work remaining
- 16
- Fully supported
- 1
Access administration subareas
- Permission sets & groups: 20/25 recorded matches; 1 additional local passes; 4 remaining; 0 fully supported.
- Muting: 11/12 recorded matches; 0 additional local passes; 1 remaining; 1 fully supported.
- Profiles & users: 13/23 recorded matches; 0 additional local passes; 10 remaining; 0 fully supported.
- Record sharing: 23/24 recorded matches; 0 additional local passes; 1 remaining; 0 fully supported.
These counts use the dated catalog cases. Saving settings and passing a bounded comparison do not establish complete effective access. Inspect exact contracts and limitations.
i
Transaction behavior, event delivery and subscription execution under the recorded profiles.
- Recorded matches
- 38 / 50
- Additional local passes
- 0
- Work remaining
- 12
- Fully supported
- 0
i
SOSL search execution and bounded result contracts.
- Recorded matches
- 9 / 9
- Additional local passes
- 0
- Work remaining
- 0
- Fully supported
- 0
i
Cache execution, partition access and expiry under the recorded contracts.
- Recorded matches
- 5 / 7
- Additional local passes
- 0
- Work remaining
- 2
- Fully supported
- 0
How to read this research
Percentages describe selected research cases, not a percentage of a language or platform. A recorded match is a profile-bound comparison; additional local passes have no admitted reference match in this snapshot. Full support requires an individually admitted contract without remaining limitations. Overall counts overlapping cases once and focuses on execution, excluding object and field inventories. Layouts & pages retain a separate native lifecycle inventory. Its native acceptance percentage counts original contracts with selected local evidence and never enters the reference-match denominator.
This separately dated snapshot preserves its recorded source and results; it is not a fresh run of the current source. Selected-area data · Selected capability scope, tests and limits.
Research counts describe a dated inventory of execution contracts and recorded profiles. Read as Markdown.