Workflow Reference Storage

Summary

Persisted Workflow correlation on Appraisal and its external ownership boundary.

Audience

Backend engineers, database reviewers, architects, QA, support, operations, security reviewers, and product owners.

Overview

Appraisal optionally stores one Workflow instance identity. An index supports callback correlation lookup, but no EF relationship exists because Workflow tasks and instances are externally owned.

Confirmed persistence behavior

• The reference is attached after self submission when remote Workflow start succeeds.
• Callback resolution can query Appraisal by Workflow identity.
• Duplicate callback handling relies on appraisal lifecycle state, not a separate callback receipt record.
• No Workflow task, step, decision history, callback payload, or remote status is persisted by Performance.
• The Workflow reference is retained after a terminal decision for traceability.
• Workflow start occurs outside the EF save transaction and can lead to multiple save boundaries.

Classification

Transitional external reference storage.

Requires confirmation

Reference uniqueness, callback receipt persistence, cleanup, authentication, and reconciliation require confirmation.

Diagram

Related Articles

• Performance database documentation
• Performance technical documentation

See Also

• Performance API documentation
• Performance business documentation

Keywords

• Performance persistence
• Workflow Reference Storage
• Draft database documentation

Source References

• microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
• microservices/src/performance-service/Domain/Appraisal/Appraisal.cs
• microservices/src/performance-service/Application/Commands/AppraisalCommands.cs

Revision Information

• Status: Draft
• Last reviewed: 2026-07-16
• Review cycle: Quarterly