نفس مصدر الإدارات والموديولات والـWorkflows؛ يتم تحميل 20 قصة فقط في كل صفحة.
632 نتيجة من نفس الـSRS Graphصفحة 20 من 32الكتالوج الكامل 632 Story فريدة
HRRequestType-Seed-007
الموارد البشرية والإدارة · موديول Request TypesHR إضافي موجود بالنظام
بصفتي مسؤول النظام، أريد تنفيذ المتطلب التشغيلي في موديول Request Types، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: System Admin
طبقًا للمصدر الأساسي ERP_SRS: As a System Admin, I want RequestTypesWithPoliciesSeeder to seed types and wire leave entitlements, so that HRM installs match Egyptian Labour Law.
As a System Admin, I want RequestTypesWithPoliciesSeeder to seed types and wire leave entitlements, so that HRM installs match Egyptian Labour Law.
Acceptance Criteria (4)
Runs after PolicyAndRulesSeeder in DatabaseSeeder.
Idempotent; rules resolved by name in applyLeavePoliciesAndBalances().
HREmployeeRequest-Validation-017
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد إنشاء سجل جديد في طلبات الموظفين بعد التحقق من البيانات والقواعد، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
طبقًا للمصدر الأساسي ERP_SRS: As an Employee, I want to create a request from the visible active request types, so that the system can render the correct fields, apply configured validation rules, calculate duration and balance, route approvals through the report line, and notify the correct users.
As an Employee, I want to create a request from the visible active request types, so that the system can render the correct fields, apply configured validation rules, calculate duration and balance, route approvals through the report line, and notify the correct users.
Acceptance Criteria (12)
Employees can select Department and Request Type from searchable selects.
Only active and visible request types appear to the employee according to Request Type visibility, Visible For Departments.
The system renders fields dynamically based on the selected Request Type configuration, such as Start Date, End Date, Start Time, End Time, Back to Work Date, Wanted, Number of Days, Description, Reason, Attachment, Location, Event Type, Position, and any configured dynamic fields. (new)
Description and Reason must be treated as separate fields when both are configured. Description is used for general request details, while Reason is used as the business justification for submission, approval, exception handling, or reporting. (new)
Description and Reason visibility and required behavior must be controlled by Request Type configuration. If only one field is needed, the other field must be hidden. (new)
Wanted and Number of Days must not appear together on the Employee Create Request form. (new)
The employee must see only one duration input based on the Request Type configuration: either Wanted or Number of Days. (new)
If the Request Type configuration contains both Wanted and Number of Days , the system must block request creation and show a clear configuration error until the Request Type is corrected. (new)
Balance, Remaining Balance, Used Balance, Balance Type and Expected fields are read-only for the employee and are calculated/predefined automatically when the selected Request Type has balance rules. (new)
For non-balance-based Request Types, such as No Balance or Unlimited balance mode, balance fields must be hidden or shown as Not Applicable and balance validation must be skipped. (new)
The system validates mandatory fields before save or submit and displays a clear validation message when missing.
Runtime validation must follow HREmployeeRequest-Validation-017: Apply Runtime Validation Rules Alignment for Create Request. (new)
HREmployeeRequest-Validate-002
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد تنفيذ المتطلب التشغيلي في طلبات الموظفين، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: System
طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to validate employee request data against configured rules, so that invalid requests are blocked or routed to exception handling.
As a System, I want to validate employee request data against configured rules, so that invalid requests are blocked or routed to exception handling.
Acceptance Criteria (12)
This user story defines validation rule configuration only and must not duplicate the create or modify request flow. (new)
Validation execution must be handled inside the relevant request actions such as Create Request and Modify Request. (new)
HR Admin can link one or more Validation Rules to a Request Type Rule. (new)
Each Validation Rule must define the validation type, trigger point, condition, error message, and system behavior when validation fails. (new)
Validation Rules can be configured for required fields, date range, duration, balance, frequency, overlap, required documents, eligibility, advance submission, past date allowance, future date allowance, and payroll impact preview. (new)
Each Validation Rule can define whether the failed validation blocks submission, shows a warning, or allows an exception option. (new)
Each Validation Rule must support English and Arabic error messages. (new)
The system must use the configured validation message instead of showing generic blocking messages. (new)
The system must allow configuring how many days before the Start Date a request can be submitted, when applicable. (new)
The system must allow configuring whether past-dated requests are allowed for each Request Type Rule. (new)
The system must configure whether future-dated requests are allowed and the maximum allowed future submission period, when applicable. (new)
The system must allow configuring whether the Number of Days / Hours is calculated from dates/times, entered manually, or validated against the selected date/time range. (new)
HREmployeeRequest-Exception-003
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد تنفيذ المتطلب التشغيلي في طلبات الموظفين، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
طبقًا للمصدر الأساسي ERP_SRS: As an Employee, I want to select an available exception option when my request violates a rule, so that the request can continue according to company policy.
As an Employee, I want to select an available exception option when my request violates a rule, so that the request can continue according to company policy.
Acceptance Criteria (4)
Exception options appear only when the failed rule allows exceptions.
Employees must provide reason and attachment if required by exception configuration.
Selected exceptions are stored on the request and routed to the configured approval cycle.
Unpaid Leave option may appear when Annual, Sick, Maternity or similar leave has insufficient balance and the rule allows conversion.
HREmployeeRequest-List-004
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد عرض ومتابعة سجلات طلبات الموظفين مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
طبقًا للمصدر الأساسي ERP_SRS: As an Employee, I want to view my submitted requests, so that I can track status and next action.
As an Employee, I want to view my submitted requests, so that I can track status and next action.
Acceptance Criteria (12)
Employees can view only their own submitted requests.
Employees can search/filter by request number, request type, status, and date range.
List shows Request Number, Request Type, Dates, Status, Current Approver/Next Action and Created Date.
Status changes are reflected on the user home/request page after approver actions.
Pagination and searchable filters are supported.
The list shows a summary of each request including Request Number, Request Type, Dates, Status, Current Approver, and Created Date.
The system displays 25 requests per page by default before applying pagination. (new)
Pagination controls must be available when the number of requests exceeds the default page size. (new)
If page size configuration is supported, the user can change the number of displayed records per page according to system configuration. (new)
Each request row must provide a Show / View Details action. (new)
The request details page must display all request information, not only the summary columns shown in the list. (new)
Request details must be displayed dynamically based on the selected Request Type configuration. (new)
HREmployeeRequest-Details-005
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد عرض ومتابعة سجلات طلبات الموظفين مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee or authorized user
طبقًا للمصدر الأساسي ERP_SRS: As an Employee or authorized user, I want to view request details, so that I can understand submitted data, approvals, comments, status changes, notifications and payroll impact.
As an Employee or authorized user, I want to view request details, so that I can understand submitted data, approvals, comments, status changes, notifications and payroll impact.
Acceptance Criteria (12)
The details page shows all submitted fields and read-only calculated values.
The details page must display request basic information such as request number, employee, department, request type, current status, created date, submitted date, and request dates. (new)
The details page must display request-specific fields dynamically based on the selected Request Type configuration. (new)
Timeline shows request creation, validation, direct manager action, approval users actions, status changes, email and notification events.
Timeline must show action performer, performer role, action type, decision, comment/reason, old status, new status, and action date/time when available. (new)
Attachments are visible according to permission.
Attachments must be viewable/downloadable only by users who have permission to access the request details. (new)
Payroll impact preview appears only for request types with payroll effect.
Payroll Impact section appears only when the Request Type has payroll impact enabled or when the request creates a salary, deduction, unpaid, allowance, or payroll-related effect. (new)
Payroll Effect means any request impact that may affect salary calculation, payroll processing, paid days, unpaid days, deductions, allowances, or working hours. (new)
Examples of requests with payroll effect include Leave Without Pay, Leave Salary Deduction, Permission affecting working hours, unpaid Sick Leave, unpaid Maternity Leave, or any request type configured to affect payroll. (new)
If the request has payroll effect, the details page must show the payroll impact preview or applied payroll impact according to user permissions. (new)
HREmployeeRequest-Cancel-006
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد تنفيذ المتطلب التشغيلي في طلبات الموظفين، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
طبقًا للمصدر الأساسي ERP_SRS: As an Employee, I want to cancel an eligible request, so that I can withdraw it before final closure.
As an Employee, I want to cancel an eligible request, so that I can withdraw it before final closure.
Acceptance Criteria (4)
Only configured statuses can be cancelled.
A cancellation reason is required.
Reserved or pending balance must be restored if applicable.
Requester, direct manager, approval users and configured notification recipients receive status update notification/email.
HREmployeeRequest-Modify-007
الموارد البشرية والإدارة · طلبات الموظفينHR إضافي موجود بالنظام
بصفتي الموظف، أريد تعديل بيانات طلبات الموظفين مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
طبقًا للمصدر الأساسي ERP_SRS: As an Employee, I want to modify allowed request fields before final approval, so that I can correct request data without creating a new request.
As an Employee, I want to modify allowed request fields before final approval, so that I can correct request data without creating a new request.
Acceptance Criteria (12)
Only editable fields configured for the request type can be modified.
Modified request is revalidated against the active rule snapshot stored on the request.
Modification is required and stored in the audit log.
An employee can modify his/her request only when request status is Pending. (new)
Employees cannot modify the request if the status is Closed, Rejected, Cancelled, Final Approved, or if payroll/balance impact has already been processed. (new)
Editable fields must be clearly defined per request type configuration. (new)
Default editable fields may include request dates, number of days/hours, reason, notes, attachments, replacement employee, contact information, or request-specific fields configured as editable. (new)
Non-editable fields must include employee, request type, request number, current status, approval cycle, current approver, rule snapshot, payroll impact, and balance impact. (new)
If the modification affects dates, duration, balance, payroll impact, replacement employee, or approval routing, the system must revalidate the request and recalculate the affected values. (new)
Every modification must be stored in the request Action History / Timeline with old values, new values, modifier, modification date/time, and reason. (new)
Approvers and configured recipients are notified when modification changes routing or status.
If the request was not approved by any approver yet, the request remains Pending and follows the normal approval flow after modification. (new)
HRAdminRequest-List-008
الموارد البشرية والإدارة · طلبات إدارة الموارد البشريةHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد عرض ومتابعة سجلات طلبات إدارة الموارد البشرية مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Business / System User
طبقًا للمصدر الأساسي ERP_SRS: As an HR Admin, Admin or Manager, I want to view requests according to my permissions and report line responsibility, so that I can monitor and process employee requests.
As an HR Admin, Admin or Manager, I want to view requests according to my permissions and report line responsibility, so that I can monitor and process employee requests.
Acceptance Criteria (12)
Authorized users can view requests for departments/users they are allowed to manage.
List shows request number, employee, department, request type, status, current approver, submitted date and SLA/age if configured.
Filters must include employee, department, request type, status, date range and approval responsibility.
All dropdown filters must be searchable.
The system must clearly apply different request visibility rules for HR Admin, Admin, and Manager roles. (new)
HR Admin can view employee requests based on HR permissions, assigned departments, scope configuration. (new)
Admin can view requests based on system-level permissions. (new)
Managers can view only requests where the manager is responsible through Direct Manager hierarchy, report line responsibility, or current approval assignment. (new)
Managers visibility must not be based only on the department unless the manager is explicitly configured as responsible for that department/report line. (new)
If a user has more than one role, the system should combine allowed visibility based on the highest granted permissions without duplicating request records. (new)
The request list must display only actions allowed for the logged-in user role, permission, current request status, and approval responsibility. (new)
HR Admin actions may include view, monitor, change status, approve/reject if assigned, and process requests based on permissions. (new)
HRAdminRequest-Details-009
الموارد البشرية والإدارة · طلبات إدارة الموارد البشريةHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد عرض ومتابعة سجلات طلبات إدارة الموارد البشرية مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Business / System User
طبقًا للمصدر الأساسي ERP_SRS: As an Admin, HR Admin or Manager, I want to view full request details, so that I can approve, reject, change status or audit the request.
As an Admin, HR Admin or Manager, I want to view full request details, so that I can approve, reject, change status or audit the request.
Acceptance Criteria (4)
Authorized users can open request details from the list.
The details page shows employee data, request fields, balance calculation, exception selected, approval cycle, comments and attachments.
Available actions depend on current user role and current request status.
The system shows report line routing details: Direct Manager active flag, approval users and departments.
HRAdminRequest-ApproveReject-010
الموارد البشرية والإدارة · طلبات إدارة الموارد البشريةHR إضافي موجود بالنظام
بصفتي المدير المسؤول، أريد مراجعة واعتماد أو رفض العملية في طلبات إدارة الموارد البشرية حسب الصلاحية، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: assigned Direct Manager or Approval User
طبقًا للمصدر الأساسي ERP_SRS: As an assigned Direct Manager or Approval User, I want to approve or reject a request, so that the request can move through the approval cycle.
As an assigned Direct Manager or Approval User, I want to approve or reject a request, so that the request can move through the approval cycle.
Acceptance Criteria (12)
Only the current assigned approver can approve or reject.
If Active Direct Manager is enabled and an employee has an active direct manager, direct manager action happens before Approval Users.
If Active Direct Manager is disabled or the employee has no active direct manager, request is sent directly to Approval Users.
Reject requires comment if configured.
Final approval can deduct balance and create payroll impact if configured.
Requester and configured recipients receive notification/email after each approval decision.
The system must display available actions based on the logged-in user role, assigned approval step, permissions, and current request status. (new)
Each role must see only the actions allowed for that role and current request stage. (new)
If the logged-in user is not the current assigned approver, Approve and Reject actions must be hidden or disabled. (new)
Direct Manager can approve, reject, and add decision comments if you need to reject only when the request is assigned to the Direct Manager step. (new)
Approval User can approve, reject, and add decision comments if you need to reject when the request is assigned to that Approval User step. (new)
HR/Admin users can view request details and may change status or take administrative actions only if they have the required permissions and allowed transition rules. (new)
HRAdminRequest-ChangeStatus-011
الموارد البشرية والإدارة · طلبات إدارة الموارد البشريةHR إضافي موجود بالنظام
بصفتي المدير المسؤول، أريد تعديل بيانات طلبات إدارة الموارد البشرية مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: authorized HR/Admin/Manager user
طبقًا للمصدر الأساسي ERP_SRS: As an authorized HR/Admin/Manager user, I want to change request status according to allowed transitions, so that requests can be tracked correctly.
As an authorized HR/Admin/Manager user, I want to change request status according to allowed transitions, so that requests can be tracked correctly.
Acceptance Criteria (12)
Users can change status only if permission and transition rules allow it.
Allowed statuses include New, Open, In Progress, Pending, Closed, Rejected and Cancelled based on seeded request statuses.
Changing status requires reason when configured.
Status update triggers notification and email to requester and configured users.
Status history is stored in the timeline/audit log.
The system must provide an Action
History / Timeline section on the request details page. (new)
When a Manager, HR, Admin, or any authorized user performs an action on the request, the action must be stored in the request history. (new)
Tracked actions must include change status, approve, reject, cancel, send back, reopen, add comment, or any workflow action configured for the request type. (new)
Each action history record must display the action performer name, performer role, action type, old status, new status, action date/time, and reason/comment if provided. (new)
When the action triggers notification or email, the history should indicate that notification/email was triggered or logged when applicable. (new)
Manager actions must be visible in the request timeline so that HR/Admin users can know which manager acted, when the action happened, and what decision was taken. (new)
HRRequestStatus-List-012
الموارد البشرية والإدارة · موديول Request StatusHR إضافي موجود بالنظام
بصفتي مسؤول النظام، أريد عرض ومتابعة سجلات موديول Request Status مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: authorized HR/Admin user
طبقًا للمصدر الأساسي ERP_SRS: As an authorized HR/Admin user, I want to view the predefined request statuses in a read-only reference screen, so that I can understand the request lifecycle and ensure that statuses are used consistently across requests, approvals, notifications, and reports.
As an authorized HR/Admin user, I want to view the predefined request statuses in a read-only reference screen, so that I can understand the request lifecycle and ensure that statuses are used consistently across requests, approvals, notifications, and reports.
Acceptance Criteria (12)
The system must provide a Request Statuses screen to display all predefined request statuses. (new)
Request statuses are system/reference data and users cannot create, edit, or delete them from this screen.
The Request Statuses screen must be read-only for all users. (new)
Only System Admin/Seeder controls available statuses in the database.
Authorized users can view status names in English and Arabic. (new)
Statuses must be used consistently across Employee Requests, Admin Requests, Approval Cycle, Notifications, Reports, and Audit Trail.
The screen must allow users to search by status name. (new)
The list must be sorted based on Sort Order by default. (new)
Final statuses close the request lifecycle and prevent normal workflow actions unless special permission or allowed transition rules exist. (new)
If a status is used in requests, approvals, notifications, or reports, it must remain available for historical records. (new)
Status labels must support English and Arabic display. (new)
Request Status Examples (new)
HRRequestCycle-Approval-013
الموارد البشرية والإدارة · موديول Request Approval CycleHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد مراجعة واعتماد أو رفض العملية في موديول Request Approval Cycle حسب الصلاحية، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: System
طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to route requests based on Default Report Line configuration, so that approval users and direct manager logic are applied dynamically.
As a System, I want to route requests based on Default Report Line configuration, so that approval users and direct manager logic are applied dynamically.
Acceptance Criteria (8)
System loads matching Report Line using Entity = Request Type, Filter Data = Department and Data = selected Request Type.
System checks All Departments/Departments to confirm the requester can create the selected request type.
If Active Direct Manager = Yes and the requester has an active direct manager, the request first goes to the direct manager.
After direct manager approval, the request moves to configured Approval Users in the Report Line.
If Active Direct Manager = No, request goes directly to configured Approval Users.
If the requester has no active direct manager while Active Direct Manager = Yes, request goes directly to Approval Users.
Approval cycle changes status and stores routing history in request timeline.
Can Review this user story : ReportLine-DirectManager-008 ReportLine-RequestType-010
HRRequestCycle-DirectManagerHierarchy-014
الموارد البشرية والإدارة · موديول Request Approval CycleHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد تنفيذ المتطلب التشغيلي في موديول Request Approval Cycle، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: System
طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to route employee requests through the Direct Manager hierarchy based on the defined reporting structure, so that requests are validated by the employee’s Direct Manager and then by the next managers in the hierarchy when configured.
As a System, I want to route employee requests through the Direct Manager hierarchy based on the defined reporting structure, so that requests are validated by the employee’s Direct Manager and then by the next managers in the hierarchy when configured.
Acceptance Criteria (12)
This story applies to employee requests where the matched Default Report Line has Entity = Request Type.
The system must not validate, route, notify, or approve requests based on the Department Head.
The approval flow must be based only on the Direct Manager hierarchy defined in the employee reporting structure.
When the request is created, the system resolves the employee’s active Direct Manager.
If the employee has an active Direct Manager, the request is routed first to that Direct Manager.
If multi-level manager approval is configured, the request is routed next to the Direct Manager of the previous Direct Manager, and continues upward according to the configured reporting hierarchy.
Example: If User Ali reports to Mostafa, and Mostafa reports to Ahmed, then the approval flow should be Ali request → Mostafa approval → Ahmed approval, if the report line requires two manager levels.
If the employee has no active Direct Manager and no fallback Approval User is configured, the system must return a clear validation message or route according to the configured fallback rule.
If the employee has no active Direct Manager but Approval Users are configured, the request is routed directly to the configured Approval Users according to the report line setup.
Only the current assigned approver in the Direct Manager hierarchy can approve or reject the request at the current approval step.
A higher manager cannot approve before the lower manager step unless the report line configuration explicitly allows skipping levels.
Once a manager approves the request, the system moves the request to the next configured Direct Manager hierarchy level or to the next Approval User step.
HRRequestNotification-Create-015
الموارد البشرية والإدارة · إشعارات الطلباتHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد إنشاء سجل جديد في إشعارات الطلبات بعد التحقق من البيانات والقواعد، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: System
طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to send notifications and emails when a request is created, so that requester, approvers and configured users are informed immediately.
As a System, I want to send notifications and emails when a request is created, so that requester, approvers and configured users are informed immediately.
Acceptance Criteria (5)
On request creation, the system sends notification/email to requesters confirming submission.
System sends notification/email to Direct Manager if Active Direct Manager applies.
The system sends notification/email to Report Line Approval Users when the request reaches their step.
The system also sends notification/email to any additional users configured in notification settings/report line if applicable.
Notification content must include Request Number, Request Type, Employee, Status, Current Step and Action Link.
HRRequestNotification-Status-016
الموارد البشرية والإدارة · إشعارات الطلباتHR إضافي موجود بالنظام
بصفتي مستخدم الأعمال، أريد تعديل بيانات إشعارات الطلبات مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: System
طبقًا للمصدر الأساسي ERP_SRS: As a System, I want to send notifications and emails whenever request status changes, so that requester and responsible users know the latest action.
As a System, I want to send notifications and emails whenever request status changes, so that requester and responsible users know the latest action.
Acceptance Criteria (5)
Requester receives notification/email when request status changes to In Progress, Pending, Closed, Rejected or Cancelled.
Configured recipients receive notification/email when they are required to take action.
Approvers receive notification/email after previous step approval if the request is routed to them.
The notification event is stored in the request timeline/audit log.
Failed email sending should not block status update but must be logged for retry/diagnosis.
ValidationRule-List-001
المنصة والحوكمة · مكتبة قواعد التحقق
بصفتي مسؤول النظام، أريد عرض ومتابعة سجلات مكتبة قواعد التحقق مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: قواعد التحقق
فتح سريع للقصة
Actor: HR Admin
طبقًا للمصدر الأساسي 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.
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.
Acceptance Criteria (12)
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
ValidationRule-Create-002
المنصة والحوكمة · مكتبة قواعد التحقق
بصفتي مسؤول النظام، أريد إنشاء سجل جديد في مكتبة قواعد التحقق بعد التحقق من البيانات والقواعد، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: قواعد التحقق
فتح سريع للقصة
Actor: HR Admin
طبقًا للمصدر الأساسي 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.
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 (12)
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.
ValidationRule-Update-003
المنصة والحوكمة · مكتبة قواعد التحقق
بصفتي مسؤول النظام، أريد تعديل بيانات مكتبة قواعد التحقق مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: قواعد التحقق
فتح سريع للقصة
Actor: HR Admin
طبقًا للمصدر الأساسي 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.
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 (11)
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.