Continuous Feedback (FBCK)

Peer feedback · 1:1 meeting notes · formal HR memos · recognition wall · real-time SignalR push — unified continuous feedback culture

Key Concepts Glossary

Database Schema

TFEEDBACK — Feedback Requests

TONONOTE — 1:1 Meeting Notes

TACTIONITEM — Action Items

TMEMO — Formal HR/Manager Memos

TRECOGNITION — Recognition & Appreciation

Feedback Lifecycle

Memo Lifecycle (Most Complex)

Recognition Flow

FeedbackSummaryDTO — PERM ESS Cross-Module

FBCK exposes a lean summary method called by PermESSBLL.GetMyPerformanceSummary to aggregate feedback counts into one ESS response without loading full feedback records:

// FBCKDAL/DTOs/FeedbackSummaryDTO.cs
public class FeedbackSummaryDTO {
    public int FeedbackCount          { get; set; }  // total feedback received, last 90 days
    public int PendingResponseCount   { get; set; }  // Requested/InProgress (Status=0 or 1)
    public int UnacknowledgedMemos    { get; set; }  // TMEMO Status=1 for this EmployeeId
    public int RecentRecognitionCount { get; set; }  // TRECOGNITION last 30 days for this employee
}

// IFeedbackBLL interface method
Task<FeedbackSummaryDTO> GetFeedbackSummaryForESS(int employeeId, LoginDTO login, CancellationToken ct);

FeedbackHub — SignalR

IFBCKClient — Strongly-Typed Client Contract

// FBCKSL/Hubs/IFBCKClient.cs
public interface IFBCKClient
{
    Task ReceiveFeedbackNotification(FeedbackDTO feedback);
    Task ReceiveMemoNotification(MemoDTO memo);
    Task ReceiveRecognitionNotification(RecognitionDTO recognition);
    Task ReceiveActionItemReminder(ActionItemDTO actionItem);
    Task ReceiveError(string errorMessage);
}

Hub Group Strategy — Dual Membership

// FeedbackHub.cs
public override async Task OnConnectedAsync()
{
    var login = GetLoginDTO();
    // Personal notifications group
    await Groups.AddToGroupAsync(Context.ConnectionId, $"fbck:user:{login.UserId}");
    // Tenant-wide recognition wall feed
    await Groups.AddToGroupAsync(Context.ConnectionId, $"fbck:client:{login.ClientId}");
    await base.OnConnectedAsync();
}

public override async Task OnDisconnectedAsync(Exception? exception)
{
    var login = GetLoginDTO();
    // CRITICAL: clean up BOTH groups on disconnect
    await Groups.RemoveFromGroupAsync(Context.ConnectionId, $"fbck:user:{login.UserId}");
    await Groups.RemoveFromGroupAsync(Context.ConnectionId, $"fbck:client:{login.ClientId}");
    await base.OnDisconnectedAsync(exception);
}

Server-Initiated Push (MemoBLL)

// MemoBLL.cs — injecting IHubContext for push after SendMemo
public class MemoBLL(
    IMemoDAL dal,
    IValidation validation,
    IKeyInvalidate keyInvalidate,
    IEventLogPublish eventLog,
    ILogger<MemoBLL> logger,
    IHubContext<FeedbackHub, IFBCKClient> hub)  // ← inject for server-push
{
    public async Task<string> SendMemoAsync(int memoId, LoginDTO login, CancellationToken ct)
    {
        GB5Trace.Step("validate-memo-send", new { memoId });
        var memo = await _dal.GetMemoAsync(memoId, login, ct);
        if (memo.Status != 0) throw new ValidationException("Only Draft memos can be sent");

        GB5Trace.Step("send-memo", new { memoId });
        await _dal.SendMemoAsync(memoId, login, ct);

        GB5Trace.Step("event-publish", new { EventTypes.FBCKMEMOSSENT });
        await _eventLog.PublishEventLogAsync(new EventLogDTO { ... }, login);

        // Push to recipient's personal group
        await _hub.Clients.Group($"fbck:user:{memo.ToEmployeeId}").ReceiveMemoNotification(memo);
        return SuccessResponse.UpdateSuccess;
    }
}

Hub is Receive-Only

API Endpoints Reference

Feedback

One-on-One Notes

Action Items

Memos

Recognition

Sample Scenarios

Scenario A — 360 Feedback Request

POST /Feedback/RequestFeedback
{
  "TargetEmployeeId": 201,
  "ResponderId": 305,
  "FeedbackType": 4,        // 360
  "ContextType": 1,         // AppraisalLinked
  "ContextId": 1042,        // AppraisalId
  "QuestionsJson": "[\"How effectively does this person collaborate with cross-functional teams?\",\"Rate their communication skills (1-5)\",\"What is one area they should focus on improving?\"]",
  "DueDate": "2026-04-15"
}

// Response: FeedbackId: 7823, Status: 0 (Requested)
// SignalR: push ReceiveFeedbackNotification to fbck:user:305 (the responder)

Scenario B — Disciplinary Memo Full Flow

// Step 1: HR creates confidential disciplinary memo (Draft)
POST /Feedback/Memo/SaveMemo
{ "ToEmployeeId": 201, "MemoType": 1, "Subject": "Attendance Warning - March 2026",
  "ContentHtml": "<p>Dear John, this formal warning...</p>",
  "IsConfidential": true }
// Result: MemoId: 312, Status: 0 (Draft)

// Step 2: HR sends memo
POST /Feedback/Memo/SendMemo { "MemoId": 312 }
// Result: Status → 1, SentOn: 2026-03-20 09:00
// SignalR push to fbck:user:201 → ReceiveMemoNotification
// ESS shows: "1 unacknowledged memo" but ContentHtml is HIDDEN (IsConfidential=true, Status=1)

// Step 3: Employee acknowledges (ESS)
POST /Feedback/Memo/AcknowledgeMemo { "MemoId": 312 }
// EmployeeId taken from login.UserId (not from request body)
// Result: Status → 2, AcknowledgedOn: 2026-03-21 14:30
// ContentHtml now revealed in ESS

Scenario C — Recognition Wall

Scenario D — 1:1 Meeting with Action Items

// SaveOneOnOneNote
{
  "EmployeeId": 201, "ManagerId": 150, "ScheduledDate": "2026-03-22",
  "AgendaJson": "[\"Q1 OKR review — goal at 75%\",\"Career development discussion\",\"Team collaboration concerns\"]",
  "NotesJson": "[\"ARR goal strong — 22/30 leads qualified\",\"Interested in Tech Lead path by Q3\",\"Friction with design team on specs\"]",
  "Status": 0
}

// Action items created from meeting:
POST /Feedback/ActionItem/SaveActionItem
{ "ContextType": 0, "ContextId": 891,    // TONONoteId
  "EmployeeId": 201, "OwnerId": 150,
  "ActionText": "Schedule design team retrospective with Lisa",
  "DueDate": "2026-04-01" }

POST /Feedback/ActionItem/SaveActionItem
{ "ContextType": 0, "ContextId": 891,
  "EmployeeId": 150, "OwnerId": 150,
  "ActionText": "Send Tech Lead career path resources and book 1:1 with L&D",
  "DueDate": "2026-03-28" }

Integration Map

Service Configuration

Caching Strategy

ESS Employee View

What an employee sees in their FBCK-sourced dashboard sections (via PERM ESS aggregation):