---
id: TST-PFM-INT-598
title: cross workflow views queries
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - >-
    modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js
implements:
  - ATS-PFM-INT-020-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#security_invoker
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#reads
      the probe host in both views
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#skips
      a host with no view, and one whose view lacks a column, naming each
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#answers
      the tenant its own runs alone, newest first
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#maps
      a run, every column of the union, its instants ISO 8601 UTC
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#pages
      the runs two at a time
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#answers
      the failed runs as needing attention
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#narrows
      the runs to an instance, to a type and host, and to a window
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#answers
      another tenant its own run alone
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#answers
      the tenant its own timers, soonest due first and the unscheduled last
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#maps
      a timer, every column of the union, its instants ISO 8601 UTC
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#pages
      the timers, the cursor naming the soonest
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#answers
      the blocked timers as needing attention
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#narrows
      the timers to a status and a due window
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# cross workflow views queries

## Verification Boundary

This database and service suite exercises cross workflow views queries. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.