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 · كل القصص في صفحة واحدة

Validation Rules Library

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

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

As an HR Admin, I want to create reusable validation rules, so that request submissions can be validated consistently based on business conditions.

Validation Rules Library

ValidationRule-Create-002Canonical SRS Graph

As an HR Admin, I want to create reusable validation rules, so that request submissions can be validated consistently based on business conditions.

User Story

As an HR Admin, I want to create reusable validation rules, so that request submissions can be validated consistently based on business conditions.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to create reusable validation rules, so that request submissions can be validated consistently based on business conditions.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to create reusable validation rules, so that request submissions can be validated consistently based on business conditions.

Acceptance Criteria

The system provides a Create Validation Rule page.
Rule Name EN and Rule Name AR are required.
Sequence is required and controls display/order priority in the validation rules list.
Status is required and defaults to Active.
Message EN and Message AR are required to show clear localized validation messages when the rule fails.
The system must support a Conditions Builder section.
At least one condition is required.
The HR Admin can combine conditions using AND or OR.
If Combine Conditions With = AND, all conditions must be satisfied for the validation rule to be applied.
If Combine Conditions With = OR, at least one condition must be satisfied for the validation rule to be applied.
Each condition must compare a request field against a reference value.
The condition can compare against a fixed value, today’s date, another value in the request, or a shifted reference value.

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

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

Scenarios

ERP_SRS acceptance test: The system provides a Create Validation Rule page.
ERP_SRS acceptance test: Rule Name EN and Rule Name AR are required.
ERP_SRS acceptance test: Sequence is required and controls display/order priority in the validation rules list.
ERP_SRS acceptance test: Status is required and defaults to Active.
ERP_SRS acceptance test: Message EN and Message AR are required to show clear localized validation messages when the rule fails.
ERP_SRS acceptance test: The system must support a Conditions Builder section.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an HR Admin, I want to delete unused validation rules, so that the validation rules library remains clean.

Validation Rules Library

ValidationRule-Delete-006Canonical SRS Graph

As an HR Admin, I want to delete unused validation rules, so that the validation rules library remains clean.

User Story

As an HR Admin, I want to delete unused validation rules, so that the validation rules library remains clean.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to delete unused validation rules, so that the validation rules library remains clean.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to delete unused validation rules, so that the validation rules library remains clean.

Acceptance Criteria

Delete is allowed only if the validation rule is not linked to any request type and has not been used in request history.
If the validation rule is linked to request types, delete must be blocked and deactivation must be recommended.
If the validation rule has historical usage, delete must be blocked to preserve audit traceability.
The system must show a clear message explaining why deletion is blocked.

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

ينفذ HR Admin سيناريو Delete Validation Rule ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Delete is allowed only if the validation rule is not linked to any request type and has not been used in request history.
ERP_SRS acceptance test: If the validation rule is linked to request types, delete must be blocked and deactivation must be recommended.
ERP_SRS acceptance test: If the validation rule has historical usage, delete must be blocked to preserve audit traceability.
ERP_SRS acceptance test: The system must show a clear message explaining why deletion is blocked.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an HR Admin, I want to view the validation rules library, so that I can manage reusable business validation rules and understand which request types are using each rule.

Validation Rules Library

ValidationRule-List-001Canonical SRS Graph

As an HR Admin, I want to view the validation rules library, so that I can manage reusable business validation rules and understand which request types are using each rule.

User Story

As an HR Admin, I want to view the validation rules library, so that I can manage reusable business validation rules and understand which request types are using each rule.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to view the validation rules library, so that I can manage reusable business validation rules and understand which request types are using each rule.

Description

Acceptance Criteria

The system displays a list of validation rules.
The list shows columns: Sequence, Rule Name, Message, Conditions Count, Linked Request Types Count, Status, and Actions.
The system displays active and inactive validation rules.
The system shows whether each validation rule is linked to one or more request types.
The Conditions column must show the number of configured conditions for each validation rule.
The Request Types column must show the number of request types linked to the validation rule.
Users can add a new validation rule from the Validation Rules Library page.
Each row must provide actions based on permissions, such as Edit, Activate/Deactivate, Show and Delete.
Delete must be blocked if the validation rule is linked to any request type or already used in request validation history.
If a validation rule is linked to request types, the system should allow deactivation instead of deletion.
Inactive validation rules must not be available for new request type configuration but must remain visible for history and audit.
Add pagination for page and add filter by Rule name and status

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

ينفذ HR Admin سيناريو View Validation Rules Library ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The system displays a list of validation rules.
ERP_SRS acceptance test: The list shows columns: Sequence, Rule Name, Message, Conditions Count, Linked Request Types Count, Status, and Actions.
ERP_SRS acceptance test: The system displays active and inactive validation rules.
ERP_SRS acceptance test: The system shows whether each validation rule is linked to one or more request types.
ERP_SRS acceptance test: The Conditions column must show the number of configured conditions for each validation rule.
ERP_SRS acceptance test: The Request Types column must show the number of request types linked to the validation rule.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an HR Admin, I want to activate or deactivate validation rules, so that I can control which rules are available for future request type configuration.

Validation Rules Library

ValidationRule-Status-005Canonical SRS Graph

As an HR Admin, I want to activate or deactivate validation rules, so that I can control which rules are available for future request type configuration.

User Story

As an HR Admin, I want to activate or deactivate validation rules, so that I can control which rules are available for future request type configuration.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to activate or deactivate validation rules, so that I can control which rules are available for future request type configuration.

Description

Acceptance Criteria

The system allows authorized users to activate or deactivate validation rules.
Inactive validation rules must not be available for new request type configuration.
Inactive validation rules must remain linked historically to old request snapshots and reports.
If a validation rule is linked to active request types, the system must warn the HR Admin before deactivation.
A reason is required when deactivating a validation rule.
Deactivation must not affect already submitted requests.
Status changes must be stored in the audit log.

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

ينفذ HR Admin سيناريو Activate / Deactivate Validation Rule ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The system allows authorized users to activate or deactivate validation rules.
ERP_SRS acceptance test: Inactive validation rules must not be available for new request type configuration.
ERP_SRS acceptance test: Inactive validation rules must remain linked historically to old request snapshots and reports.
ERP_SRS acceptance test: If a validation rule is linked to active request types, the system must warn the HR Admin before deactivation.
ERP_SRS acceptance test: A reason is required when deactivating a validation rule.
ERP_SRS acceptance test: Deactivation must not affect already submitted requests.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an HR Admin, I want to edit validation rules, so that I can correct rule details, messages, status, or condition logic safely.

Validation Rules Library

ValidationRule-Update-003Canonical SRS Graph

As an HR Admin, I want to edit validation rules, so that I can correct rule details, messages, status, or condition logic safely.

User Story

As an HR Admin, I want to edit validation rules, so that I can correct rule details, messages, status, or condition logic safely.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to edit validation rules, so that I can correct rule details, messages, status, or condition logic safely.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to edit validation rules, so that I can correct rule details, messages, status, or condition logic safely.

Acceptance Criteria

The system provides an Edit Validation Rule page.
The edit page displays the existing rule data.
Users can update Rule Name EN , Rule Name AR , Sequence, Status, Message EN, Message AR, Combine Conditions With, and condition rows according to permissions.
If the validation rule is not linked to any request type and has not been used in request history, all fields can be edited.
If the validation rule is linked to request types or has been used in request validation history, changes that may affect old requests must not recalculate historical requests.
Existing requests must keep their original validation snapshot and must not be affected by updates to the validation rule.
Changes to the validation rule apply only to new requests after the edit date.
If changing condition logic may affect active or pending requests, the system must warn the HR Admin before saving.
The system must store old value, new value, changed by, changed date/time, and change reason in the audit log.
Change Reason is required when editing an active validation rule linked to request types.
Edit — 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

ينفذ HR Admin سيناريو Edit Validation Rule ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The system provides an Edit Validation Rule page.
ERP_SRS acceptance test: The edit page displays the existing rule data.
ERP_SRS acceptance test: Users can update Rule Name EN , Rule Name AR , Sequence, Status, Message EN, Message AR, Combine Conditions With, and condition rows according to permissions.
ERP_SRS acceptance test: If the validation rule is not linked to any request type and has not been used in request history, all fields can be edited.
ERP_SRS acceptance test: If the validation rule is linked to request types or has been used in request validation history, changes that may affect old requests must not recalculate historical requests.
ERP_SRS acceptance test: Existing requests must keep their original validation snapshot and must not be affected by updates to the validation rule.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an HR Admin, I want to view validation rule details, so that I can review its conditions, messages, linked request types, status, and audit history.

Validation Rules Library

ValidationRule-View-004Canonical SRS Graph

As an HR Admin, I want to view validation rule details, so that I can review its conditions, messages, linked request types, status, and audit history.

User Story

As an HR Admin, I want to view validation rule details, so that I can review its conditions, messages, linked request types, status, and audit history.

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to view validation rule details, so that I can review its conditions, messages, linked request types, status, and audit history.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, I want to view validation rule details, so that I can review its conditions, messages, linked request types, status, and audit history.

Acceptance Criteria

The system displays a validation rule details page.
The details page shows Rule Name EN, Rule Name AR, Sequence, Status, Message EN, Message AR, and Combine Conditions With.
The page shows all configured condition rows.
The page shows the readable condition summary for each condition.
The page shows the count of linked request types.
The page displays the list of linked request types if any exist.
The page shows audit/log history if audit tracking is enabled.
The details page is read-only unless the user has edit permission.
Show — 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

ينفذ HR Admin سيناريو Show Validation Rule Details (new) ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The system displays a validation rule details page.
ERP_SRS acceptance test: The details page shows Rule Name EN, Rule Name AR, Sequence, Status, Message EN, Message AR, and Combine Conditions With.
ERP_SRS acceptance test: The page shows all configured condition rows.
ERP_SRS acceptance test: The page shows the readable condition summary for each condition.
ERP_SRS acceptance test: The page shows the count of linked request types.
ERP_SRS acceptance test: The page displays the list of linked request types if any exist.

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