ERP HRM · WORD DOCUMENT VIEW · V1.0c

عرض الـUser Stories بنفس ملف الـWord

طريقة عرض إضافية لا تستبدل التحليل الحالي: اختر الإدارة ثم الـEpic، وستظهر كل القصص تحته بنفس ترتيب الصفوف وألوان المصدر.

العودة للتحليل الفني

171 Story معتمدة في V1.0c2 إضافة نظام خارج الملف1 · 3 · 5 Epics مذكورة في سجل تحديث V1.0c

الإدارةEpic / Module

EPIC DOCUMENT · كل القصص في صفحة واحدة

Serial Number Configuration

0 من المصدر المعتمد

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

As an Admin, I want to create a serial number configuration, so that a selected module/model can generate automatic serials.

Serial Number Configuration

SerialConfig-Create-003Canonical SRS Graph

As an Admin, I want to create a serial number configuration, so that a selected module/model can generate automatic serials.

User Story

As an Admin, I want to create a serial number configuration, so that a selected module/model can generate automatic serials.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to create a serial number configuration, so that a selected module/model can generate automatic serials.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to create a serial number configuration, so that a selected module/model can generate automatic serials.

Acceptance Criteria

Module, model, prefix, reset type, number of zeros, and status are required.
The system must prevent duplicate active configurations for the same module/model unless explicitly allowed.
If the reset type is Yearly, the serial format uses Prefix-Year-Sequence, such as INV-2026-0001.
If the reset type is Monthly, the serial format uses Prefix-Year-Month-Sequence, such as INV-2026-05-0001.
The sequence counter represents the number of records created for that model within the configured reset period.
The serial value should be generated automatically when a new record is created in the linked model.
Generated serial fields on business records must be read-only after creation unless special admin correction is allowed.
Create / Edit serial number configuration — field dictionary

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Admin سيناريو Create Serial Number Configuration ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Module, model, prefix, reset type, number of zeros, and status are required.
ERP_SRS acceptance test: The system must prevent duplicate active configurations for the same module/model unless explicitly allowed.
ERP_SRS acceptance test: If the reset type is Yearly, the serial format uses Prefix-Year-Sequence, such as INV-2026-0001.
ERP_SRS acceptance test: If the reset type is Monthly, the serial format uses Prefix-Year-Month-Sequence, such as INV-2026-05-0001.
ERP_SRS acceptance test: The sequence counter represents the number of records created for that model within the configured reset period.
ERP_SRS acceptance test: The serial value should be generated automatically when a new record is created in the linked model.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want to delete unused serial configurations, so that unused setup records can be removed safely.

Serial Number Configuration

SerialConfig-Delete-005Canonical SRS Graph

As an Admin, I want to delete unused serial configurations, so that unused setup records can be removed safely.

User Story

As an Admin, I want to delete unused serial configurations, so that unused setup records can be removed safely.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to delete unused serial configurations, so that unused setup records can be removed safely.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to delete unused serial configurations, so that unused setup records can be removed safely.

Acceptance Criteria

Delete is allowed only if no serial number was generated from this configuration.
If serials were generated, delete is blocked and the system should suggest deactivation.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Admin سيناريو Delete Serial Configuration with Blocking Rules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Delete is allowed only if no serial number was generated from this configuration.
ERP_SRS acceptance test: If serials were generated, delete is blocked and the system should suggest deactivation.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a System, I want to generate serial numbers automatically when records are created, so that all linked modules use consistent numbering.

Serial Number Configuration

SerialConfig-Generate-006Canonical SRS Graph

As a System, I want to generate serial numbers automatically when records are created, so that all linked modules use consistent numbering.

User Story

As a System, I want to generate serial numbers automatically when records are created, so that all linked modules use consistent numbering.

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to generate serial numbers automatically when records are created, so that all linked modules use consistent numbering.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to generate serial numbers automatically when records are created, so that all linked modules use consistent numbering.

Acceptance Criteria

When a linked model record is created, the system reads the active configuration for that module/model.
The system generates a unique serial using prefix, year, optional month, and padded sequence.
The generated serial must be unique per model and reset period.
Serial generation must be transaction-safe to avoid duplicate numbers during concurrent creation.
If no active configuration exists for a required model, the system must block creation or use fallback policy according to configuration.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System سيناريو Generate Serial Number for Linked Model Records ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: When a linked model record is created, the system reads the active configuration for that module/model.
ERP_SRS acceptance test: The system generates a unique serial using prefix, year, optional month, and padded sequence.
ERP_SRS acceptance test: The generated serial must be unique per model and reset period.
ERP_SRS acceptance test: Serial generation must be transaction-safe to avoid duplicate numbers during concurrent creation.
ERP_SRS acceptance test: If no active configuration exists for a required model, the system must block creation or use fallback policy according to configuration.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want to list serial number configurations, so that I can monitor numbering rules per module and model.

Serial Number Configuration

SerialConfig-List-001Canonical SRS Graph

As an Admin, I want to list serial number configurations, so that I can monitor numbering rules per module and model.

User Story

As an Admin, I want to list serial number configurations, so that I can monitor numbering rules per module and model.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to list serial number configurations, so that I can monitor numbering rules per module and model.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to list serial number configurations, so that I can monitor numbering rules per module and model.

Acceptance Criteria

Filter by module, model, status, reset type, and date range.
Show columns including module, model, prefix, includes year, includes month, number of zeros, reset type, next number preview, status, and actions.
Inactive configurations remain visible for audit but cannot be used for new serial generation.
The list must display dynamic summary cards such as active configurations, inactive configurations, yearly reset configurations, and monthly reset configurations based on selected filters.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Admin سيناريو View and Monitor Serial Number Configurations ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Filter by module, model, status, reset type, and date range.
ERP_SRS acceptance test: Show columns including module, model, prefix, includes year, includes month, number of zeros, reset type, next number preview, status, and actions.
ERP_SRS acceptance test: Inactive configurations remain visible for audit but cannot be used for new serial generation.
ERP_SRS acceptance test: The list must display dynamic summary cards such as active configurations, inactive configurations, yearly reset configurations, and monthly reset configurations based on selected filters.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a System, I want to reset serial counters based on configured period, so that numbering starts again per year or per month when required.

Serial Number Configuration

SerialConfig-Reset-007Canonical SRS Graph

As a System, I want to reset serial counters based on configured period, so that numbering starts again per year or per month when required.

User Story

As a System, I want to reset serial counters based on configured period, so that numbering starts again per year or per month when required.

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to reset serial counters based on configured period, so that numbering starts again per year or per month when required.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to reset serial counters based on configured period, so that numbering starts again per year or per month when required.

Acceptance Criteria

Yearly reset starts sequence from 0001 at the beginning of each new year.
Monthly reset starts sequence from 0001 at the beginning of each new month.
If the reset type is None, the sequence continues without period reset.
The system must store period keys such as 2026 or 2026-05 to separate counters.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System سيناريو Apply Yearly or Monthly Reset Rules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Yearly reset starts sequence from 0001 at the beginning of each new year.
ERP_SRS acceptance test: Monthly reset starts sequence from 0001 at the beginning of each new month.
ERP_SRS acceptance test: If the reset type is None, the sequence continues without period reset.
ERP_SRS acceptance test: The system must store period keys such as 2026 or 2026-05 to separate counters.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want to edit serial number configuration, so that corrections can be applied without breaking generated references.

Serial Number Configuration

SerialConfig-Update-004Canonical SRS Graph

As an Admin, I want to edit serial number configuration, so that corrections can be applied without breaking generated references.

User Story

As an Admin, I want to edit serial number configuration, so that corrections can be applied without breaking generated references.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to edit serial number configuration, so that corrections can be applied without breaking generated references.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to edit serial number configuration, so that corrections can be applied without breaking generated references.

Acceptance Criteria

Prefix, reset type, and number of zeros can be edited only if no serial has been generated, unless the admin correction policy allows future-only changes.
Generated serials already assigned to records must not be changed by updating configuration.
Changing configuration after usage must affect only future generated serials and must be logged in the audit trail.
Inactive configuration cannot generate new serials.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Admin سيناريو Edit Serial Configuration with Usage Constraints ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Prefix, reset type, and number of zeros can be edited only if no serial has been generated, unless the admin correction policy allows future-only changes.
ERP_SRS acceptance test: Generated serials already assigned to records must not be changed by updating configuration.
ERP_SRS acceptance test: Changing configuration after usage must affect only future generated serials and must be logged in the audit trail.
ERP_SRS acceptance test: Inactive configuration cannot generate new serials.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want to view serial configuration details and preview, so that I can verify how the next serial will look before using it.

Serial Number Configuration

SerialConfig-View-002Canonical SRS Graph

As an Admin, I want to view serial configuration details and preview, so that I can verify how the next serial will look before using it.

User Story

As an Admin, I want to view serial configuration details and preview, so that I can verify how the next serial will look before using it.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to view serial configuration details and preview, so that I can verify how the next serial will look before using it.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to view serial configuration details and preview, so that I can verify how the next serial will look before using it.

Acceptance Criteria

Display module, model, prefix, reset type, year/month behavior, number of zeros, current sequence, next sequence, and generated preview.
The preview must update when configuration values change before saving.
Example without monthly reset: INV-2026-0001.
Example with monthly reset: INV-2026-05-0001, and the next month starts again from 0001.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Title or Statement	Text 3..250	Yes	3–250 sanitized characters
Record Owner	User Reference	Yes	Active user with access to record scope
Effective Date	Date	No	In an allowed period without conflicting active records

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Admin سيناريو View Serial Configuration Details and Generated Preview ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Display module, model, prefix, reset type, year/month behavior, number of zeros, current sequence, next sequence, and generated preview.
ERP_SRS acceptance test: The preview must update when configuration values change before saving.
ERP_SRS acceptance test: Example without monthly reset: INV-2026-0001.
ERP_SRS acceptance test: Example with monthly reset: INV-2026-05-0001, and the next month starts again from 0001.

Alternative Path

—

Edge Cases

—

QPENTASCOPE

جاري تجهيز مساحة العمل

بنحمّل الواجهة والبيانات المطلوبة فقط.

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Title or Statement

Text 3..250

Yes

3–250 sanitized characters

Record Owner

User Reference

Yes

Active user with access to record scope

Effective Date

Date

In an allowed period without conflicting active records