عرض Word للـUser Stories

SAME DOCUMENT LAYOUT

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

HR Reference Data

HRReferenceData-Seeders-007Canonical SRS Graph

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

User Story

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

طبقًا للمصدر الأساسي ERP_SRS: As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

Description

Acceptance Criteria

Unit Type and Effect Type must have seeders.
These records already exist as system models and are used by both Request Type and Rule Configuration.
End users must not be able to create, edit or delete seeded values from the UI.
All dropdowns/selects using these models must support searchable UX.
Effect Type list must remove: edit time doctor, advanced payment and purchase.

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
Employee	Employee Reference	Yes	Active and in user scope; sensitive fields require field permission
Request Type	Reference	Yes	Active and applicable to role, country and contract
Effective Date	Date	Yes	Must respect allowed backdate and locked periods
Employee Notes	Text 0..2000	No	Maximum 2,000 characters with sanitization

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System Admin سيناريو Seed Unit Type and Effect Type ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Unit Type and Effect Type must have seeders.
ERP_SRS acceptance test: These records already exist as system models and are used by both Request Type and Rule Configuration.
ERP_SRS acceptance test: End users must not be able to create, edit or delete seeded values from the UI.
ERP_SRS acceptance test: All dropdowns/selects using these models must support searchable UX.
ERP_SRS acceptance test: Effect Type list must remove: edit time doctor, advanced payment and purchase.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

HR Reference Data

HRReferenceData-Seeders-007Canonical SRS Graph

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

User Story

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

Description

Acceptance Criteria

Unit Type and Effect Type must have seeders.
These records already exist as system models and are used by both Request Type and Rule Configuration.
End users must not be able to create, edit or delete seeded values from the UI.
All dropdowns/selects using these models must support searchable UX.
Effect Type list must remove: edit time doctor, advanced payment and purchase.

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
Employee	Employee Reference	Yes	Active and in user scope; sensitive fields require field permission
Request Type	Reference	Yes	Active and applicable to role, country and contract
Effective Date	Date	Yes	Must respect allowed backdate and locked periods
Employee Notes	Text 0..2000	No	Maximum 2,000 characters with sanitization

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System Admin سيناريو Seed Unit Type and Effect Type ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Unit Type and Effect Type must have seeders.
ERP_SRS acceptance test: These records already exist as system models and are used by both Request Type and Rule Configuration.
ERP_SRS acceptance test: End users must not be able to create, edit or delete seeded values from the UI.
ERP_SRS acceptance test: All dropdowns/selects using these models must support searchable UX.
ERP_SRS acceptance test: Effect Type list must remove: edit time doctor, advanced payment and purchase.

Alternative Path

—

Edge Cases

—

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

HR Reference Data

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.

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

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

HR Reference Data

As a System Admin, I want Unit Type and Effect Type to be seeded reference models, so that they are consistent across Rule Configuration and Request Type without allowing user CRUD.