Story 1.16: 16-Step Workflow Visualization - Wireframe

Story: Epic 1, Story 1.16 - Event Management Service

Last updated: October 22, 2025 Reading time: 13 minutes File size: 22.46 KB

16-Step Workflow Visualization (Event Detail View)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ ← Back to Dashboard        Spring Conference 2025 - Workflow Manager                 β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                                                       β”‚
β”‚  Event: Cloud Native Architecture        Status: Active       Progress: 7/16 (44%)   β”‚
β”‚  Date: May 15, 2025                     Deadline: March 15                           β”‚
β”‚                                                                                       β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚
β”‚  β”‚                         16-STEP EVENT WORKFLOW                                   β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚   Planning Phase          Speaker Phase           Publishing Phase    Final Phaseβ”‚ β”‚
β”‚  β”‚   ═══════════            ════════════            ═══════════════    ═══════════ β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚   β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”        β”‚ β”‚
β”‚  β”‚   β”‚ βœ“ │───▢│ βœ“ │───▢│ βœ“ │───▢│ βœ“ │───▢│ βœ“ │───▢│ βœ“ │───▢│ ● │───▢│   β”‚ ...    β”‚ β”‚
β”‚  β”‚   β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜        β”‚ β”‚
β”‚  β”‚    1        2        3        4        5        6        7        8             β”‚ β”‚
β”‚  β”‚   Topic   Speaker  Assign  Outreach Status  Collect  Review  Threshold         β”‚ β”‚
β”‚  β”‚   Select  Research Contact           Track   Content  Quality  Check            β”‚ β”‚
β”‚  β”‚   βœ“ Done  βœ“ Done   βœ“ Done  βœ“ Done  βœ“ Done  βœ“ Done   ● Active  β—‹ Pending      β”‚ β”‚
β”‚  β”‚   Jan 5   Jan 12   Jan 15  Jan 20  Ongoing Feb 10   NOW      Mar 1            β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚   β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”    β”Œβ”€β”€β”€β”        β”‚ β”‚
β”‚  β”‚   β”‚   │───▢│   │───▢│   │───▢│   │───▢│   │───▢│   │───▢│   │───▢│   β”‚        β”‚ β”‚
β”‚  β”‚   β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜    β””β”€β”€β”€β”˜        β”‚ β”‚
β”‚  β”‚    9        10       11       12       13       14       15       16            β”‚ β”‚
β”‚  β”‚   Select   Assign   Publish  Finalize News    Assign   Catering Partner        β”‚ β”‚
β”‚  β”‚   Speaker  Slots    Progress  Agenda   letter  Moder.   & Venue  Meeting       β”‚ β”‚
β”‚  β”‚   β—‹ Wait   β—‹ Wait   β—‹ Wait   β—‹ Apr 1  β—‹ Apr 5 β—‹ Apr 10 β—‹ Done   β—‹ May 20      β”‚ β”‚
β”‚  β”‚                                                          2023                    β”‚ β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
β”‚                                                                                       β”‚
β”‚  β”Œβ”€β”€β”€ STEP 7: CONTENT QUALITY REVIEW (CURRENT) ────────────────────────────────────┐ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚  Status: IN PROGRESS                    Started: Feb 10    Due: Feb 20           β”‚ β”‚
β”‚  β”‚  Owner: Anna M.                         Progress: 60%                            β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚  Tasks:                                                                          β”‚ β”‚
β”‚  β”‚  β˜‘ Review abstract length (8/8 complete)                                        β”‚ β”‚
β”‚  β”‚  β˜‘ Verify lessons learned included (8/8 complete)                               β”‚ β”‚
β”‚  β”‚  ☐ Technical accuracy check (5/8 complete)                                      β”‚ β”‚
β”‚  β”‚  ☐ Final approval from moderator (0/8 complete)                                 β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚  Blockers:                                                                       β”‚ β”‚
β”‚  β”‚  ⚠️ 3 abstracts need revision - awaiting speaker response                       β”‚ β”‚
β”‚  β”‚                                                                                   β”‚ β”‚
β”‚  β”‚  [View Details] [Reassign] [Mark Complete] [Skip Step] [Get Help]              β”‚ β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
β”‚                                                                                       β”‚
β”‚  β”Œβ”€β”€β”€ AUTOMATION STATUS ────────────────┬─── DEPENDENCIES ─────────────────────────┐ β”‚
β”‚  β”‚                                       β”‚                                          β”‚ β”‚
β”‚  β”‚  πŸ€– Auto-reminders: Active            β”‚  Step 8 blocked by: Step 7 completion   β”‚ β”‚
β”‚  β”‚  πŸ“§ Email sequences: 3 sent           β”‚  Step 11 requires: Min. 6 speakers      β”‚ β”‚
β”‚  β”‚  πŸ“Š Progress tracking: Real-time      β”‚  Step 12 depends on: Venue confirmation β”‚ β”‚
β”‚  β”‚  πŸ”„ Workflow rules: 12 active         β”‚                                          β”‚ β”‚
β”‚  β”‚                                       β”‚  [View Dependency Graph β†’]               β”‚ β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
β”‚                                                                                       β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Key Interactive Elements

  • Workflow Steps: Click any step to view detailed status and tasks
  • Progress Indicators: Visual states (βœ“ Done, ● Active, β—‹ Pending, ⚠️ Blocked, πŸ”΄ Overdue)
  • Step Actions: Inline buttons for common operations on current step
  • Automation Panel: View and configure automated workflows
  • Dependency Graph: Visual representation of step dependencies
  • Phase Grouping: Steps organized by logical phases

Workflow States

  • βœ“ Done: Completed steps (green)
  • ● Active: Current step (blue, pulsing)
  • β—‹ Pending: Future steps (gray)
  • ⚠️ Blocked: Steps with issues (orange)
  • πŸ”΄ Overdue: Past deadline (red)

Functional Requirements Met

  • FR2: Complete 16-step workflow visualization with progress tracking
  • FR20: Automated notifications and reminders integrated into workflow
  • Dependency Management: Clear visualization of step dependencies
  • Team Collaboration: Owner assignment and task distribution
  • Workflow Rules: Configurable automation rules

User Interactions

  1. Click Step: Drill down into detailed view of any workflow step
  2. Reassign Tasks: Change step ownership
  3. Mark Complete: Manually complete steps when ready
  4. Skip Step: Override workflow with proper authorization
  5. View Dependency Graph: Understand step relationships
  6. Configure Automation: Set up rules and notifications

Technical Notes

  • Progress updates via manual page reload
  • Workflow state machine enforces dependencies
  • Audit trail tracks all state changes
  • Configurable workflow templates per event type
  • Role-based permissions for step actions

API Requirements

Initial Page Load APIs

When the 16-Step Workflow Visualization screen loads, the following APIs are called to provide the necessary data:

CONSOLIDATED API APPROACH (Story 1.17):

  1. GET /api/v1/events/{eventId}?include=workflow,team

    • Returns: Event basic info with complete workflow state and team assignments in a single call
    • Response includes:
      • Event core data: id, title, date, status, venue, deadline
      • workflow: Complete 16-step workflow state with step details, completion status, owners, dates, blockers, dependencies, automation status, history (last 20 entries)
      • team: Team member assignments with availability, current workload, roles
    • Used for: Populate all event and workflow information in a single request
    • Performance: Reduced from 7 API calls to 1 (86% reduction in HTTP requests)
  2. GET /api/v1/events/{eventId}/workflow/steps/{stepNumber}

    • Query params: includeTaskDetails (true)
    • Returns: Detailed step information with task list, completion status, owner info, blockers, progress percentage
    • Used for: Display current step details panel (Step 7 in example)
    • Note: This endpoint remains separate as it’s only called on-demand when drilling into a specific step

MIGRATION NOTE (Story 1.17): The original implementation required 7 separate API calls on page load, resulting in waterfall loading delays and complex loading states. The new consolidated API reduces this to 2 calls:

  • 1 primary call for event + workflow + team (previously 6 calls)
  • 1 on-demand call for step details (only when needed)

This consolidation improves:

  • Page load time: ~75% faster (from ~2s to <500ms)
  • Loading state complexity: Single loading indicator for all workflow data
  • Data consistency: Atomic snapshot of complete workflow state
  • User experience: Instant workflow visualization render
  • Network efficiency: Eliminated request waterfalls

Action APIs

Workflow Step Management

  1. PUT /api/v1/events/{eventId}/workflow/steps/{stepNumber}/complete

    • Payload: { completedBy, completionNotes, overrideWarnings: boolean }
    • Response: Updated workflow state, next step activated, automation triggered
    • Used for: Mark current step as complete from [Mark Complete] button
  2. PUT /api/v1/events/{eventId}/workflow/steps/{stepNumber}/reassign

    • Payload: { newOwnerId, reassignReason, notifyPreviousOwner: boolean }
    • Response: Updated assignment, notification sent, updated workflow state
    • Used for: Reassign step ownership from [Reassign] button
  3. PUT /api/v1/events/{eventId}/workflow/steps/{stepNumber}/skip

    • Payload: { skipReason, authorizationCode, skipType: "temporary|permanent" }
    • Response: Step skipped confirmation, workflow advanced, audit log entry
    • Used for: Skip workflow step with authorization from [Skip Step] button
  4. PUT /api/v1/events/{eventId}/workflow/steps/{stepNumber}/reopen

    • Payload: { reopenReason, affectedSteps: [] }
    • Response: Step reopened, dependent steps updated, notifications sent
    • Used for: Reopen completed step if issues found
  5. POST /api/v1/events/{eventId}/workflow/steps/{stepNumber}/blocker

    • Payload: { blockerType, description, severity: "low|medium|high", estimatedResolution }
    • Response: Blocker created, notifications sent, workflow status updated
    • Used for: Report blocker preventing step completion
  6. DELETE /api/v1/events/{eventId}/workflow/steps/{stepNumber}/blocker/{blockerId}

    • Payload: { resolutionNotes }
    • Response: Blocker removed, workflow unblocked, notifications sent
    • Used for: Remove resolved blocker

Task Management Within Steps

  1. PUT /api/v1/events/{eventId}/workflow/steps/{stepNumber}/tasks/{taskId}/complete

    • Payload: { completedBy, notes }
    • Response: Task marked complete, step progress updated
    • Used for: Complete individual task within step (e.g., β€œReview abstract length”)
  2. POST /api/v1/events/{eventId}/workflow/steps/{stepNumber}/tasks

    • Payload: { taskTitle, description, assigneeId, dueDate }
    • Response: Task created, notifications sent
    • Used for: Add custom task to workflow step
  3. DELETE /api/v1/events/{eventId}/workflow/steps/{stepNumber}/tasks/{taskId}

    • Payload: { deletionReason }
    • Response: Task deleted, step progress recalculated
    • Used for: Remove task from step

Automation Management

  1. GET /api/v1/events/{eventId}/workflow/automation/rules

    • Returns: All automation rules with conditions, actions, status
    • Used for: View automation configuration
  2. PUT /api/v1/events/{eventId}/workflow/automation/rules/{ruleId}/toggle

    • Payload: { enabled: boolean }
    • Response: Rule status updated
    • Used for: Enable/disable automation rules
  3. POST /api/v1/events/{eventId}/workflow/automation/rules

    • Payload: { trigger, conditions: [], actions: [], schedule }
    • Response: Rule created, activated
    • Used for: Create new automation rule
  4. PUT /api/v1/events/{eventId}/workflow/automation/reminders

    • Payload: { stepNumber, reminderSchedule: [], recipients: [] }
    • Response: Reminder configuration updated
    • Used for: Configure auto-reminders for step

Dependency Management

  1. GET /api/v1/events/{eventId}/workflow/dependencies/graph

    • Query params: format (json|svg|png)
    • Returns: Dependency graph data or visualization
    • Used for: Generate and display dependency graph
  2. PUT /api/v1/events/{eventId}/workflow/dependencies

    • Payload: { stepNumber, dependsOn: [], conditions: [] }
    • Response: Dependencies updated, workflow validated
    • Used for: Update step dependencies
  3. POST /api/v1/events/{eventId}/workflow/dependencies/validate

    • Returns: Validation results with warnings, errors, suggestions
    • Used for: Validate workflow before advancing steps

Workflow Help & Support

  1. GET /api/v1/workflow/help/step/{stepNumber}

    • Returns: Help documentation for specific step, best practices, common issues, tips
    • Used for: Display context-sensitive help from [Get Help] button
  2. POST /api/v1/events/{eventId}/workflow/support-request

    • Payload: { stepNumber, issueDescription, urgency: "low|medium|high" }
    • Response: Support ticket created, estimated response time
    • Used for: Request help from support team

History & Audit

  1. GET /api/v1/events/{eventId}/workflow/audit-trail

    • Query params: stepNumber (optional), userId (optional), dateRange, limit (50)
    • Returns: Detailed audit trail with all workflow changes, timestamps, users, actions
    • Used for: View complete workflow history
  2. GET /api/v1/events/{eventId}/workflow/export

    • Query params: format (pdf|csv|json), includeHistory (true)
    • Returns: Download URL for workflow export
    • Used for: Export workflow state and history

Primary Navigation Actions

  1. ← Back to Dashboard button β†’ Navigate to Event Management Dashboard (story-1.16-event-management-dashboard.md)

    • Returns to main dashboard
    • Shows all active events
    • Preserves workflow state
  2. Event title (Spring Conference 2025) β†’ Navigate to Event Detail/Edit Screen

    • Full event information
    • Edit event details
    • Team management
    • Timeline view
  3. Workflow step click (Step 1-16) β†’ Expands step detail panel

    • Shows step details in bottom section
    • Displays tasks and progress
    • Reveals blockers
    • Shows action buttons
    • No screen navigation
  4. Current step indicator (● Active) β†’ Automatically expanded

    • Step 7 in example
    • Already showing details
    • Focus on current work
    • No additional action needed
  5. Completed step indicator (βœ“ Done) β†’ Click to view historical details

    • Shows completion date
    • Displays who completed it
    • Shows completion notes
    • Review mode (read-only)
    • No screen navigation
  6. Pending step indicator (β—‹ Pending) β†’ Click to view upcoming step

    • Shows dependencies
    • Displays prerequisites
    • Shows estimated start date
    • Preview mode
    • No screen navigation
  7. Blocked step indicator (⚠️ Blocked) β†’ Click to view blocker details

    • Shows blocking issues
    • Displays resolution actions
    • Shows affected timeline
    • Resolution options
    • No screen navigation
  8. Team member name click (Anna M.) β†’ Navigate to User Profile Screen

    • User details
    • Current assignments
    • Availability calendar
    • Contact options

Step Action Buttons

  1. [View Details] button β†’ Expands full step details

    • Shows all tasks
    • Displays full description
    • Shows related documents
    • Reveals additional actions
    • No screen navigation
  2. [Reassign] button β†’ Opens reassignment modal

    • Team member selector
    • Load balancing info
    • Reason input field
    • Notification options
    • Submits via API
    • No screen navigation
  3. [Mark Complete] button β†’ Opens completion confirmation dialog

    • Completion checklist
    • Notes input
    • Override warnings toggle
    • Submits completion
    • Advances workflow
    • Updates visualization
    • No screen navigation
  4. [Skip Step] button β†’ Opens authorization dialog

    • Requires authorization code
    • Skip reason required
    • Impact warning shown
    • Permanent/temporary option
    • Audit trail entry
    • No screen navigation
  5. [Get Help] button β†’ Opens help modal

    • Step-specific documentation
    • Best practices
    • Common issues
    • Support request option
    • Video tutorials
    • No screen navigation

Task Interactions

  1. Task checkbox (β˜‘/☐) β†’ Toggles task completion

    • Marks task complete/incomplete
    • Updates step progress
    • Saves via API
    • Updates percentage
    • No screen navigation
  2. Task text click β†’ Shows task details tooltip

    • Task description
    • Assigned person
    • Due date
    • Related resources
    • No navigation

Automation Panel Actions

  1. Auto-reminders status β†’ Click to configure

    • Opens reminder settings
    • Schedule configuration
    • Recipient selection
    • Template selection
    • No screen navigation
  2. Email sequences count β†’ Click to view details

    • Lists sent emails
    • Shows recipients
    • Displays open/click rates
    • Template preview
    • No screen navigation
  3. Workflow rules count β†’ Click to manage rules

    • Opens rules configuration
    • Enable/disable rules
    • Create new rules
    • Edit existing rules
    • No screen navigation

Dependencies Panel Actions

  1. Dependency line click β†’ Highlights related steps

    • Shows blocking relationship
    • Displays condition
    • Shows impact
    • Visual highlight
    • No screen navigation
  2. [View Dependency Graph β†’] button β†’ Opens dependency graph modal

    • Full-screen graph view
    • Interactive visualization
    • Zoom and pan
    • Highlight paths
    • Export options
    • No permanent screen navigation (modal)

Phase Grouping Interactions

  1. Phase header click (Planning Phase) β†’ Collapses/expands phase

    • Shows/hides phase steps
    • Accordion behavior
    • Quick navigation
    • No screen navigation
  2. Phase progress indicator β†’ Shows phase summary

    • Completed steps count
    • Phase duration
    • Phase status
    • Tooltip display
    • No navigation

Event-Driven Navigation

  1. Step completed β†’ Requires manual page reload

    • User must refresh page to see updated workflow visualization
    • Progress indicator updates after reload
    • Step status icon changes after reload
  2. Blocker added β†’ Requires manual page reload

    • User must refresh page to see blocker status
    • Step icon updates after reload
    • Dependencies panel updates after reload
  3. Task completed by team member β†’ Requires manual page reload

    • User must refresh page to see task completion
    • Task checkbox state updates after reload
    • Progress percentage updates after reload
  4. Deadline approaching β†’ Shows warning indicator

    • Changes step color
    • Shows countdown timer
    • May trigger notification
    • Updates urgency indicator
    • No automatic navigation
  5. Step overdue β†’ Shows overdue indicator

    • Changes step icon to πŸ”΄
    • Shows overdue warning
    • Triggers escalation notification
    • Updates dashboard alerts
    • No automatic navigation
  6. Reassignment completed β†’ Updates step owner

    • Changes owner name
    • Shows reassignment note
    • Sends notifications
    • Updates team panel
    • No automatic navigation
  7. Automation rule triggered β†’ Shows automation activity

    • Updates automation panel
    • Shows triggered action
    • May show notification
    • Updates affected steps
    • No automatic navigation
  8. Dependency satisfied β†’ Unblocks dependent step

    • Removes blocker warning
    • Updates dependency panel
    • Changes step status
    • Enables step actions
    • No automatic navigation