Source-to-decision product tour

Follow a supported source through review, traceability and impact

This guided, customer-data-free tour mirrors current product routes and uses neutral examples to explain the reviewable workflow.

Review all featuresOpen the detailed documentation

01

Choose a source or capture the project directly

Starting point
Start from a supported file, an assigned read-only source or project records entered directly.
What the view brings together
Document Intake, Partner Data Sources or direct project capture.
What you can decide next
Choose the permitted source path for the project context.
Detailed documentation
Source selectionSupported file, assigned read-only source, or direct capture
Supported fileRead-only source
Supported file
Read-only source
Direct capture
  • PDF or structured data
  • Assigned reference
  • Project record
Illustrative static view

02

Start the supported preview or extraction

Starting point
A selected source is not yet an adopted project artifact.
What the view brings together
The explicit Document Intake preview or extraction action and its bounded result.
What you can decide next
Review the preview before any project artifact is adopted.
Detailed documentation
Source previewPreview created; no project artifact adopted yet
Preview ready
Preview readyFields extracted
Source retainedRows mapped
Review nextCandidates proposed
Illustrative static view

03

Review, edit and adopt selected candidates

Starting point
Proposed artifacts require a deliberate human selection.
What the view brings together
Candidate details, source references and the explicit adoption action.
What you can decide next
Adopt only the reviewed and selected results.
Detailed documentation
Candidate reviewHuman selection required
ReviewEditSelect
  1. Source checked
  2. Candidate edited
  3. Selected result adopted
Illustrative static view

04

Create use-case and test-case suggestions from confirmed context

Starting point
Use cases must be reviewed before they become context for test-case suggestions.
What the view brings together
Change Request → Use Cases → Test Cases as two distinct previews and adoptions.
What you can decide next
Keep the chain from confirmed context to selected use cases and tests reviewable.
Detailed documentation
Reviewed artifact chainUse cases reviewed before test-case generation
Context confirmedUse cases reviewedTests proposed
Preview use cases
Adopt selection
Preview test cases
Illustrative static view

05

Connect traceability, coverage and dependencies

Starting point
A failed or blocked test needs its confirmed context to support a decision.
What the view brings together
The latest execution with confirmed specification and use-case context, linked evidence and defects, and applicable rule-driven readiness signals.
What you can decide next
Inspect confirmed links and the current execution state.
Detailed documentation
Traceability and dependenciesConfirmed links and current execution state
Specification confirmed
Defect linked
Dependency visible
Coverage linkedExecution failedRule signal
Illustrative static view

06

Preview an activity ten days later

Starting point
A schedule question needs a calculated preview, not a change to the live plan.
What the view brings together
Calculated dates and schedule deltas; float and critical path when returned; Project Health deltas only with a comparable baseline.
What you can decide next
Review the calculated result while the scenario remains unapplied.
Detailed documentation
Ten-day scenarioCalculated dates and deltas; scenario not applied
Activity +10 daysDates recalculatedNot applied
  1. Schedule delta
  2. Float when available
  3. Baseline condition
Illustrative static view

07

Review the evidence for the next decision

Starting point
Project, partner and release decisions need the relevant permitted records and calculated effects.
What the view brings together
Permission-visible traceability, readiness, approval, release, report or partner views.
What you can decide next
Review the source references and project records; the decision remains human.
Detailed documentation
Decision reviewProject, partner or release decision remains human
Records linkedProject question
Effects calculatedPartner evidence
Human decisionRelease basis
Illustrative static view

Guidance without conflation

Know which assistant supports which question

The authenticated product uses separate contracts for product orientation and integration project setup. Both remain distinct from the public Product Assistant.

Produktratgeber

Uses curated product knowledge for product questions and next-step orientation. Opening it does not automatically load integration project records.

Projekt-Assistent

Uses deterministic goal, source and setup checks to show a guided setup path and at most three safe next actions.