Diamant

Needs you

  • Inbox
  • Decisions
  • Plans
  • Code

Pipeline

  • Activity
  • Graph
Sign in
Plans/

PublicFacingInterface: Table with processing status of files

Brain review
ADO work item#337988Product Backlog Item

PublicFacingInterface: Table with processing status of files

Synced just nowOpen in ADO
State
Done
Assigned
Patrick Fichtner
Area
Diamant Entwicklung\Produkt\Projektteams\Cross Functional Services\Mathildenhoehe\ITP
Project
Diamant Entwicklung
Freshness
Synced just now

ADO description

As a bookkeeper, I want to see the progress of the invoice or a clear error if it fails — so that I always know whether my invoice was processed successfully.

ADO acceptance criteria

We have a table of the files that are currently processed, which is based on the L2 screenshots (see below) from the prototype: We update the table content (with update button), based on an execution feed endpoint from the AgentRuntime out of scope ( @Martin Riedl, Dr. ) : Table is updated when file is uploaded (see #337830 ) continuously update of feed in near-realtime

Parent

  • #337664ITP: Upload invoice and send to orchestration service and visualise processing(New)

Children

  • #338193Frontend: ExecutionFeedToolbar (Dumb Component + Spec)(Done)
  • #338307Wire ExecutionFeedAdapter to Agent Runtime HTTP client(Done)
  • #338195Backend: Domain-Modell + Interface (ExecutionFeed.cs, IExecutionFeedService.cs)(Done)

Linked PRs

  • ITP-Public-Facing-Interface#61158PR 61158(unknown)
  • ITP-Public-Facing-Interface#61299PR 61299(unknown)
  • ITP-Public-Facing-Interface#61298PR 61298(unknown)

Plan review. The agent proposed a plan. Review it below, then approve so it can start coding — or request changes.

Azure DevOps
  5. Human review

Implement the approved work packet "Show processing-status column in the execution-feed cockpit table" with a scoped branch and human-reviewed PR.

high risk

The implementation agent can change source code and open a PR, so dashboard approval is required before coding and before PR creation.

Expected files

None listed.

Implementation steps

  • 1.Inspect the work packet evidence, parent work item context, and linked pull request/code context before editing.
  • 2.Locate the owning repository and smallest set of files needed for the requested behavior.
  • 3.Make a narrow implementation change on an ai/work-packet branch.
  • 4.Run the focused test/typecheck command for the touched package or application.
  • 5.Collect the diff and test output for dashboard review before opening a PR.

Test plan

  • #338190Branch anlegen: feature/337988-execution-feed-table(Done)
  • #338196Backend: Adapter + Controller + DTOs + MappingExtensions(Done)
  • #338191Frontend: Shared State Infrastruktur (service-state.ts, execution-feed.ts)(Done)
  • #338194Frontend: ExecutionFeed (Smart Component) + Cockpit + Routing + i18n(Done)
  • #338533Pre-Connect Merge-Arbeiten(Done)
  • #338192Frontend: ExecutionFeedService + Spec(Done)
  • #338198CLAUDE.md aktualisieren (Service-Pattern, Smart/Dumb, styleUrl, Backend-Konventionen)(Done)
  • #338197Backend: Tests (Unit + Integration) + DI-Registrierung in Program.cs(Done)

    • Siblings

    • #337985PublicFacingInterface: Upload Button & Dialog(Removed)
    • #337989PublicFacingInterface: Endpoint to upload files(Done)
    • #337994AgentRuntime: endpoint to receive & process job description (url & metadata) of uploaded file(Done)
    • #337997AgentRuntime: endpoint to get execution state (Agent persistence)(Done)
    • #337995AgenticWorkflow: implement a first agent orchestrator that calls agents(Done)
    • #337996AgenticWorkflow: implement first special agents(Done)
    • #338024FoundationCapabilities: Diamant 4 Connectivity & MCP Wrapper(Removed)
    • ·Run the most focused unit test or typecheck for the touched package.
    • ·Run the repository-level validation command if the focused test does not cover the changed surface.

    Repositories

    • ·ITP-Public-Facing-Interface