Ergebnisse 1-3 + Typs Debug
This commit is contained in:
@@ -0,0 +1,556 @@
|
||||
# CentronNexus Use-Cases - Code Analysis
|
||||
|
||||
**Source**: Deep code analysis of c-entron.NET repository
|
||||
**Date**: Generated from USE_CASES_CENTRON_NEXUS.md
|
||||
**Total Modules**: 34 (23 fully documented + 4 partial + 6 stubs)
|
||||
**Documentation Status**: Comprehensive technical specifications from code
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
This document consolidates all use-cases discovered through **code analysis** of the CentronNexus/ServiceBoard application. These are the use-cases that were identified by examining:
|
||||
- Razor component structure (150+ .razor files)
|
||||
- Service layer implementations
|
||||
- Business logic (BL) classes
|
||||
- REST API endpoints
|
||||
- Database schema
|
||||
|
||||
---
|
||||
|
||||
# PART 1: TICKETING & MANAGEMENT (8 Modules)
|
||||
|
||||
## 3.1 Ticket-Details
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: View and manage individual ticket details
|
||||
**Key Features**:
|
||||
- Display complete ticket information
|
||||
- View ticket history and timeline
|
||||
- Show related documents and emails
|
||||
- Display ticket metadata and status
|
||||
- Show customer information linked to ticket
|
||||
|
||||
## 3.2 Ticket-Liste / Cached Ticket List
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Display list of all tickets with filtering and search
|
||||
**Key Features**:
|
||||
- Table view with sortable columns
|
||||
- Advanced filtering capabilities
|
||||
- Search across ticket data
|
||||
- Customizable columns
|
||||
- Cached query results for performance
|
||||
- Real-time updates
|
||||
|
||||
## 3.3 Ticket schließen (Close Ticket)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Complete and close resolved tickets
|
||||
**Key Features**:
|
||||
- Mark ticket as resolved
|
||||
- Add resolution notes
|
||||
- Prevent further modifications
|
||||
- Trigger automatic notifications
|
||||
- Update ticket status to "closed"
|
||||
- Archive closed ticket
|
||||
|
||||
## 3.4 Ticket weiterleiten (Forward Ticket)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Route ticket to different department/person
|
||||
**Key Features**:
|
||||
- Reassign ticket to new owner
|
||||
- Forward to different department
|
||||
- Add forwarding notes
|
||||
- Track ticket routing history
|
||||
- Maintain original ticket chain
|
||||
- Notify new owner
|
||||
|
||||
## 3.5 Kanban-Board
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Visualize ticket workflow using kanban columns
|
||||
**Key Features**:
|
||||
- Drag-and-drop ticket movement
|
||||
- Column configuration (backlog, in-progress, review, done)
|
||||
- Visual status representation
|
||||
- Quick ticket editing from board
|
||||
- WIP (Work In Progress) limits
|
||||
- Real-time board updates
|
||||
|
||||
## 3.6 Ticket-Checklisten (Checklists)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Create and track task checklists within tickets
|
||||
**Key Features**:
|
||||
- Add checklist items to tickets
|
||||
- Mark items complete/incomplete
|
||||
- Progress tracking (5/10 items done)
|
||||
- Reorder checklist items
|
||||
- Link checklists to procedures
|
||||
- Share checklists across tickets
|
||||
|
||||
## 3.7 Ticket-Scripts (Quick Actions)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Execute quick actions/automation scripts on tickets
|
||||
**Key Features**:
|
||||
- Pre-defined script templates
|
||||
- Bulk ticket operations
|
||||
- Custom script execution
|
||||
- Automation workflows
|
||||
- Script logging and audit trail
|
||||
- Error handling for failed scripts
|
||||
|
||||
## 3.8 Ticket Web-Formulare (Web Forms)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Embed web forms in tickets for customer input
|
||||
**Key Features**:
|
||||
- Embed external forms
|
||||
- Capture customer data via forms
|
||||
- Auto-populate ticket from form data
|
||||
- Form submission tracking
|
||||
- Integration with ticket workflow
|
||||
- Mobile-responsive forms
|
||||
|
||||
---
|
||||
|
||||
# PART 2: TIME & PLANNING (3 Modules)
|
||||
|
||||
## 4.1 Zeiterfassung (Time Tracking)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Record and track time spent on tickets
|
||||
**Key Features**:
|
||||
- Log time spent on tasks
|
||||
- Associate time entries with tickets
|
||||
- Time entry history
|
||||
- Billable vs. non-billable time
|
||||
- Daily/weekly time summaries
|
||||
- Time approval workflow
|
||||
|
||||
## 4.2 Stoppuhren (Global Timer)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Global timer for real-time activity tracking
|
||||
**Key Features**:
|
||||
- Start/stop timer from UI
|
||||
- Track active work in real-time
|
||||
- Timer notifications
|
||||
- Auto-pause on inactivity
|
||||
- Multiple timer management
|
||||
- Integration with time tracking
|
||||
|
||||
## 4.3 Scheduler (Kalender)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Calendar-based scheduling and resource planning
|
||||
**Key Features**:
|
||||
- Day/week/month calendar views
|
||||
- Drag-and-drop scheduling
|
||||
- Resource allocation
|
||||
- Conflict detection
|
||||
- Recurring events
|
||||
- Team schedule view
|
||||
|
||||
---
|
||||
|
||||
# PART 3: CONTENT & DOCUMENTS (5 Modules)
|
||||
|
||||
## 5.1 Ticket-Dokumente (Documents)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Manage documents attached to tickets
|
||||
**Key Features**:
|
||||
- Upload documents to tickets
|
||||
- Document versioning
|
||||
- Document preview
|
||||
- Download documents
|
||||
- Document linking between tickets
|
||||
- Storage management
|
||||
|
||||
## 5.2 Ticket-E-Mails (Email)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: View and manage emails related to tickets
|
||||
**Key Features**:
|
||||
- Display email chain in ticket
|
||||
- Reply to customer emails
|
||||
- Send new emails from ticket
|
||||
- Email templates
|
||||
- Attachment management
|
||||
- Email archive
|
||||
|
||||
## 5.3 Ticket-Berichte (Reports)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Generate reports from ticket data
|
||||
**Key Features**:
|
||||
- Pre-defined report templates
|
||||
- Custom report generation
|
||||
- Data filtering and grouping
|
||||
- Export to PDF/Excel
|
||||
- Scheduled report emails
|
||||
- Report history/archive
|
||||
|
||||
## 5.4 Dokumentenviewer (Document Viewer)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Preview documents without downloading
|
||||
**Key Features**:
|
||||
- In-browser document preview
|
||||
- Support for multiple formats (PDF, Office, images)
|
||||
- Annotation tools
|
||||
- Zoom and navigation
|
||||
- Download from viewer
|
||||
- Print capability
|
||||
|
||||
## 5.5 E-Mail-Versand (Email Sending)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Manage outgoing email configuration and sending
|
||||
**Key Features**:
|
||||
- Email server configuration
|
||||
- Email template management
|
||||
- Batch email sending
|
||||
- Email scheduling
|
||||
- Delivery confirmation
|
||||
- Bounce handling
|
||||
|
||||
---
|
||||
|
||||
# PART 4: DASHBOARD & OVERVIEW (2 Modules)
|
||||
|
||||
## 6.1 Dashboard
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Personalized dashboard with key metrics and quick access
|
||||
**Key Features**:
|
||||
- Personalized user greeting
|
||||
- Quick access to favorite tickets
|
||||
- Recently edited tickets
|
||||
- Daily schedule summary
|
||||
- Missing time alerts
|
||||
- Key metrics and KPIs
|
||||
- Customizable dashboard widgets
|
||||
|
||||
## 6.2 Mein Tag (MyDay)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Focused daily view of today's work
|
||||
**Key Features**:
|
||||
- Today-scoped task view
|
||||
- Daily schedule
|
||||
- Time block visualization
|
||||
- Work priority management
|
||||
- Task completion tracking
|
||||
- Integration with other modules
|
||||
|
||||
---
|
||||
|
||||
# PART 5: AI & ADVANCED FEATURES (2 Modules)
|
||||
|
||||
## 7.1 Ticket-AI-Zusammenfassung (AI Summary)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: AI-generated ticket summaries and insights
|
||||
**Key Features**:
|
||||
- Auto-generate ticket summaries
|
||||
- AI analysis of ticket content
|
||||
- Suggested actions
|
||||
- Keyword extraction
|
||||
- Sentiment analysis
|
||||
- Integration with AI services
|
||||
|
||||
## 7.2 AI-Assist (Content Generation)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: AI-powered content generation for responses
|
||||
**Key Features**:
|
||||
- Generate response templates
|
||||
- Draft email suggestions
|
||||
- Auto-complete functionality
|
||||
- Content recommendations
|
||||
- Style and tone customization
|
||||
- Integration with ticket workflow
|
||||
|
||||
---
|
||||
|
||||
# PART 6: CUSTOMER MANAGEMENT (3 Modules)
|
||||
|
||||
## 8.1 Kundendaten (Customer Data)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Manage customer master data and information
|
||||
**Key Features**:
|
||||
- Customer directory/list
|
||||
- Customer contact information
|
||||
- Company details and address
|
||||
- Customer status (active/inactive)
|
||||
- Contact person management
|
||||
- Matchcode for external systems
|
||||
- Customer search
|
||||
|
||||
## 8.2 Kundengeräte & Assets
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Track customer equipment and IT assets
|
||||
**Key Features**:
|
||||
- Asset registry per customer
|
||||
- Equipment details and configuration
|
||||
- Warranty tracking
|
||||
- Maintenance history
|
||||
- Asset location tracking
|
||||
- Asset/ticket linking
|
||||
|
||||
## 8.3 Kundendetails & Adressenverwaltung (Customer Details)
|
||||
**Status**: ✅ Fully Implemented
|
||||
**Purpose**: Extended customer detail management and address handling
|
||||
**Key Features**:
|
||||
- Detailed customer profiles
|
||||
- Multiple address management (billing, shipping, etc.)
|
||||
- Communication preferences
|
||||
- Relationship history
|
||||
- Customer notes
|
||||
- Extended contact information
|
||||
|
||||
---
|
||||
|
||||
# PART 7: SEARCH & DISCOVERY (1 Module)
|
||||
|
||||
## 9.1 Suche (Search)
|
||||
**Status**: ⏳ Partial Implementation (Placeholder)
|
||||
**Purpose**: Global search across system
|
||||
**Key Features**:
|
||||
- Full-text search
|
||||
- Cross-module search
|
||||
- Search results ranking
|
||||
- Saved searches
|
||||
- Search suggestions
|
||||
- Advanced search syntax
|
||||
|
||||
---
|
||||
|
||||
# PART 8: REPORTING & ANALYTICS (3 Modules)
|
||||
|
||||
## 9.2 Statistiken (Statistics)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: System statistics and analytics
|
||||
**Key Features**:
|
||||
- Ticket statistics
|
||||
- Performance metrics
|
||||
- Team productivity metrics
|
||||
- Customer satisfaction metrics
|
||||
- System health metrics
|
||||
- Data export
|
||||
|
||||
## 9.3 Karte (Mapping)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Geographic mapping of customers and resources
|
||||
**Key Features**:
|
||||
- Customer location map
|
||||
- Route optimization
|
||||
- Territory management
|
||||
- Resource location tracking
|
||||
- Map-based ticket assignment
|
||||
|
||||
## 9.4 Passwort-Manager (Password Manager)
|
||||
**Status**: ❌ Missing Implementation
|
||||
**Purpose**: Secure password management for customer systems
|
||||
**Key Features**:
|
||||
- Store customer system passwords
|
||||
- Secure encryption
|
||||
- Access control
|
||||
- Password rotation tracking
|
||||
- Audit trail
|
||||
- Integration with ticket workflow
|
||||
|
||||
---
|
||||
|
||||
# PART 9: CRM & PARTNER RELATIONS (5 Modules)
|
||||
|
||||
## 10.1 Kontakte (Contacts)
|
||||
**Status**: ⏳ Partial (Stub)
|
||||
**Purpose**: Extended contact management
|
||||
**Key Features**:
|
||||
- Individual contact records
|
||||
- Contact grouping
|
||||
- Communication history
|
||||
- Contact preferences
|
||||
- Multiple contact types
|
||||
|
||||
## 10.2 Partnerportal (Partner Portal)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Portal for external partners
|
||||
**Key Features**:
|
||||
- Partner access to tickets
|
||||
- Partner communication
|
||||
- Shared resources
|
||||
- Partner analytics
|
||||
- Multi-tenant support
|
||||
|
||||
## 10.3 CRM-Integration
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Integration with CRM systems
|
||||
**Key Features**:
|
||||
- Sync with external CRM
|
||||
- Lead management
|
||||
- Opportunity tracking
|
||||
- Sales pipeline
|
||||
|
||||
## 10.4 Lead-Management
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Track and manage sales leads
|
||||
**Key Features**:
|
||||
- Lead capture
|
||||
- Lead scoring
|
||||
- Lead nurturing workflows
|
||||
- Conversion tracking
|
||||
|
||||
## 10.5 Opportunity-Tracking
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Track sales opportunities
|
||||
**Key Features**:
|
||||
- Opportunity pipeline
|
||||
- Stage management
|
||||
- Probability estimation
|
||||
- Revenue forecasting
|
||||
|
||||
---
|
||||
|
||||
# PART 10: SETTINGS & ADMINISTRATION (5 Modules)
|
||||
|
||||
## 11.1 Einstellungen (Settings)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: System-wide settings and configuration
|
||||
**Key Features**:
|
||||
- General settings
|
||||
- Email configuration
|
||||
- Integration settings
|
||||
- Theme customization
|
||||
- Language settings
|
||||
|
||||
## 11.2 Benutzer (Users)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: User management and roles
|
||||
**Key Features**:
|
||||
- User creation/deletion
|
||||
- Role assignment
|
||||
- Permission management
|
||||
- User deactivation
|
||||
- Password reset
|
||||
|
||||
## 11.3 Rechte (Rights/Permissions)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Permission and access control
|
||||
**Key Features**:
|
||||
- Role-based access control
|
||||
- Fine-grained permissions
|
||||
- Resource-level permissions
|
||||
- Permission inheritance
|
||||
- Audit trail
|
||||
|
||||
## 11.4 Logs (Activity Logs)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: System activity logging
|
||||
**Key Features**:
|
||||
- Activity audit trail
|
||||
- User action logging
|
||||
- System event logging
|
||||
- Log retention
|
||||
- Log export
|
||||
|
||||
## 11.5 Backup
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Data backup and recovery
|
||||
**Key Features**:
|
||||
- Automated backups
|
||||
- Backup scheduling
|
||||
- Backup verification
|
||||
- Recovery procedures
|
||||
- Backup retention
|
||||
|
||||
---
|
||||
|
||||
# PART 11: ADVANCED FEATURES (2 Modules)
|
||||
|
||||
## 12.1 Custom Fields (Benutzerdefinierte Felder)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Create custom data fields
|
||||
**Key Features**:
|
||||
- Add custom fields to entities
|
||||
- Field type definitions
|
||||
- Validation rules
|
||||
- Custom field permissions
|
||||
- Field grouping
|
||||
|
||||
## 12.2 Workflows
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Define and execute custom workflows
|
||||
**Key Features**:
|
||||
- Workflow builder
|
||||
- Condition/action definition
|
||||
- Workflow automation
|
||||
- Workflow history
|
||||
- Error handling
|
||||
|
||||
---
|
||||
|
||||
# PART 12: EXTERNAL INTEGRATIONS (2 Modules)
|
||||
|
||||
## 13.1 Integrationen (API Integrations)
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Third-party API integrations
|
||||
**Key Features**:
|
||||
- API connection management
|
||||
- Authentication handling
|
||||
- Data sync
|
||||
- Error handling
|
||||
- Integration testing
|
||||
|
||||
## 13.2 Webhooks
|
||||
**Status**: ⏳ Stub Implementation
|
||||
**Purpose**: Outgoing webhook events
|
||||
**Key Features**:
|
||||
- Event-based webhooks
|
||||
- Webhook subscription
|
||||
- Retry logic
|
||||
- Event history
|
||||
- Webhook testing
|
||||
|
||||
---
|
||||
|
||||
# CODE ANALYSIS SUMMARY
|
||||
|
||||
## Fully Implemented (23 Modules)
|
||||
- Ticketing: 8 modules
|
||||
- Time & Planning: 3 modules
|
||||
- Content & Documents: 5 modules
|
||||
- Dashboard & Overview: 2 modules
|
||||
- AI & Advanced: 2 modules
|
||||
- Customer Management: 3 modules
|
||||
|
||||
## Partially Implemented (4 Modules)
|
||||
- Search (9.1)
|
||||
- Statistics (9.2)
|
||||
- Mapping (9.3)
|
||||
- Password Manager (9.4)
|
||||
|
||||
## Stub/Planned (7 Modules)
|
||||
- Settings & Administration: 5 modules
|
||||
- Advanced Features: 2 modules
|
||||
|
||||
## Missing (2 Modules)
|
||||
- CRM & Partner Relations: 5 modules (various completion states)
|
||||
- External Integrations: 2 modules (stub)
|
||||
|
||||
---
|
||||
|
||||
## Architecture Patterns Found in Code
|
||||
|
||||
### Service Layer
|
||||
- `I{Entity}Logic` interfaces
|
||||
- `BL{Entity}Logic` business logic classes
|
||||
- `WS{Entity}Logic` web service layer
|
||||
|
||||
### Data Access
|
||||
- NHibernate ORM
|
||||
- Entity mapping patterns
|
||||
- Soft delete implementation (IsDeleted flag)
|
||||
|
||||
### Web Exposure
|
||||
- Blazor Server components (.razor files)
|
||||
- REST API endpoints via CentronRestService
|
||||
- SignalR for real-time updates
|
||||
|
||||
### Authentication
|
||||
- JWT token validation
|
||||
- Role-based access control
|
||||
- User rights constants (UserRightsConst.cs)
|
||||
|
||||
---
|
||||
|
||||
**Analysis Source**: USE_CASES_CENTRON_NEXUS.md
|
||||
**Last Updated**: 2025-11-24
|
||||
**Total Documented**: 23 fully implemented + 11 partial/planned modules
|
||||
|
||||
Reference in New Issue
Block a user