BUILDING / USER MANUALبيلدينغ / دليل المستخدم
A CLEARER WAY TO WORKطريقة أوضح للعمل

Your workspace. Explained.مساحة عملك. بكل وضوح.

A practical guide to the React end-user workspace. Odoo pages are clearly marked as internal QA/admin evidence; ordinary users should work in React.دليل عملي لمساحة React المخصصة للمستخدم. شاشات Odoo موضّحة كأدلة اختبار أو إدارة داخلية؛ يستخدم العملاء React في أعمالهم اليومية.

Open local workspace ↗افتح مساحة العمل المحلية ↗
VERIFIED PROJECT PROGRESSنسبة إنجاز المشروع المتحقق منها

95.1%

156 of 164 stories are fully verified. 1 are partial, 0 missing and 7 blocked.اكتمل التحقق من 156 قصة من أصل 164. هناك 1 قصة جزئية و0 مفقودة و7 متوقفة.

Updated 2026-11-17. Partial work is not counted as completed. This percentage measures the original164stories; additional market features have a separate backlog.آخر تحديث 2026-11-17. لا يحتسب العمل الجزئي ضمن المكتمل. تقيس النسبة القصص الأصلية الـ164؛ لميزات السوق الإضافية قائمة عمل منفصلة.

16React workspacesمساحات React
410Embedded screenshotsلقطات شاشة مضمّنة
156/164 · 95.1%Verified DONE storiesقصص مكتملة تم التحقق منها
AR / ENTwo languages. One guide.لغتان. ودليل واحد.
Product direction: users work in React. React images include preview, watermarked synthetic examples and isolated live QA captures; native Odoo images are authorized internal QA/admin evidence from an isolated database. They are not proof of live AI output, tenant isolation, Saudi invoicing approval, or completion of the entire requirements backlog.اتجاه المنتج: يستخدم العملاء React. صور React تشمل المعاينة وأمثلة اصطناعية موسومة ولقطات اختبار فعلي معزولة؛ صور Odoo دليل اختبار أو إدارة داخلية مصرح به من قاعدة معزولة. ليست دليلاً على نتائج نموذج فعلية أو عزل المستأجرين أو اعتماد الفوترة السعودية أو اكتمال المتطلبات كلها.
USER GUIDEدليل المستخدم / 01

Start with your workspaceابدأ بمساحة عملك

Use your own Odoo account to work with live records. Design preview lets you explore the interface with sample data.استخدم حسابك في Odoo للعمل على السجلات الفعلية. تتيح معاينة التصميم استكشاف الواجهة ببيانات تجريبية.

  1. Open the React workspace at the same website address as this manual. On the demo PC, it is http://127.0.0.1:3200.افتح مساحة React على عنوان الموقع نفسه الذي فُتح منه هذا الدليل. على جهاز العرض المحلي، العنوان هو http://127.0.0.1:3200.
  2. The connected React demo uses the namaa_ksa database by default and routes Odoo requests to the Namaa Odoo service. If your administrator gives you another supported database, enter it explicitly.يستخدم عرض React المتصل قاعدة namaa_ksa افتراضياً ويوجّه طلبات Odoo إلى خدمة Odoo الخاصة بنماء. إذا زوّدك المسؤول بقاعدة أخرى مدعومة، فأدخل اسمها صراحة.
  3. The interface starts in Arabic. Choose English in the top toolbar if preferred.تبدأ الواجهة بالعربية. اختر English من الشريط العلوي إذا رغبت.
  4. Enter the database supplied by your administrator, your username and password, then choose Sign in to workspace.أدخل قاعدة البيانات التي يحددها المسؤول واسم المستخدم وكلمة المرور، ثم اختر الدخول إلى مساحة العمل.
  5. For the walkthrough, choose Explore design preview. The preview label stays visible; it does not use your company’s records.للاستعراض اختر استكشف التصميم التجريبي. تظل علامة المعاينة ظاهرة، ولا تُستخدم سجلات شركتك.
  6. Sign out from the user area at the bottom of the side navigation.سجّل الخروج من منطقة المستخدم أسفل القائمة الجانبية.
Your account permissions still apply. A hidden menu item is an appearance preference, not a permission change.تظل صلاحيات حسابك سارية. إخفاء عنصر من القائمة تفضيل للمظهر ولا يغيّر الصلاحيات.
USER GUIDEدليل المستخدم / 03

Read the business overviewاقرأ لوحة التحكم

Start with the four cards: confirmed sales, opportunity pipeline, purchase commitments and outstanding receivables.ابدأ بالبطاقات الأربع: المبيعات المؤكدة وقيمة الفرص البيعية والتزامات الشراء ومستحقات العملاء.

  1. In live mode, the cards use the totals available to your account in the current SAR company. Preview values are sample figures.في الوضع الفعلي تستخدم البطاقات الإجماليات المتاحة لحسابك في الشركة الحالية بالريال. قيم المعاينة تجريبية.
  2. Sales bars rank customers in the loaded confirmed SAR orders. The chart is not a historical trend or growth forecast.ترتّب أشرطة المبيعات العملاء حسب الطلبات المؤكدة المحمّلة بالريال. ليست مخططاً تاريخياً أو توقعاً للنمو.
  3. Pipeline pulse shows counts by the returned opportunity stages. Stage names come from your records.يعرض نبض الفرص البيعية أعداد الفرص حسب المراحل التي تُرجعها سجلاتك.
  4. Open a recent order or use the department shortcuts. Refresh in live mode to request current records.افتح طلباً حديثاً أو استخدم اختصارات الأقسام. حدّث في الوضع الفعلي لطلب السجلات الحالية.
Different cards and charts may cover different record windows: do not interpret recent-record charts as all-company history.قد تغطي البطاقات والمخططات نطاقات مختلفة من السجلات؛ لا تعتبر مخطط السجلات الحديثة تاريخ الشركة كاملاً.
USER GUIDEدليل المستخدم / 04

Manage customer opportunitiesأدر الفرص البيعية

The CRM register keeps a readable view of opportunities, customers, expected revenue and configured stages.يوفر سجل العملاء عرضاً واضحاً للفرص والعملاء والإيراد المتوقع والمراحل المعدّة.

  1. Choose CRM. Search by opportunity, partner or business reference, or filter by a stage.اختر إدارة العملاء. ابحث بالفرصة أو الشريك أو مرجع الأعمال، أو صفّ حسب المرحلة.
  2. Choose New opportunity. Select a partner, enter the opportunity name and expected revenue, optionally add a reference, and classify the client as government or private when known.اختر فرصة جديدة. حدّد الشريك وأدخل اسم الفرصة والإيراد المتوقع، وأضف مرجعاً وصنّف العميل حكومياً أو خاصاً عند توفر المعلومة.
  3. In live mode, Find another partner searches the available customer/vendor list. Correct highlighted fields before saving.في الوضع الفعلي يتيح البحث عن شريك آخر البحث في قائمة العملاء والموردين المتاحة. صحّح الحقول الموضحة قبل الحفظ.
  4. For construction lead matching, enter company-defined trade and tender-category codes one per line. Scouting compares them case-insensitively with the active company mandate. These internal codes do not connect an official tender feed.لمطابقة العملاء المحتملين في قطاع البناء، أدخل رموز التخصصات وفئات المناقصات التي تحددها الشركة، رمزاً في كل سطر. تقارنها شاشة الاستكشاف مع تفويض الشركة النشطة دون تمييز حالة الأحرف. هذه الرموز الداخلية لا تتصل بمصدر مناقصات رسمي.
  5. Open a record to review its details. Edit record preserves the document revision; reopen it if Odoo reports a stale change.افتح السجل لمراجعة تفاصيله. يحافظ تعديل السجل على رمز المراجعة؛ أعد فتحه إذا أبلغ Odoo عن تغيير سابق.
  6. Delete first opens a review. Keep record cancels; Delete record sends the deletion only after your decision.يفتح حذف مراجعة أولاً. يلغي الاحتفاظ بالسجل الإجراء، ولا يُرسل الحذف إلا بعد اختيار حذف السجل.
This screen creates opportunities. It does not implement automatic lead qualification, tender discovery or won-to-project acceptance.تنشئ هذه الشاشة فرصاً بيعية. لا تنفّذ تأهيلاً آلياً للعملاء أو اكتشاف المناقصات أو قبول تحويل الفرصة إلى مشروع.
USER GUIDEدليل المستخدم / 05

Prepare quotations and sales ordersجهّز عروض الأسعار وطلبات البيع

A quotation starts as a draft. Review the partner and product lines before confirming an order.يبدأ عرض السعر كمسودة. راجع الشريك وبنود المنتجات قبل تأكيد الطلب.

  1. Open Sales and choose New document. Select the customer and add product lines.افتح المبيعات واختر مستنداً جديداً. حدّد العميل وأضف بنود المنتجات.
  2. Enter quantities. Leave a quotation price blank to use configured Odoo pricing, or enter an explicit price including zero if intended.أدخل الكميات. اترك سعر عرض السعر فارغاً لاستخدام تسعير Odoo المُعدّ، أو أدخل سعراً صريحاً بما فيه الصفر إذا كان مقصوداً.
  3. Use Add product line or remove an unneeded line. The editor supports 1–100 ordinary lines.استخدم إضافة بند منتج أو احذف البند غير المطلوب. يدعم المحرر من بند واحد إلى ١٠٠ بند عادي.
  4. The estimated subtotal is before taxes. Save the draft and inspect the authoritative Odoo totals and tax before confirmation.الإجمالي التقديري قبل الضرائب. احفظ المسودة وافحص إجماليات Odoo والضريبة قبل التأكيد.
  5. In live mode, open the draft and choose Review confirmation. Confirm order is the separate final action. Sent quotations can still be reviewed for confirmation.في الوضع الفعلي افتح المسودة واختر مراجعة التأكيد. تأكيد الطلب هو الإجراء النهائي المنفصل. يمكن مراجعة عروض الأسعار المرسلة للتأكيد أيضاً.
Confirmed orders are read-only in this editor. Use the appropriate native Odoo cancellation/reversal flow when needed.الطلبات المؤكدة للقراءة فقط في هذا المحرر. استخدم إجراء الإلغاء أو العكس المناسب في Odoo عند الحاجة.
USER GUIDEدليل المستخدم / 06

Review RFQs and purchasingراجع طلبات التسعير والمشتريات

The purchasing workspace uses the same draft editor and explicit review pattern as sales.تستخدم مساحة المشتريات محرر المسودات ونمط المراجعة الصريحة نفسه المستخدم في المبيعات.

  1. Choose Purchase. Filter draft/sent, confirmed or cancelled documents and search vendors or references.اختر المشتريات. صفّ المسودات والمُرسلة أو المؤكدة أو الملغاة، وابحث بالمورد أو المرجع.
  2. Choose New document, select a vendor, and enter the requested products and quantities.اختر مستنداً جديداً وحدّد المورد وأدخل المنتجات والكميات المطلوبة.
  3. Keep unspecified RFQ prices blank for native configured pricing. Inspect the saved result before commitment.اترك أسعار طلب التسعير غير المحددة فارغة لتسعير Odoo المُعدّ. افحص النتيجة المحفوظة قبل الالتزام.
  4. For material requests, open the Material requests tab. Create a draft with a required date, products, quantities, units and specifications; link confirmed BOQ material lines when available. The requester submits it and an authorized reviewer approves or rejects it.لطلبات المواد، افتح تبويب طلبات المواد. أنشئ مسودة بتاريخ الحاجة والمنتجات والكميات والوحدات والمواصفات، واربط بنود المواد من جدول كميات معتمد عند توفرها. يرسل مقدم الطلب المسودة ويعتمدها أو يرفضها مراجع مخوّل.
  5. After approval, choose Create RFQ, select an active supplier and create a draft quotation. React calls the native Odoo purchase-request wizard, which links the RFQ lines to the request and preserves BOQ/analytic allocation. Review prices and delivery terms in the RFQ before sending it.بعد الاعتماد، اختر إنشاء طلب عرض سعر وحدد مورداً نشطاً لإنشاء مسودة عرض. تستدعي React معالج طلبات الشراء الأصلي في Odoo، الذي يربط البنود بالطلب ويحافظ على توزيع جدول الكميات والتحليلات. راجع الأسعار وشروط التسليم في العرض قبل إرساله.
  6. Stock Managers open Site locations and choose New warehouse. Enter a unique name and 2–5 character short code, then choose native one-, two- or three-step receipt and delivery flows. Odoo creates the warehouse, stock locations, operation types and routes.يفتح مديرو المخزون مواقع المشاريع ثم يختارون مستودعاً جديداً. أدخل اسماً فريداً ورمزاً مختصراً من 2 إلى 5 أحرف، ثم اختر عمليات الاستلام والتسليم الأصلية بخطوة أو خطوتين أو ثلاث. ينشئ Odoo المستودع ومواقع المخزون وأنواع العمليات والمسارات.
  7. After warehouse creation, select Create site location, choose the project and the new warehouse Stock location, then enter the site store name. Odoo links the internal site location to that project; stock transfers remain a separate workflow.بعد إنشاء المستودع، اختر إنشاء موقع للمشروع وحدد المشروع وموقع المخزون التابع للمستودع الجديد ثم أدخل اسم مخزن الموقع. يربط Odoo موقع المخزون الداخلي بالمشروع؛ وتبقى تحويلات المخزون إجراءً منفصلاً.
  8. Choose Site transfers to move available stock from a warehouse location to a project site. Create the transfer to reserve stock. For lot/serial tracked products, review the exact reserved lot or serial lines in React and enter the actual quantity for each; each serial can be transferred at most once. Validate only quantities reserved for the transfer and choose a backorder for any remainder.اختر تحويلات الموقع لنقل المخزون المتاح من موقع المستودع إلى موقع المشروع. أنشئ التحويل لحجز المخزون. بالنسبة للمنتجات المتتبعة بالدفعة أو الرقم التسلسلي، راجع أسطر الحجز المحددة في React وأدخل الكمية الفعلية لكل منها؛ لا يمكن نقل الرقم التسلسلي أكثر من مرة واحدة. اعتمد الكميات المحجوزة للتحويل فقط واختر إنشاء طلب متبقٍ لأي كمية غير منقولة.
  9. Choose Receipts to see incoming purchase deliveries. Open an eligible receipt and confirm its destination. For a one-step receipt, choose an active bin in the same warehouse; multi-step receipts retain their configured Odoo staging flow. Enter the actual quantities delivered, choose whether Odoo should create a backorder for the remainder, then validate to update native stock and purchase received quantities.اختر الاستلامات لعرض توريدات الشراء الواردة وتأكد من موقع الوجهة. في الاستلام بخطوة واحدة، اختر موقعاً نشطاً في المستودع نفسه؛ وتحافظ الاستلامات متعددة الخطوات على مسار التجهيز المضبوط في Odoo. أدخل الكميات المستلمة فعلياً، وحدد إنشاء طلب متبقٍ عند الحاجة، ثم اعتمد لتحديث المخزون وكميات الشراء المستلمة في Odoo.
  10. For a lot-tracked product, enter the actual received quantity, add the supplier batch/lot number, and enter the quantity represented by that lot. For a serial-tracked product, add one unique serial number for each received unit; each serial must represent exactly one unit. The sum of the lot/serial quantities must match the received quantity. Odoo verifies or creates the native lot and serial records according to the incoming operation type.للمنتج المتتبع بالتشغيلة، أدخل الكمية المستلمة فعلياً ثم أضف رقم تشغيلة المورد والكمية التي تمثلها. وللمنتج المتتبع تسلسلياً، أضف رقماً تسلسلياً فريداً لكل وحدة مستلمة؛ يجب أن يمثل كل رقم وحدة واحدة بالضبط. يجب أن يطابق مجموع كميات التشغيلات أو الأرقام التسلسلية الكمية المستلمة. يتحقق Odoo من سجلات التشغيلات والأرقام التسلسلية الأصلية أو ينشئها وفقاً لنوع عملية الاستلام.
  11. Review confirmation does not itself confirm anything. Only Confirm order submits that state change.لا تؤكد مراجعة التأكيد أي شيء بمفردها. يرسل تأكيد الطلب وحده تغيير الحالة.
  12. Your role and the document state determine available edit/delete actions. A denied request remains an error.تحدد صلاحياتك وحالة المستند إجراءات التعديل والحذف المتاحة. يبقى الطلب المرفوض خطأ ولا يُعرض كنجاح.
React supports material requests, draft RFQ handoff and actual quantities for incoming receipts, including lot/serial details and native backorders. Supplier comparison, complete three-way matching and wider role/company acceptance remain open; this is not full purchasing parity.تدعم React طلبات المواد وتحويلها إلى مسودة عرض سعر والكميات الفعلية للاستلامات الواردة، بما فيها تفاصيل التشغيلات والأرقام التسلسلية والطلبات المتبقية الأصلية. لا تزال مقارنة الموردين والمطابقة الثلاثية الكاملة واختبارات الأدوار والشركات الأوسع مفتوحة؛ وهذا لا يمثل تكافؤاً كاملاً للمشتريات.
USER GUIDEدليل المستخدم / 07

Work with invoices and vendor billsاعمل على فواتير العملاء والموردين

Use the accounting register to distinguish customer invoices from vendor bills and view their payment states.استخدم سجل المحاسبة للتمييز بين فواتير العملاء والموردين وعرض حالات الدفع.

  1. Choose Accounting. Filter document types and statuses; Unpaid customer invoices excludes vendor bills and drafts.اختر المحاسبة. صفّ حسب النوع والحالة؛ تستبعد فواتير العملاء غير المدفوعة فواتير الموردين والمسودات.
  2. Open Milestone billing to review progress certificates. Odoo creates an invoice draft after certificate approval; the React action can retry creation for an approved certificate that has no linked invoice.افتح فواتير الإنجاز لمراجعة شهادات التقدم. ينشئ Odoo مسودة فاتورة بعد اعتماد الشهادة؛ ويمكن إعادة محاولة الإنشاء لشهادة معتمدة بلا فاتورة مرتبطة.
  3. The sample milestone screen is preview data. In live mode Odoo controls certificate access, account taxes and invoice creation. This action never posts or sends the invoice.شاشة الإنجاز التجريبية بيانات معاينة. في الوضع الفعلي يتحكم Odoo في صلاحيات الشهادة وضرائب الحساب وإنشاء الفاتورة. لا يرحّل هذا الإجراء الفاتورة ولا يرسلها.
  4. In Accounting → Payments, select open invoices or vendor bills for the same partner and register a pooled payment or enter an exact amount per document. Review the total, journal, date and memo before registering. Draft payments can be canceled from React. Eligible posted payments can be reversed with a required reason; Odoo posts a linked reversal journal entry and restores the open balance. Bank-statement-matched payments must first be unmatched, and internal transfers use Odoo’s native two-leg process.في المحاسبة ← الدفعات، حدّد فواتير مفتوحة أو فواتير مورد للمورّد أو العميل نفسه، ثم سجّل دفعة مجمّعة أو أدخل مبلغاً دقيقاً لكل مستند. راجع الإجمالي والدفتر والتاريخ والوصف قبل التسجيل. يمكن إلغاء الدفعات المسودة من React. ويمكن عكس الدفعات المرحلة المؤهلة مع ذكر السبب؛ ينشئ Odoo قيد عكس مرتبطاً ويعيد الرصيد المفتوح. يجب أولاً فك مطابقة الدفعات المرتبطة بكشف بنك، أما التحويلات الداخلية فتتبع الإجراء الأصلي ذي الطرفين في Odoo.
  5. The live Payments register loads 50 records per page and checks one extra record to enable Next only when another page exists. Use Previous/Next to browse older authorized payments. Search and status filters return to page one; Odoo applies the active-company and record permissions on every page.يعرض سجل الدفعات الفعلي ٥٠ سجلاً في كل صفحة ويفحص سجلاً إضافياً لتفعيل التالي عند وجود صفحة أخرى. استخدم السابق والتالي لتصفح الدفعات الأقدم المتاحة لصلاحياتك. تعيد عوامل البحث والحالة العرض إلى الصفحة الأولى، ويطبق Odoo صلاحيات الشركة والسجلات في كل صفحة.
  6. Choose Export CSV to download all payments matching the current search and status, across pages. The export includes linked documents, actor/time, references and reversal details. Exports are limited to 5,000 rows; if the page reports a cap, narrow the search/status and export again. Spreadsheet formula-like values are escaped.اختر تصدير CSV لتنزيل كل الدفعات المطابقة للبحث والحالة الحاليين عبر الصفحات. يتضمن التصدير المستندات المرتبطة وبيانات المنفذ والوقت والمراجع وتفاصيل العكس. الحد الأقصى ٥٠٠٠ صف؛ إذا ظهرت رسالة الحد، ضيّق البحث أو الحالة ثم أعد التصدير. تُعالج القيم التي قد تُفسر كصيغ في برامج الجداول.
  7. In design preview, open Bank reconciliation to inspect linked synthetic statement and invoice examples. Reconciliation actions are disabled; actual matching is performed in Odoo under your accounting access.في معاينة التصميم افتح تسوية البنك لمراجعة أمثلة اصطناعية مترابطة لكشف الحساب والفواتير. إجراءات التسوية معطلة؛ تتم المطابقة الفعلية في Odoo وفق صلاحياتك المحاسبية.
  8. For a live import, choose Accounting → Statement import, select a QIF/OFX/CAMT/MT940 file and its bank journal, then review the imported transactions in Bank reconciliation. CSV/Excel requires a journal file map configured by an accountant; import permission is restricted to accounting users.للاستيراد الفعلي اختر المحاسبة ← استيراد كشف، وحدد ملف QIF أو OFX أو CAMT أو MT940 ودفتر البنك، ثم راجع الحركات المستوردة في تسوية البنك. تتطلب ملفات CSV/Excel خريطة أعمدة للدفتر يضبطها المحاسب؛ ويقتصر الاستيراد على المستخدمين المحاسبيين.
  9. In live Bank reconciliation, review the proposed invoice/payment matches and Odoo balance before applying. To reverse an authorized match, select Reconciled, reopen the transaction and choose Undo reconciliation. Odoo restores the open invoice/bill balance and the suspense counterpart; the action is denied to users without accountant access or access to that company.في تسوية البنك الفعلية، راجع مطابقة الفواتير أو الدفعات المقترحة ورصيد Odoo قبل الاعتماد. للتراجع عن مطابقة مصرح بها، اختر تمت التسوية، وافتح الحركة ثم اختر التراجع عن التسوية. يعيد Odoo رصيد الفاتورة أو فاتورة المورد المفتوح والبند المقابل في الحساب الوسيط؛ ويُرفض الإجراء لمن لا يملك صلاحية المحاسب أو صلاحية الوصول إلى الشركة.
  10. When a customer pays more than the invoice, review the remaining suspense amount. If policy confirms the excess is a credit or income, add an explicit counterpart to the approved account, check that Odoo shows a zero remainder, then apply the reconciliation. Do not write off a customer overpayment without the accounting decision and account required by your company.عندما يدفع العميل مبلغاً يتجاوز الفاتورة، راجع المبلغ المتبقي في الحساب الوسيط. إذا أكدت السياسة أن الزيادة رصيد دائن أو إيراد، فأضف بنداً مقابلاً صريحاً إلى الحساب المعتمد، وتحقق من ظهور الرصيد صفراً في Odoo ثم اعتمد التسوية. لا تشطب الزيادة دون القرار المحاسبي والحساب المعتمد من شركتك.
  11. For a bank fee with VAT, choose the company-approved reconciliation model and review the Odoo preview line by line. The isolated example breaks a SAR 115 fee into SAR 100 expense and SAR 15 purchase VAT, with zero remaining suspense. Confirm the tax and expense accounts follow your accounting policy before applying.لرسوم البنك الخاضعة للضريبة، اختر نموذج التسوية المعتمد للشركة وراجع معاينة Odoo بنداً بنداً. يقسم المثال المعزول رسماً قدره 115 ريالاً إلى مصروف 100 ريال وضريبة مشتريات 15 ريالاً، مع رصيد وسيط متبقٍ يساوي صفراً. تحقق من توافق حسابي الضريبة والمصروف مع السياسة المحاسبية قبل الاعتماد.
  12. Accounting managers can open CSV / Excel maps, create a company-specific map, enter the exact header names or 1-based column positions, choose delimiter, decimal/date conventions and Excel sheet, then save it in Odoo. Assign the map to the matching bank journal before import. Shared maps can be viewed, but only company-owned maps can be edited; an assigned map must be unassigned before deletion.يمكن لمدير المحاسبة فتح خرائط CSV وExcel وإنشاء خريطة للشركة وإدخال أسماء العناوين بدقة أو أرقام الأعمدة بدءاً من 1، وتحديد الفاصل وطريقة الكسور والتاريخ وورقة Excel، ثم حفظها في Odoo. اربط الخريطة بدفتر البنك المناسب قبل الاستيراد. يمكن عرض الخرائط المشتركة، لكن تعديل خرائط الشركة فقط؛ ويجب إلغاء ربط الخريطة بالدفتر قبل حذفها.
  13. A mapped CSV import was exercised through the live authenticated BFF and native Odoo wizard on an isolated QA database. For this manual, see the isolated QA setup example in the CSV / Excel maps screenshot index; test records are routinely removed after verification.تم اختبار استيراد CSV بخريطة عبر BFF الموثق ومعالج Odoo الأصلي في قاعدة QA معزولة. راجع مثال الإعداد المعزول في فهرس صور خرائط CSV وExcel؛ وتُحذف سجلات الاختبار بعد التحقق.
  14. Create a new invoice/bill and choose the document type. Enter explicit unit prices for every invoice line.أنشئ فاتورة جديدة واختر نوعها. أدخل سعراً صريحاً لكل بند فاتورة.
  15. Unknown sample balances are shown as a dash. They are not assumed to be zero.تُعرض الأرصدة التجريبية غير المعروفة بشرطة ولا تُفترض صفراً.
  16. Save as draft. Review partner, lines, tax and total in the saved record before using Review posting.احفظ كمسودة. راجع الشريك والبنود والضريبة والإجمالي في السجل المحفوظ قبل مراجعة الترحيل.
  17. Post document is an explicit live action using your permissions and the original record timestamp. Posted documents remain locked here.ترحيل المستند إجراء فعلي صريح يستخدم صلاحياتك والطابع الزمني الأصلي. تبقى المستندات المرحّلة مقفلة هنا.
For the demo, keep financial examples as drafts. The UI is not evidence that ZATCA Simulation onboarding or Saudi go-live acceptance is complete.للعرض التوضيحي أبقِ الأمثلة المالية كمسودات. ليست الواجهة دليلاً على اكتمال تهيئة محاكاة ZATCA أو قبول الإطلاق السعودي.
USER GUIDEدليل المستخدم / 08

Ask a specialist and review draftsاسأل متخصصاً وراجع المسودات

Choose a specialist for customer, sales, purchasing, finance or business-summary work. The ERP coordinator supports broader requests.اختر متخصصاً للعملاء أو المبيعات أو المشتريات أو المالية أو ملخص الأعمال. يدعم منسق الأعمال الطلبات الأوسع.

  1. In live mode, type your request in Arabic or English. Suggested prompts only fill the composer; Send request starts the task.في الوضع الفعلي اكتب طلبك بالعربية أو الإنجليزية. تملأ المقترحات حقل الطلب فقط؛ يبدأ إرسال الطلب المهمة.
  2. Wait for the server response. Local inference may take minutes. A progress indicator is not a completed result.انتظر رد الخادم. قد يستغرق النموذج المحلي دقائق. مؤشر التقدم ليس نتيجة مكتملة.
  3. If a draft is proposed, inspect the partner/product record IDs, quantities, prices and complete payload.إذا اقتُرحت مسودة فافحص معرّفات الشريك والمنتجات والكميات والأسعار والمحتوى الكامل.
  4. Reject sends a rejection. Approve draft creation permits only those proposed drafts. Order confirmation and invoice posting remain separate business actions.يرسل رفض قرار الرفض. تسمح الموافقة على إنشاء المسودة بإنشاء المسودات المقترحة فقط. يظل تأكيد الطلب وترحيل الفاتورة إجراءين منفصلين.
  5. After a decision, reopen the request from Recent requests to inspect its saved Odoo review receipt: reviewer, Riyadh time, company, rationale, request ID and related draft.بعد اتخاذ القرار، أعد فتح الطلب من الطلبات الأخيرة لمراجعة إيصال القرار المحفوظ في أودو، بما يشمل المراجع ووقت الرياض والشركة والمبرر ومعرّف الطلب والمسودة المرتبطة.
  6. Resolve a pending review before changing specialists. Recent requests lets you reopen stored replies and pending reviews. A completed conversation can provide context to a follow-up with the same specialist.احسم المراجعة المعلقة قبل تغيير المتخصص. تتيح الطلبات الأخيرة فتح الردود المحفوظة والمراجعات المعلقة. يمكن استخدام سياق محادثة مكتملة للمتابعة مع المتخصص نفسه.
  7. Open record appears only for returned Odoo records with a supported local link. Check request history after a service failure before retrying.يظهر فتح السجل فقط لسجلات Odoo المُرجعة برابط محلي مدعوم. راجع سجل الطلبات بعد فشل الخدمة قبل المحاولة مجدداً.
Preview cannot run AI or create drafts. Watermarked approval/result images in this guide use synthetic test responses, not a live model or customer transaction.لا تشغّل المعاينة الذكاء الاصطناعي ولا تنشئ مسودات. تستخدم صور الموافقة والنتائج الموسومة في هذا الدليل ردود اختبار اصطناعية، لا نموذجاً فعلياً أو معاملة عميل.
USER GUIDEدليل المستخدم / 09

Plan and complete follow-upsخطّط للمتابعات وأنجزها

Tasks are Odoo activities assigned to you and linked to accessible company records.المهام أنشطة Odoo مسندة إليك ومرتبطة بسجلات الشركة المتاحة لك.

  1. Choose Tasks & Workflows. Search a task or document and filter All, Today, Overdue or Upcoming.اختر المهام وسير العمل. ابحث بالمهمة أو المستند وصفّ حسب الكل أو اليوم أو متأخرة أو قادمة.
  2. In Plan a follow-up choose a department and linked document, then enter a summary and valid deadline.في خطّط لمتابعة اختر القسم والمستند المرتبط، ثم أدخل الملخص والموعد الصحيح.
  3. Choose Schedule task. A successful response saves a native activity assigned to your user.اختر جدولة المهمة. يحفظ الرد الناجح نشاطاً أصلياً مسنداً إلى مستخدمك.
  4. Choose Complete on a task to review it first. Add optional feedback, then choose Complete task. Keep open cancels the decision.اختر إنجاز على المهمة لمراجعتها أولاً. أضف ملاحظات اختيارية ثم اختر إنجاز المهمة. يلغي إبقاء المهمة القرار.
  5. A denied completion keeps the task open. Refresh after errors rather than assuming the activity was completed.يبقي رفض الإنجاز المهمة مفتوحة. حدّث بعد الأخطاء ولا تفترض اكتمال النشاط.
  6. Node-RED is a separate optional local editor. It needs its own authorized login; single sign-on is not enabled.Node-RED محرر محلي اختياري منفصل. يحتاج إلى تسجيل دخول مصرّح به؛ الدخول الموحد غير مفعل.
The preview task form is disabled and does not simulate completed work. Task-list/review tutorial screenshots are explicitly synthetic examples.نموذج المهام في المعاينة معطل ولا يحاكي أعمالاً منجزة. صور قائمة المهام ومراجعتها أمثلة اصطناعية موضحة صراحة.
USER GUIDEدليل المستخدم / 10

Quick answers for the walkthroughإجابات سريعة أثناء العرض

Use these checks when a screen looks different from an example.استخدم هذه النقاط عندما تختلف الشاشة عن المثال.

  1. No records? Check the current company and your access, clear filters, then refresh. Only recent accessible records are loaded.لا توجد سجلات؟ تحقق من الشركة الحالية وصلاحياتك وامسح التصفية ثم حدّث. تُحمّل السجلات الحديثة المتاحة فقط.
  2. Edit/delete disabled? The record state or account permissions may prevent the action. Confirmed and posted records use native Odoo processes.التعديل أو الحذف معطل؟ قد تمنع حالة السجل أو صلاحيات الحساب الإجراء. تتبع المستندات المؤكدة والمرحّلة إجراءات Odoo الأصلية.
  3. A record changed? Close and reopen it before editing. Do not bypass the revision warning.تغيّر السجل؟ أغلقه وأعد فتحه قبل التعديل. لا تتجاوز تنبيه المراجعة.
  4. Missing company logo on another device? Appearance choices are stored in the current browser, not tenant-wide document branding.اختفى الشعار في جهاز آخر؟ تُحفظ تفضيلات المظهر في المتصفح الحالي، وليست هوية عامة لمستندات الشركة.
  5. Need the guide offline? Save this HTML file. Screenshots, fonts and instructions are embedded. Use Print / Save PDF to print it.تحتاج الدليل دون اتصال؟ احفظ ملف HTML هذا. الصور والخطوط والتعليمات مضمّنة فيه. استخدم الطباعة أو الحفظ بصيغة PDF.
The responsive office app is not the separate offline Site PWA. This manual does not certify full construction/offline/compliance acceptance.تطبيق المكتب المتجاوب مستقل عن تطبيق الموقع للعمل دون اتصال. لا يثبت هذا الدليل قبول جميع خصائص البناء أو عدم الاتصال أو الامتثال.
USER GUIDEدليل المستخدم / 11

Odoo backend QA (internal only)اختبار خلفية Odoo (داخلي فقط)

React is the end-user workspace for daily operations. Odoo is the authoritative backend; the screens in this chapter are internal QA/admin evidence, not the required customer workflow.React هي مساحة المستخدم اليومية. Odoo هي الخلفية المعتمدة؛ الشاشات في هذا الفصل أدلة اختبار وإدارة داخلية وليست مسار الاستخدام المطلوب للعميل.

  1. Use the React workspace for office records. Open Odoo only for authorized internal QA or administration, with a separate test account and database.استخدم مساحة React لسجلات المكتب. افتح Odoo للاختبار أو الإدارة الداخلية المصرح بها فقط، بحساب وقاعدة اختبار منفصلين.
  2. The separate construction lab is at http://127.0.0.1:8069. Its databases and installed applications differ from the office foundation.مختبر البناء المنفصل على http://127.0.0.1:8069. تختلف قواعد بياناته وتطبيقاته المثبتة عن أساس المكتب.
  3. The native screenshots below were captured from be_qa_20261023, an isolated QA database with tutorial and standard demo records. An administrator supplies QA access separately; passwords are never included in this guide.التُقطت صور Odoo أدناه من be_qa_20261023، قاعدة اختبار معزولة تحتوي سجلات تعليمية وتجريبية. يوفّر المسؤول بيانات الدخول بشكل منفصل ولا يتضمن الدليل كلمات مرور.
  4. Use the application menu to open a register, search for QA Tutorial, then select a row. Changes in QA do not update the office database.استخدم قائمة التطبيقات لفتح السجل وابحث عن QA Tutorial ثم اختر صفاً. لا تحدّث تغييرات الاختبار قاعدة المكتب.
QA examples use the database’s test accounting configuration. They do not demonstrate Saudi invoicing certification or a completed production rollout.تستخدم الأمثلة إعدادات المحاسبة التجريبية لقاعدة الاختبار، ولا تثبت اعتماد الفوترة السعودية أو اكتمال النشر الفعلي.
USER GUIDEدليل المستخدم / 12

Projects, BOQ and daily site recordsالمشاريع وجداول الكميات وسجلات الموقع

Use the React Projects & BOQ workspace for project BOQ drafts, cost lines and baseline approval. In Project plan, record the current schedule as a named snapshot, submit the rationale, then have a different owner or PM review the task snapshot and approve or reject it with a recorded reason. Approved baselines become the official project baseline; task create, update and delete events appear in the immutable change history. This slice is verified against isolated Odoo QA.استخدم مساحة المشاريع وجداول الكميات في React لمسودات الكميات وبنود التكلفة واعتماد خط الأساس. في خطة المشروع، احفظ الجدول الحالي كلقطة مسماة وأرسل المبرر، ثم اطلب من مالك أو مدير مشروع آخر مراجعة لقطة المهام واعتمادها أو رفضها مع تسجيل السبب. يصبح خط الأساس المعتمد هو الرسمي للمشروع، وتظهر أحداث إنشاء المهام وتعديلها وحذفها في سجل تغييرات غير قابل للتعديل. تم التحقق من هذه الشريحة في Odoo للاختبار المعزول.

  1. Open Projects & BOQ. Choose New BOQ, select a project, enter a name, then add named sections and work, material, labour or equipment lines.افتح المشاريع وجداول الكميات. اختر جدولاً جديداً وحدد المشروع واسمه، ثم أضف الأقسام وبنود الأعمال أو المواد أو العمالة أو المعدات.
  2. Choose a unit, enter a positive quantity and nonnegative unit rate. Review the planned total, then choose Save draft. Odoo validates your project, company and access.اختر الوحدة وأدخل كمية موجبة وسعراً غير سالب. راجع الإجمالي المخطط ثم اختر حفظ المسودة. يتحقق Odoo من المشروع والشركة والصلاحية.
  3. Open a draft and choose Edit draft to update its sections or lines. Odoo rejects stale versions; refresh and review the latest draft before retrying.افتح المسودة واختر تعديل لتحديث الأقسام أو البنود. يرفض Odoo الإصدارات القديمة؛ حدّث الصفحة وراجع أحدث مسودة قبل إعادة المحاولة.
  4. Choose Review & confirm, inspect the amount, then Confirm baseline. Odoo snapshots the approved baseline and locks the confirmed BOQ. Only an authorized Build Engine role can create or approve it.اختر مراجعة واعتماد، وافحص المبلغ، ثم اعتمد خط الأساس. يحفظ Odoo نسخة معتمدة ويقفل جدول الكميات. يلزم دور مخوّل في Build Engine للإنشاء أو الاعتماد.
  5. For scheduling, choose Project plan, select a project and add phases or tasks. A project manager can enable milestones, then add a deadline, stakeholder obligation, responsible person and linked tasks. Odoo allows a milestone to be marked reached after its linked tasks are closed. Record schedule baselines from the same workspace; the requester cannot approve their own snapshot.للجدولة، اختر خطة المشروع وحدد مشروعاً ثم أضف المراحل أو المهام. يستطيع مدير المشروع تفعيل المعالم وإضافة الموعد النهائي والتزام صاحب المصلحة والمسؤول والمهام المرتبطة. يسمح Odoo بإكمال المعلم بعد إغلاق مهامه المرتبطة. سجّل خطوط أساس الجدول من المساحة نفسها؛ ولا يمكن لمقدم الطلب اعتماد لقطته.
  6. For a project lifecycle, open Workflow execution. Review the current Odoo stage and its mandatory quality gate. A Project Manager cannot advance while the gate is pending or failed. The assigned Site role opens Quality & Safety → Inspections & checklists, signs the required item, then the Project Manager refreshes the workflow and retries. Odoo records both actors and timestamps; the gate is not bypassed by the React screen.لمتابعة دورة حياة المشروع، افتح تنفيذ سير العمل. راجع مرحلة Odoo الحالية وبوابة الجودة الإلزامية. لا يستطيع مدير المشروع التقدم ما دامت البوابة معلقة أو غير ناجحة. يفتح دور الموقع المعيّن الجودة والسلامة ← قوائم الفحص، ويوقّع البند المطلوب؛ ثم يحدّث مدير المشروع سير العمل ويعيد المحاولة. يسجل Odoo المستخدمين والوقت، ولا تتجاوز شاشة React البوابة.
  7. For scheduled materials, edit a task and select a confirmed material BOQ line, then enter the quantity allocated to that task. In the task row choose Check material for planned date, select the project stock location and save the review. Odoo compares the allocated amount with its stock forecast through the planned start date and stores an audit snapshot; this does not reserve stock or create an order.لمراجعة المواد المجدولة، عدّل المهمة واختر بند مواد معتمداً من جدول الكميات، ثم أدخل الكمية المخصصة للمهمة. في صف المهمة اختر فحص توفر المادة للتاريخ المخطط وحدد موقع مخزون المشروع واحفظ المراجعة. يقارن Odoo الكمية المخصصة بتوقع المخزون حتى تاريخ بدء المهمة ويحفظ لقطة تدقيق؛ ولا يحجز المخزون أو ينشئ طلب شراء.
  8. For labor time, choose Timesheets, select a project and one of its tasks, then enter the work date, hours and a short summary. React records the entry against your linked employee; Odoo calculates labor cost and updates BOQ actuals when a task is linked to a labour line. Review and approval actions are not yet available in this React screen.لتسجيل وقت العمالة، اختر سجلات الوقت ثم حدد المشروع وإحدى مهامه وأدخل تاريخ العمل والساعات وملخصاً قصيراً. يسجل React الإدخال باسم الموظف المرتبط بحسابك؛ ويحسب Odoo تكلفة العمالة ويحدّث فعليات جدول الكميات عند ربط المهمة ببند عمالة. إجراءات المراجعة والاعتماد غير متاحة بعد في شاشة React.
  9. For a spreadsheet, choose the Bills of quantities tab, then Import spreadsheet. Select an .xlsx file, check the suggested column mapping, and choose Validate rows. Fix every row error before selecting an available project and importing one draft BOQ.لاستيراد ملف، اختر تبويب جداول الكميات ثم استيراد Excel. اختر ملف xlsx وراجع ربط الأعمدة المقترح ثم تحقق من الصفوف. أصلح جميع الأخطاء قبل اختيار مشروع متاح واستيراد مسودة واحدة.
  10. To request an AI take-off proposal, choose Draft from drawing. Select a project, describe the scope, and upload one PNG, JPEG, WebP or PDF up to 14 MB. PDFs must contain 1–5 pages. The drawing is sent only to the configured local vision model.لطلب مقترح حصر آلي، اختر إعداد مسودة من مخطط. حدد المشروع واشرح النطاق وارفع ملف PNG أو JPEG أو WebP أو PDF لا يتجاوز ١٤ ميغابايت. يجب أن يحتوي PDF على صفحة إلى خمس صفحات. يُرسل المخطط إلى نموذج الرؤية المحلي المضبوط فقط.
  11. Review the proposed lines, units, confidence, measurement basis and warnings. Missing quantities stay blank; rates are always zero. Treat every value as an estimate requiring a quantity-surveyor check. Choose Review and edit draft to complete quantities and approved rates, then Save draft. No BOQ is written before you save. The original drawing is not stored; the saved BOQ retains its filename, drawing and scope fingerprints, local model and reviewed page count for later review.راجع البنود والوحدات ومستوى الثقة وأساس القياس والتحذيرات. تبقى الكميات غير المعروفة فارغة والأسعار صفراً دائماً. اعتبر كل قيمة تقديرية وتحتاج مراجعة حاسب كميات. اختر مراجعة وتعديل المسودة لإكمال الكميات والأسعار المعتمدة ثم احفظها. لا يُكتب جدول الكميات قبل الحفظ. لا يُحفظ المخطط الأصلي؛ ويحتفظ جدول الكميات باسم الملف وبصمتي المخطط والنطاق والنموذج المحلي وعدد الصفحات المراجعة للمراجعة لاحقاً.
  12. The project Gantt estimates its critical path from dependencies and the active Odoo company work calendar. Choose Portfolio timeline to compare all projects you can read, search tasks or filter by project; blue outlines mark the estimated critical tasks within each project. The portfolio is read-only and does not calculate cross-project dependencies, resource leveling, employee calendars or float.يقدّر مخطط المشروع المسار الحرج اعتماداً على الاعتماديات وتقويم عمل شركة Odoo الحالية. اختر الجدول الزمني للمحفظة لمقارنة المشاريع المتاحة لك وابحث عن المهام أو صفّ حسب المشروع؛ تشير الحدود الزرقاء إلى المهام الحرجة التقديرية داخل كل مشروع. عرض المحفظة للقراءة فقط ولا يحسب الاعتماديات بين المشاريع أو موازنة الموارد أو تقاويم الموظفين أو السماح الزمني.
  13. The screenshot gallery includes a live React-to-Odoo QA walkthrough. Its isolated company uses USD; it is not evidence of Saudi SAR acceptance.يتضمن معرض الصور استعراضاً فعلياً من React إلى Odoo للاختبار. تستخدم شركة الاختبار المعزولة الدولار، ولا يثبت ذلك قبول الريال السعودي.
  14. For daily site reporting, open Daily site reports under Projects & BOQ. Create a report with its project/date and optional conditions, work notes, manpower, deliveries and delays. Search report content, filter by project/date, review totals for the filtered rows, and export those rows as CSV. When offline, a draft is kept in this browser profile and queued for retry; keep the profile until sync completes. Offline attachment sync and full multi-device conflict handling are not supported.للتقارير اليومية للموقع، افتح التقارير اليومية ضمن المشاريع وجداول الكميات. أنشئ تقريراً بالمشروع والتاريخ وأضف اختيارياً حالة الموقع وملاحظات العمل والقوى العاملة والتوريدات والتأخيرات. ابحث في محتوى التقارير وصفّها بالمشروع والتاريخ وراجع إجماليات السجلات المحددة وصدّرها بصيغة CSV. عند انقطاع الاتصال تحفظ المسودة في ملف المتصفح وتنتظر إعادة المحاولة؛ احتفظ بالملف حتى اكتمال المزامنة. لا تتوفر مزامنة المرفقات دون اتصال أو معالجة كاملة للتعارض بين الأجهزة.
  15. Material capture accepts positive finite quantities. A linked BOQ item must belong to the same project/company and use its unit. Offline synchronization remains under development.يقبل تسجيل المواد كميات موجبة ومحدودة. يجب أن ينتمي بند الكميات إلى المشروع والشركة نفسيهما وأن يستخدم وحدته. لا تزال المزامنة دون اتصال.
BOQ equipment cost lines, project milestone obligations, immutable schedule baseline approval/change history and read-only approved-baseline comparison are available as verified React slices. Excel import now passed a live Project Manager flow through React, the authenticated QA BFF and isolated Odoo; a separate persisted import-batch history and retry/company-boundary acceptance remain open. The critical-path estimate is available, while working calendars, calendar-aware critical dates and full project setup/scheduling remain incomplete. Daily site reports support structured entries, offline draft retry, project/date/search filters, summary totals and CSV export; broader role acceptance remains open. Scheduled material availability is a partial review: task quantities are explicit, the forecast comparison is a dated snapshot, and this mocked React workflow has not yet had live role-based browser acceptance. The equipment-line and BOQ import screenshots use isolated test data.تتوفر في React شرائح تم التحقق منها لبنود معدات جدول الكميات والتزامات معالم المشروع واعتماد خطوط أساس الجدول وسجل التغييرات غير القابل للتعديل ومقارنة خط الأساس المعتمد للقراءة فقط. اجتاز استيراد Excel مساراً حياً لمدير المشروع عبر React وBFF الاختبار وOdoo المعزول؛ وما زال سجل دفعات الاستيراد الدائم وقبول إعادة المحاولة وحدود الشركة مفتوحاً. يتوفر تقدير المسار الحرج، بينما لا تزال تقاويم العمل والتواريخ الحرجة المرتبطة بها وإعداد المشروع الكامل والجدولة غير مكتملة. تدعم تقارير الموقع اليومية الإدخالات المنظمة وإعادة محاولة المسودات دون اتصال والتصفية بالمشروع والتاريخ والبحث والإجماليات وتصدير CSV؛ ولا يزال قبول الأدوار الأوسع مفتوحاً. مراجعة توفر المواد المجدولة جزئية: كمية المهمة محددة صراحةً ومقارنة التوقع لقطة مؤرخة ولم يخضع المسار التجريبي بعد لاختبار قبول حي بصلاحيات الأدوار. تستخدم صور المعدات والاستيراد بيانات اختبار معزولة.
USER GUIDEدليل المستخدم / 13

Quality, drawings, contracts and AI inboxالجودة والمخططات والعقود وصندوق الذكاء الاصطناعي

The native registers provide separate review steps and preserve links to the project.توفر السجلات الأصلية خطوات مراجعة منفصلة وتحافظ على ارتباطها بالمشروع.

  1. Open Workflow templates to review the published inspection flow. Published definitions are versioned instead of silently edited.افتح قوالب سير العمل لمراجعة مسار الفحص المنشور. تُنشأ إصدارات للتعريفات المنشورة بدلاً من تعديلها بصمت.
  2. Open Quality gate instances and inspect the pending tutorial checkpoint. Required evidence and role-specific sign-off must be satisfied before advancing. Do not represent sample references as regulatory certification.افتح حالات بوابات الجودة وافحص نقطة التحقق التعليمية المعلقة. يلزم استيفاء الأدلة والتوقيع حسب الدور قبل التقدم. لا تمثل المراجع التجريبية اعتماداً تنظيمياً.
  3. Open Drawings to inspect the code, revision and project. The tutorial row has no engineering file attached; CAD conversion, 3D viewing and offline markups are not demonstrated.افتح المخططات لفحص الرمز والمراجعة والمشروع. لا يرفق الصف التعليمي ملفاً هندسياً، ولا يعرض تحويل CAD أو العرض ثلاثي الأبعاد أو التعليقات دون اتصال.
  4. Open Contracts to review the tutorial draft, partner, dates and project. Tender and AI suggestion registers may be empty until their prerequisite actions create records.افتح العقود لمراجعة المسودة التعليمية والشريك والتواريخ والمشروع. قد تبقى سجلات المناقصات ومقترحات الذكاء الاصطناعي فارغة حتى تنشئ الإجراءات السابقة سجلاتها.
  5. The construction AI suggestion inbox is separate from the office React draft approval flow. Review the proposed change and source before an authorized decision. No autonomous business write is demonstrated.صندوق مقترحات ذكاء البناء مستقل عن موافقات مسودات React المكتبية. راجع التغيير المقترح ومصدره قبل القرار المصرّح به. لا يعرض الدليل كتابة أعمال مستقلة.
Registers, screenshots and passing module tests cover bounded features. Project ACLs, identity binding, archive extraction, converters and full acceptance remain open.تغطي السجلات والصور واختبارات الوحدات ميزات محددة. تبقى صلاحيات المشروع وربط الهوية واستخراج الأرشيف والتحويلات والقبول الشامل أعمالاً مفتوحة.
USER GUIDEدليل المستخدم / 14

Use React RFIs; review Odoo for QAاستخدم طلبات React وراجع Odoo للاختبار

React is the daily user workspace. The isolated Odoo preview is for internal QA and administration; other construction screens still await React delivery.تتبع واجهة Odoo الأصلية الآن ألوان مساحة React وأسلوب التنقل فيها، مع تقديم مراسلات المشروع عبر شاشات ERP الأصلية.

  1. For daily work, choose Site Correspondence in React. Search RFIs and filter by status; the list shows project, respondent, response deadline and overdue state.للعمل اليومي، اختر مراسلات الموقع في React. ابحث في الطلبات وصفّ حسب الحالة؛ تعرض القائمة المشروع والمجيب وموعد الرد وحالة التأخير.
  2. Create a draft with a subject, company project, active internal respondent, request date, response deadline and question. Save the draft, review it, then choose Send to respondent.أنشئ مسودة بعنوان ومشروع تابع للشركة ومجيب داخلي نشط وتاريخ الطلب وموعد الرد والسؤال. احفظ المسودة وراجعها ثم اختر إرسال للمجيب.
  3. A project manager or owner can open an open RFI and update its respondent or response deadline. The change uses the current record version; refresh and review again if another user changed the RFI.يمكن لمدير المشروع أو المالك فتح طلب قيد الانتظار وتحديث المجيب أو الموعد النهائي للرد. يستخدم التغيير إصدار السجل الحالي؛ حدّث الصفحة وراجع الطلب إذا غيّره مستخدم آخر.
  4. The assigned respondent opens the request and submits a response. A project manager or owner closes an answered request; authorized managers can cancel an unanswered request. Odoo checks these permissions on every action.يفتح المجيب المعيّن الطلب ويرسل الرد. يغلق مدير المشروع أو المالك الطلب بعد الإجابة، ويستطيع المدير المخوّل إلغاء الطلب غير المجاب. يتحقق Odoo من الصلاحيات في كل إجراء.
  5. The isolated native preview at http://127.0.0.1:8068 is for QA and administration. Its database is be_theme_qa_20261024. Ask your administrator for access; passwords are not embedded in this guide.معاينة Odoo المعزولة على http://127.0.0.1:8068 مخصصة للاختبار والإدارة. قاعدة بياناتها be_theme_qa_20261024. اطلب بيانات الدخول من المسؤول؛ لا يتضمن الدليل كلمات مرور.
  6. Use sidebar search to find an app or menu. On a phone, open the workspace menu; Escape closes it and restores keyboard focus. Your Odoo permissions determine the available records.استخدم البحث الجانبي للعثور على تطبيق أو قائمة. افتح قائمة مساحة العمل في الهاتف؛ يغلقها Escape ويعيد تركيز لوحة المفاتيح. تحدد صلاحيات Odoo السجلات المتاحة لك.
  7. Open Project correspondence → Requests for information. Choose New, enter a subject and question, select a company project and an active internal respondent with project access, and choose the response deadline.افتح مراسلات المشروع ← طلبات الاستفسار. اختر جديداً، وأدخل الموضوع والسؤال، وحدد مشروع الشركة ومستجيباً داخلياً نشطاً يملك صلاحية المشروع، وحدد الموعد النهائي للرد.
  8. Save the draft, then Send for response. Odoo assigns a reference and schedules an activity for the respondent. The submitted question is locked to preserve its history.احفظ المسودة ثم اختر إرسال للرد. يعيّن Odoo مرجعاً وينشئ نشاطاً للمستجيب. يُقفل السؤال المرسل للحفاظ على تاريخه.
  9. The assigned respondent opens the RFI, selects Response, enters the answer and chooses Submit answer. The native activity is completed and the responder/time are recorded.يفتح المستجيب المسند إليه الطلب، ويختار الرد، ويدخل الإجابة ثم يضغط إرسال الرد. يُنجز النشاط الأصلي ويُسجل صاحب الرد ووقته.
  10. Open Project log, choose an accessible project, then filter by RFI or Submittal and search the reference, subject or response. Choose Export CSV or Export Excel to download the visible filtered correspondence. The workbook includes state, actors and times, deadlines, response or decision notes, drawing and revision history. Odoo checks project access; a log capped at 500 records per type shows a notice.افتح سجل المشروع واختر مشروعاً متاحاً، ثم صفِّ حسب طلب المعلومات أو مستند الاعتماد وابحث بالمرجع أو الموضوع أو الرد. اختر تصدير CSV أو Excel لتنزيل المراسلات الظاهرة بعد التصفية. يتضمن ملف Excel الحالة والمنفذين والأوقات والمواعيد والرد أو ملاحظات القرار والمخطط وسجل الإصدارات. يتحقق Odoo من صلاحية المشروع، ويعرض تنبيهاً عند بلوغ حد ٥٠٠ سجل لكل نوع.
  11. A project manager or owner closes an answered RFI. The Audit tab shows the original author, update timestamps, version and closure actor/time. Closed requests remain locked.يغلق مدير المشروع أو المالك طلب الاستفسار بعد الرد عليه. يعرض تبويب سجل التدقيق المنشئ الأصلي وأوقات التحديث والإصدار وصاحب الإغلاق ووقته. تبقى الطلبات المغلقة مقفلة.
  12. Filter Overdue to find open requests past their deadline. Manager changes to the deadline or respondent update the native response activity. Cancellation closes the outstanding activity.صفّ حسب متأخر للعثور على الطلبات المفتوحة التي تجاوزت موعدها. تُحدّث تغييرات المدير في الموعد أو المستجيب نشاط الرد الأصلي. ينهي الإلغاء النشاط المعلق.
  13. For Arabic or English in native Odoo, use the user menu → My Preferences → Language, save, then sign in again. The pictured QA workflow was verified in both language layouts.لاختيار العربية أو الإنجليزية في Odoo الأصلي، استخدم قائمة المستخدم ← تفضيلاتي ← اللغة، ثم احفظ وسجّل الدخول مجدداً. تحقّق الاختبار من تخطيطي اللغتين.
The React RFI UI journey passes a mocked browser flow, and native Odoo acceptance is documented. Full live-role/company/project boundary acceptance is pending. Screenshots use synthetic examples or an isolated QA database; they are not live customer records.اجتازت واجهة React لطلبات المعلومات اختبار متصفح ببيانات اصطناعية، ووُثق قبول Odoo الأصلي. لا يزال قبول الأدوار الفعلية وحدود الشركة والمشروع قيد التحقق. تستخدم الصور أمثلة اصطناعية أو قاعدة اختبار معزولة وليست سجلات عملاء فعلية.
USER GUIDEدليل المستخدم / 15

Saudi accounting and local specialistsالمحاسبة السعودية والمختصون المحليون

Use the isolated Saudi company to rehearse financial workflows and ask read-only local specialists.استخدم الشركة السعودية المعزولة للتدرب على العمليات المحاسبية وسؤال المختصين المحليين للقراءة فقط.

  1. Open http://localhost:8068, sign in as be_ksa_qa_manager and select QA KSA — Building Services. The local password is BE_ACCOUNTING_QA_PASSWORD in ignored .env.افتح http://localhost:8068 وسجّل الدخول بالحساب be_ksa_qa_manager واختر QA KSA — Building Services. كلمة المرور المحلية في .env تحت BE_ACCOUNTING_QA_PASSWORD.
  2. Open Accounting KSA. Review draft customer invoices and vendor bills, native Saudi chart/taxes, assets/deferrals, budget, bank tools and financial reports.افتح المحاسبة السعودية. راجع مسودات فواتير العملاء والموردين ودليل الحسابات والضرائب السعودي والأصول والموازنات وأدوات البنوك والتقارير.
  3. For the posted-only2026 demo, profit and loss shows SAR25,000 income minus12,000 expenses =13,000 profit. Synthetic general entries balance137,000 debit and credit. Invoices and bills remain drafts.في عرض عام٢٠٢٦ للقيود المرحلة فقط، تظهر إيرادات٢٥٬٠٠٠ ريال ومصروفات١٢٬٠٠٠ وربح١٣٬٠٠٠. تتوازن القيود الاصطناعية بمجموع١٣٧٬٠٠٠ مدين ودائن. تظل الفواتير مسودات.
  4. Download PDF/XLSX reports and verify company, period, currency and figures. Inspect the36,000SAR asset schedule and120,000SAR project budget with an accountant.نزّل تقارير PDF وXLSX وتحقق من الشركة والفترة والعملة والأرقام. راجع جدول أصل بقيمة٣٦٬٠٠٠ ريال وموازنة المشروع١٢٠٬٠٠٠ ريال مع المحاسب.
  5. Choose AI specialists → New. Select CRM, sales, purchasing, accounting, analyst or coordinator; ask a question and press Ask local specialist. Review the stored reply, model, completion time and Records used.اختر المختصون الذكيون ← جديد. حدد مختص العلاقات أو المبيعات أو المشتريات أو المحاسبة أو المحلل أو المنسق، واطرح السؤال واضغط اسأل المختص المحلي. راجع الرد والنموذج والوقت والسجلات المستخدمة.
  6. All six profiles completed actual qwen3.8:27b smoke checks. These advisers cannot create/post/send business documents. Finance access is required for accounting context. Existing React approval agents keep their separate workflow.نجحت فحوص الاتصال الفعلي للنموذج qwen3.8:27b للملفات الستة. لا يمكن لهؤلاء المستشارين إنشاء مستندات أعمال أو ترحيلها أو إرسالها. تتطلب المحاسبة صلاحية مالية. تحتفظ وكلاء React بمسار موافقاتها المستقل.
  7. Open /qa-checklist.html to run26manual scenarios, record PASS/FAIL/BLOCKED and export your observations. The page also lists every executed automated case with its scope.افتح /qa-checklist.html لتنفيذ٢٦ حالة يدوية وتسجيل النجاح أو الفشل أو العوائق وتصدير ملاحظاتك. تسرد الصفحة أيضاً كل حالة آلية منفذة ونطاقها.
No live Saudi government/bank API or Fatoora submission is demonstrated. Official access and accountant approval remain required. Banking reconciliation/OCR accuracy and full user acceptance are separate manual checks.لا يشمل العرض اتصالاً فعلياً بواجهات الجهات السعودية أو البنوك أو إرسال فواتير إلى فاتورة. تظل الصلاحيات الرسمية واعتماد المحاسب مطلوبة. التسوية البنكية ودقة التعرف على المستندات والقبول الكامل فحوص يدوية مستقلة.
USER GUIDEدليل المستخدم / 15

Register and move equipmentسجّل المعدات وانقلها

Use the React Equipment register to capture company assets and maintain an auditable project-custody history.استخدم سجل المعدات في React لتسجيل أصول الشركة وحفظ سجل قابل للتدقيق لحركة عهدتها بين المشاريع.

  1. Choose Equipment. Register equipment and enter the asset name, model or serial number, acquisition cost/date/reference, vendor and warranty date. Odoo saves the authoritative maintenance equipment record.اختر المعدات. سجّل المعدة وأدخل الاسم والطراز أو الرقم التسلسلي وتكلفة الاقتناء وتاريخه ومرجعه والمورد وتاريخ الضمان. يحفظ Odoo سجل المعدة المعتمد.
  2. Select an item to review its company, current project, cost, acquisition details, creator and last update. Movement history shows the project, actor, timestamp and note.اختر معدة لمراجعة الشركة والمشروع الحالي والتكلفة وبيانات الاقتناء والمنشئ وآخر تحديث. يعرض سجل الحركات المشروع والمنفذ والوقت والملاحظة.
  3. Check out an in-yard asset to a project. Transfer a checked-out asset to a different project, or return it to the yard. Odoo rejects duplicate checkout and a return to the wrong project.اصرف معدة موجودة في المستودع إلى مشروع. انقل المعدة المصروفة إلى مشروع آخر أو أعدها للمستودع. يرفض Odoo الصرف المكرر والإرجاع إلى مشروع غير صحيح.
  4. Where the optional Equipment Accounting integration is installed, link the equipment to a running Accounting KSA fixed asset and submit a retirement request with its reason, date and sale details. A different finance/owner user with accounting rights must approve; approval posts the native disposal journal entry and archives the equipment. Rejection requires a reason.عند تثبيت تكامل محاسبة المعدات الاختياري، اربط المعدة بأصل ثابت سارٍ في المحاسبة السعودية وقدّم طلب التقاعد مع السبب والتاريخ وبيانات البيع. يجب أن يوافق مستخدم مالي أو مالك آخر لديه صلاحيات محاسبية؛ وترحّل الموافقة قيد التخلص الأصلي وتؤرشف المعدة. يتطلب الرفض ذكر السبب.
  5. Only authorized Build Engine roles can use custody actions. Project and company access are checked by Odoo; movement history is immutable.تقتصر إجراءات العهدة على أدوار Build Engine المصرح بها. يتحقق Odoo من صلاحيات المشروع والشركة ويحفظ تاريخ الحركات دون تعديل.
Equipment registration and custody are available. The optional Accounting KSA integration adds an independently approved native disposal path; it still requires isolated Odoo acceptance and the agreed DEC-06 approval matrix. Stock intake, broader asset capitalization, maintenance integration and offline custody remain separate requirements.يتاح تسجيل المعدات وإدارة العهدة. يضيف تكامل المحاسبة السعودية الاختياري مسار التخلص الأصلي بموافقة مستقلة؛ ولا يزال بحاجة إلى قبول Odoo المعزول واعتماد مصفوفة الموافقات DEC-06. يظل استلام المخزون ورسملة الأصول الأوسع وتكامل الصيانة والعهدة دون اتصال متطلبات منفصلة.
USER GUIDEدليل المستخدم / 16

Maintain the customer directoryأدر دليل العملاء

Create and maintain company customers in React. Archive keeps historical documents while removing a customer from new active selections.أنشئ عملاء الشركة وأدرهم في React. تحافظ الأرشفة على المستندات السابقة وتزيل العميل من قوائم الاختيار النشطة.

  1. Open CRM → Customers. Choose Active, Archived or All to filter the current company customer register. Search by name, email, VAT or Commercial Registration.افتح إدارة العملاء ← العملاء. اختر نشط أو مؤرشف أو الكل لتصفية سجل الشركة الحالية. ابحث بالاسم أو البريد أو الرقم الضريبي أو السجل التجاري.
  2. Choose Archive beside a customer, review the confirmation, then confirm. The customer becomes unavailable in active CRM, sales and accounting pickers; existing invoices and orders remain unchanged.اختر أرشفة بجانب العميل، وراجع التأكيد، ثم أكّده. لن يعود العميل متاحاً في قوائم الاختيار النشطة لإدارة العملاء والمبيعات والمحاسبة؛ وتبقى الفواتير والطلبات السابقة دون تغيير.
  3. Open the Archived filter to find the customer. Choose Restore and confirm to make them available for new workflows again.افتح تصفية مؤرشف للعثور على العميل. اختر استعادة وأكّد لإتاحته مجدداً في مسارات العمل الجديدة.
  4. If another user changed the customer after the register loaded, Odoo rejects a stale archive/restore request. Refresh the list and review the current record before retrying.إذا غيّر مستخدم آخر بيانات العميل بعد تحميل السجل، يرفض Odoo طلب الأرشفة أو الاستعادة القديم. حدّث القائمة وراجع السجل الحالي قبل إعادة المحاولة.
Archive does not merge or delete contacts. Customer merge governance and actual-role live browser acceptance remain separate work.لا تدمج الأرشفة جهات الاتصال ولا تحذفها. تظل حوكمة دمج العملاء واختبارات المتصفح المباشرة بالأدوار الفعلية أعمالاً مستقلة.
USER GUIDEدليل المستخدم / 17

Register and activate construction contractsسجّل عقود البناء وفعّلها

Use Contracts when the Build Engine contract app is enabled for your Odoo company. React records draft scope, commercial terms, compliance flags and critical dates; Odoo controls permissions and lifecycle.استخدم العقود عند تفعيل تطبيق عقود Build Engine لشركة Odoo. يسجل React النطاق التجاري والشروط وعلامات الامتثال والمواعيد الحرجة؛ ويتحكم Odoo بالصلاحيات ودورة العقد.

  1. Open Contracts and choose New contract. Select the client, supplier or subcontract type, sector, counterparty, project, contract dates, retention and variation ceiling.افتح العقود واختر عقداً جديداً. حدّد نوع العميل أو المورد أو المقاول من الباطن والقطاع والطرف المقابل والمشروع وتواريخ العقد ونسبة الاحتجاز وسقف التغييرات.
  2. Enter a named scope line, positive quantity and unit rate. Add a milestone or expiry date when needed. Choose Saudi checklist flags; the draft receives pending-review clause entries for the selected requirements.أدخل بند نطاق مسمى وكمية موجبة وسعر الوحدة. أضف موعداً رئيسياً أو تاريخ انتهاء عند الحاجة. اختر علامات قائمة التحقق السعودية؛ وتُسجل بنود المراجعة المختارة بحالة بانتظار المراجعة.
  3. Save the draft, open Contract details and review its amount, scope lines, dates and compliance checklist. Odoo sends critical-date reminder activities ahead of the due date.احفظ المسودة وافتح تفاصيل العقد وراجع المبلغ وبنود النطاق والمواعيد وقائمة الامتثال. يجدول Odoo أنشطة تذكير بالمواعيد الحرجة قبل تاريخ الاستحقاق.
  4. In Contract details, choose Run review under Clause evidence review. The saved review flags selected checklist items with neither clause text nor a reference. It preserves the reviewer and timestamp; it does not decide whether a clause is legally required or whether the agreement complies. An owner, project manager or procurement user can run it; finance can read the history.في تفاصيل العقد، اختر إجراء المراجعة ضمن مراجعة أدلة البنود. تشير المراجعة المحفوظة إلى بنود القائمة المحددة التي لا تحتوي على نص أو مرجع. وتحفظ المراجع والتوقيت؛ لكنها لا تحدد ما إذا كان البند مطلوباً قانونياً أو ما إذا كانت الاتفاقية ممتثلة. يستطيع المالك أو مدير المشروع أو المشتريات إجراءها؛ ويمكن للمالية قراءة سجلها.
  5. Only an authorized owner or project manager can activate. Activation freezes the commercial baseline; active contract lines cannot be changed. Review the confirmation carefully. An active contract must be closed before cancellation.لا يستطيع التفعيل إلا مالك أو مدير مشروع مخوّل. يثبت التفعيل خط الأساس التجاري؛ ولا يمكن تغيير بنود العقد النشط. راجع التأكيد بعناية. يجب إغلاق العقد النشط قبل إلغائه.
  6. A subcontract must link to an awarded tender and its awarded bid. React uses the winning bidder and tender project so the subcontract counterparty matches the award.يجب ربط عقد المقاولة من الباطن بمناقصة مرساة وعرضها الفائز. يستخدم React مقدم العرض الفائز ومشروع المناقصة لضمان تطابق الطرف المقابل مع الترسية.
  7. On an active contract, open Variation orders and choose a confirmed project BOQ. Select a line to modify or add a new BOQ line, enter the quantity/cost change and a reason, then save and submit. Odoo checks the linked contract ceiling. An authorized owner or project manager can approve or reject; approval applies the BOQ revision and creates a baseline.في العقد النشط، افتح أوامر التغيير واختر جدول كميات مؤكداً للمشروع. اختر بنداً لتعديله أو أضف بنداً جديداً، وأدخل تغير الكمية أو التكلفة والسبب، ثم احفظ وأرسل للمراجعة. يتحقق Odoo من سقف العقد المرتبط. يستطيع المالك أو مدير المشروع المخول الاعتماد أو الرفض؛ ويطبق الاعتماد إصدار جدول الكميات وينشئ خط أساس.
  8. React now creates and edits draft contract terms, scope, dates and checklist entries, then runs native activation, close and cancel actions. Draft editing updates existing child rows by ID and keeps omitted rows; its form currently edits the first scope line and first key date. Variation drafts now support up to 100 modify/add lines, version-checked edits and native submit/approve/reject/cancel/reset actions. Saved child rows cannot be deleted under the PM ACL; richer cost/schedule impact analysis, audit review, attachments and complete renewal/notice management remain open.ينشئ React مسودات شروط العقد والنطاق والمواعيد وقائمة التحقق ويعدلها، ثم ينفذ إجراءات التفعيل والإغلاق والإلغاء الأصلية. يحدث تعديل المسودة البنود الحالية حسب المعرّف ويحافظ على البنود غير المعروضة؛ ويعدل النموذج حالياً أول بند نطاق وأول موعد. تدعم مسودات أوامر التغيير الآن حتى 100 بند إضافة أو تعديل، مع تحرير يتحقق من الإصدار وإجراءات الإرسال والاعتماد والرفض والإلغاء وإعادة المسودة الأصلية. لا يمكن حذف البنود المحفوظة بصلاحيات مدير المشروع؛ وما زال تحليل أثر التكلفة والجدول ومراجعة سجل التدقيق والمرفقات وإدارة التجديد والإشعارات الكاملة مفتوحاً.
The example image uses synthetic browser data. The selected-clause evidence-gap review has focused isolated test coverage, while the legal rubric, document extraction, full role/tenant acceptance and remaining contract story criteria remain open; this screen does not claim complete contract parity.تستخدم الصورة بيانات متصفح اصطناعية. تمت تغطية مراجعة فجوات أدلة البنود المحددة باختبار معزول مركز؛ بينما لا تزال القواعد القانونية واستخراج المستندات واختبارات الأدوار وعزل الشركات وبقية معايير قصة العقود مفتوحة. ولا تدّعي هذه الشاشة اكتمال تكافؤ العقود.
USER GUIDEدليل المستخدم / 18

Plan project phases and crewخطط مراحل المشروع وفريقه

Use the project plan to group Odoo tasks into phases, set planned dates, assign internal crew and equipment, define task dependencies and review crew/equipment overlap warnings.استخدم خطة المشروع لتجميع مهام Odoo في مراحل وتحديد تواريخها المخططة وإسناد الفريق والمعدات وتعريف الاعتماديات ومراجعة تنبيهات تداخل الفريق والمعدات.

  1. Open Projects, then choose Project plan. Select a project visible to your Odoo role. The Bills of quantities tab remains available beside it.افتح المشاريع ثم اختر خطة المشروع. حدّد مشروعاً متاحاً لصلاحياتك في Odoo. تبقى علامة جداول الكميات متاحة بجوارها.
  2. Choose Add phase or task. Create a top-level task for a phase; choose a parent phase when adding a child task.اختر إضافة مرحلة أو مهمة. أنشئ مهمة رئيسية للمرحلة، وحدّد المرحلة الأم عند إضافة مهمة فرعية.
  3. Set both planned start and deadline, or leave both blank. If dependencies are disabled, an authorized project manager can enable them from the project plan; this setting is enabled in React and can only be disabled in Odoo administration. Add dependencies that must finish first, assign active internal team members and choose company equipment.حدّد تاريخ البداية والموعد النهائي معاً أو اتركهما فارغين. إذا كانت الاعتماديات معطلة، يستطيع مدير مشروع مخوّل تفعيلها من خطة المشروع؛ يمكن تفعيل هذا الإعداد في React، بينما يتم تعطيله من إدارة Odoo فقط. أضف الاعتماديات التي يجب إنجازها أولاً، وأسند أعضاء الفريق الداخلي النشطين واختر معدات الشركة.
  4. Save the task. Reopen it to revise its schedule, parent, dependencies or crew. Odoo checks the current project permissions and rejects stale edits.احفظ المهمة. أعد فتحها لتعديل الجدول أو المرحلة الأم أو الاعتماديات أو الفريق. يتحقق Odoo من صلاحيات المشروع الحالية ويرفض التعديلات القديمة.
  5. The timeline marks parent phases and late open tasks. The task list warns when a shared crew member overlaps another readable project, when equipment is scheduled on overlapping tasks, or when an asset is held by another project or in maintenance.يُظهر المخطط المراحل الرئيسية والمهام المفتوحة المتأخرة. تنبه قائمة المهام عند تداخل مواعيد عضو فريق مشترك مع مشروع آخر يمكن قراءته، أو عند جدولة المعدات في مهام متداخلة، أو عند وجود أصل في مشروع آخر أو تحت الصيانة.
  6. Record a schedule baseline to snapshot the current task dates, dependencies, assigned crew/equipment and stages. Add a rationale and submit. A different Build Engine owner or PM must approve or reject it with a reason; the requester cannot decide their own baseline. Review task creation, edits and deletion in Schedule change history. On an approved baseline, choose Compare with current schedule to review changed fields and added or removed tasks. This comparison is read-only.سجّل خط أساس للجدول لحفظ تواريخ المهام الحالية واعتمادياتها والفريق والمعدات والمراحل. أضف مبرراً ثم أرسل الطلب. يجب أن يعتمد مالك أو مدير مشروع آخر في Build Engine الطلب أو يرفضه مع ذكر السبب؛ ولا يمكن لمقدم الطلب اعتماد خط أساسه. راجع إنشاء المهام وتعديلها وحذفها في سجل تغييرات الجدول. في خط أساس معتمد، اختر مقارنة بالجدول الحالي لمراجعة الحقول المتغيرة والمهام المضافة أو المحذوفة. المقارنة للقراءة فقط.
This React schedule covers phase/task create/edit, planned-date timeline, crew overlap warnings, equipment assignment and equipment schedule/custody warnings. Immutable schedule baselines and approval history are live-verified through ordinary PM/owner roles in isolated QA; the screenshot below uses mocked APIs and shows a read-only comparison with one changed task, one addition and one removal. Warnings do not reserve or block resources. Per-project paths now use the active company work calendar; cross-project dependency paths, resource leveling, employee/project calendars, schedule float and remaining story criteria are open.يغطي جدول React إنشاء المراحل والمهام وتعديلها وعرض التواريخ المخططة وتنبيهات تداخل الفريق وإسناد المعدات وتنبيهات جدول المعدات وحيازتها. تم التحقق مباشرةً من خطوط أساس الجدول غير القابلة للتعديل وسجل الموافقات بأدوار مدير المشروع والمالك في بيئة اختبار معزولة؛ أما الصورة أدناه فتستخدم واجهات وهمية وتعرض مقارنة للقراءة فقط. لا تحجز التنبيهات الموارد أو تمنع إسنادها. تستخدم المسارات لكل مشروع تقويم عمل الشركة الحالي؛ ولا تزال الاعتماديات العابرة للمشاريع وموازنة الموارد وتقاويم الموظفين أو المشاريع والسماح الزمني وبقية معايير القصة مفتوحة.
USER GUIDEدليل المستخدم / 19

Maintain supplier contactsأدر جهات اتصال الموردين

Use the React supplier directory to search, create and maintain current-company contacts used in purchasing. Editing and archive actions use optimistic revisions; supplier qualification is a separate approval workflow and is not implied by these contact actions.استخدم دليل الموردين في React للبحث وإنشاء وإدارة جهات اتصال الشركة المستخدمة في المشتريات. تعتمد التعديلات والأرشفة على التحقق من الإصدار؛ ويظل تأهيل المورد سير موافقة مستقلاً ولا ينتج عن إدارة بيانات الاتصال.

  1. Open Purchase and choose Suppliers. Use Active, Archived or All to review the directory; search by name, email, VAT or commercial registration.افتح المشتريات ثم اختر الموردين. استخدم نشط أو مؤرشف أو الكل لمراجعة الدليل؛ وابحث بالاسم أو البريد أو الرقم الضريبي أو السجل التجاري.
  2. Choose New supplier to add a company contact. Enter the legal name and any available Arabic name, contact information, Saudi VAT number, commercial registration, region and national short address.اختر مورد جديد لإضافة جهة اتصال للشركة. أدخل الاسم النظامي وما يتوفر من الاسم العربي ومعلومات التواصل والرقم الضريبي والسجل التجاري والمنطقة والعنوان الوطني المختصر.
  3. Choose Edit beside a supplier to change its details. Odoo checks role, company scope, duplicate identifiers and the revision you opened; refresh if another user changed the supplier first.اختر تعديل بجانب المورد لتغيير بياناته. يتحقق Odoo من الدور ونطاق الشركة وتكرار المعرفات والإصدار الذي فتحته؛ حدّث البيانات إذا عدّل مستخدم آخر المورد أولاً.
  4. Choose Archive and confirm to remove the supplier from active purchasing selection lists. Existing purchase orders, bills and accounting history remain unchanged. Use Archived, then Restore to return the supplier to active lists.اختر أرشفة وأكد لإزالة المورد من قوائم الاختيار النشطة للمشتريات. تبقى أوامر الشراء والفواتير والسجلات المحاسبية السابقة دون تغيير. افتح المؤرشف ثم اختر استعادة لإرجاع المورد إلى القوائم النشطة.
  5. Supplier contact maintenance does not approve qualification or establish an approved-vendor status. Use the separately authorized qualification workflow when its policy is configured.إدارة بيانات اتصال المورد لا تعتمد التأهيل ولا تنشئ حالة مورد معتمد. استخدم سير التأهيل المنفصل والمصرح به عند إعداد سياسته.
The screenshot below uses mocked API data for the browser walkthrough. Qualification evidence, the supplier approval lifecycle and buyer-role live acceptance remain incomplete.تستخدم الصورة أدناه بيانات واجهة وهمية لاستعراض المتصفح. لا تزال أدلة التأهيل ودورة اعتماد المورد وقبول دور المشتري الفعلي غير مكتملة.
USER GUIDEدليل المستخدم / 20

Issue material from project stockصرف المواد من مخزون المشروع

Use Projects & BOQ → Material issues to consume stock held at a project site. Each validated issue is a native Odoo outgoing stock move linked to the project, product and confirmed material BOQ line. Its native project analytic cost is linked back to the BOQ actuals.استخدم المشاريع وجداول الكميات ← صرف المواد لاستهلاك المخزون الموجود في موقع المشروع. كل عملية صرف معتمدة هي حركة مخزون صادرة أصلية في Odoo ومرتبطة بالمشروع والمنتج وبند المواد المعتمد في جدول الكميات. وترتبط تكلفتها التحليلية الأصلية بفعلي جدول الكميات.

  1. Choose the project and one of its site stock locations. Available quantities are calculated for that exact location.اختر المشروع وأحد مواقع مخزونه. تُحسب الكميات المتاحة لهذا الموقع تحديداً.
  2. Choose a confirmed material BOQ line with a storable product. Review the available stock, enter the issue quantity and add a work note. For serial-tracked products, enter a whole number of units.اختر بند مواد معتمداً مرتبطاً بمنتج مخزني. راجع المخزون المتاح وأدخل كمية الصرف وملاحظة العمل. يجب إدخال عدد صحيح من الوحدات للمنتجات المتتبعة بالأرقام التسلسلية.
  3. Choose Confirm stock issue. Odoo reserves and validates the issue from the site location; lot and serial details are retained on stock move lines, together with the BOQ link and the actor, company and completion time.اختر تأكيد صرف المخزون. يحجز Odoo الكمية ويعتمد الصرف من موقع المشروع؛ ويحفظ تفاصيل الدفعات والأرقام التسلسلية على سطور حركة المخزون مع ارتباط جدول الكميات والمستخدم والشركة ووقت الاعتماد.
  4. Refresh the issue register to reopen the native stock reference and confirm the project, BOQ item, product, quantity, lot or serial, location and issue audit.حدّث سجل الصرف لإعادة فتح مرجع حركة المخزون الأصلية والتحقق من المشروع وبند جدول الكميات والمنتج والكمية والدفعة أو الرقم التسلسلي والموقع وسجل التدقيق.
  5. Open Bills of quantities to review the positive actual cost on the BOQ summary and material line. The source analytic entry retains Odoo’s signed outgoing value.افتح جداول الكميات لمراجعة التكلفة الفعلية الموجبة في ملخص الجدول وبند المواد. يحتفظ القيد التحليلي المصدر بإشارة الصرف الأصلية في Odoo.
  6. Actual cost follows the product stock valuation and the project analytic plan. Confirm the required valuation method and cost-recognition point with Finance; broader tenant and role acceptance remains in progress.تتبع التكلفة الفعلية تقييم مخزون المنتج والخطة التحليلية للمشروع. أكّد مع المالية طريقة التقييم وتوقيت إثبات التكلفة؛ ولا يزال قبول الأدوار والشركات الإضافية جارياً.
The React → authenticated BFF → Odoo live walkthrough verified the native signed analytic cost, positive BOQ actual, lot and BOQ links, project/company, actor/time and remaining site quantity. A disposable QA database was dropped. Stock valuation policy and overall construction parity remain open.تحقق اختبار معزول عبر React ثم BFF الموثق ثم Odoo من صرف الدفعات وإرجاعها وصرف وحدتين برقمين تسلسليين ثم إعادة أحدهما، ومن التكلفة التحليلية الأصلية وصافي الفعلي وروابط الأرقام التسلسلية والبند والمشروع والشركة والمستخدم والوقت ورصيد الموقع. حُذفت قاعدة QA المؤقتة. لا تزال سياسة تقييم المخزون والتكافؤ الكامل لنظام البناء قيد الاستكمال.
USER GUIDEدليل المستخدم / 21

Count site stock and review variancesجرد مخزون الموقع ومراجعة الفروقات

Use Stock Counts to record the physical balance at a project yard. A Stock Officer submits the count and a different Stock Manager reviews and applies or rejects its variance through native Odoo inventory adjustment.استخدم جرد المخزون لتسجيل الرصيد الفعلي في ساحة المشروع. يرسل مسؤول المخزون نتيجة الجرد، ثم يراجع مدير مخزون مختلف الفروقات ويعتمدها أو يرفضها عبر تسوية المخزون الأصلية في Odoo.

  1. Open Stock Counts and choose a project and one of its project stock locations. Current Odoo balances appear by product and lot or serial.افتح جرد المخزون واختر المشروع وأحد مواقع مخزونه. تظهر أرصدة Odoo الحالية حسب المنتج والدفعة أو الرقم التسلسلي.
  2. Enter the physical quantity for each displayed balance. Values must be between zero and 1,000,000; serial tracked products accept only zero or one. Invalid values show an error beside the field.أدخل الكمية الفعلية لكل رصيد ظاهر. يجب أن تكون القيمة بين صفر و1,000,000؛ ويقبل المنتج المتتبع برقم تسلسلي صفراً أو واحداً فقط. تظهر رسالة الخطأ بجانب الحقل.
  3. Add an optional shift or zone note and choose Submit for review. Odoo stores the quant snapshot, expected quantity, count variance, company, project, counter and timestamp.أضف ملاحظة اختيارية للوردية أو المنطقة ثم اختر الإرسال للمراجعة. يحفظ Odoo لقطة رصيد المخزون والكمية المتوقعة والفرق والشركة والمشروع ومنفذ الجرد والوقت.
  4. A different Stock Manager opens the pending count. Approve & apply posts the variance through Odoo inventory adjustment; Reject requires a reason. The counter cannot approve their own count.يفتح مدير مخزون مختلف عملية الجرد المعلقة. يؤدي الاعتماد والتطبيق إلى ترحيل الفرق من خلال تسوية المخزون في Odoo؛ ويتطلب الرفض سبباً. لا يمكن لمنفذ الجرد اعتماد عمليته.
  5. Refresh the register to reopen the status, variance, project/location, counter and reviewer audit. A changed stock balance after the count was captured blocks approval until a recount.حدّث السجل لإعادة فتح الحالة والفرق والمشروع والموقع وسجل منفذ الجرد والمراجع. يمنع تغير رصيد المخزون بعد تسجيل الجرد الاعتماد حتى إعادة الجرد.
Live isolated QA verified a Warehouse Officer count, independent Stock Manager approval, audit timestamps and native on-hand change from 30 to 27. Stock counts only list quant balances already present at the selected location; discovering new products or creating missing lot/serial balances is not part of this screen yet.تحقق اختبار حي معزول من جرد مسؤول المخزون واعتماد مدير مختلف وسجل التدقيق وتغيير الرصيد الأصلي من 30 إلى 27. يعرض الجرد أرصدة المخزون المسجلة مسبقاً في الموقع المحدد؛ ولا يشمل حالياً اكتشاف منتجات جديدة أو إنشاء أرصدة دفعات أو أرقام تسلسلية مفقودة.
USER GUIDEدليل المستخدم / 22

Set project stock minimums and alertsتحديد الحد الأدنى للمخزون وتنبيهاته

Use Reorder Rules to maintain Odoo’s native minimum-stock policy for a project site. Stock Managers configure the product and thresholds; Stock Users can view forecast shortages, suggested quantities, supply warnings and the audit trail.استخدم قواعد إعادة التوريد لإدارة الحد الأدنى الأصلي للمخزون في موقع المشروع ضمن Odoo. يضبط مدير المخزون المنتج والحدود؛ ويمكن لمستخدم المخزون متابعة العجز المتوقع والكمية المقترحة وتنبيهات التوريد وسجل التدقيق.

  1. Open Reorder Rules and filter by the project whose site stock you manage. Choose New rule.افتح قواعد إعادة التوريد وصفّ حسب المشروع الذي تدير مخزونه، ثم اختر قاعدة جديدة.
  2. Choose the project, its internal stock location and a storable product. Enter a minimum and target maximum; the maximum cannot be lower than the minimum.اختر المشروع وموقع مخزونه الداخلي ومنتجاً مخزنياً. أدخل الحد الأدنى والحد المستهدف؛ ولا يمكن أن يقل الحد الأقصى عن الأدنى.
  3. Save the rule. Odoo stores a native minimum inventory rule for the company, product and project location. The rule keeps its creator and last-updated user/time.احفظ القاعدة. يخزن Odoo قاعدة الحد الأدنى الأصلية للشركة والمنتج وموقع المشروع، مع اسم المنشئ وآخر مستخدم ووقت تحديث.
  4. Review on-hand, forecast, minimum/target, suggested quantity, deadline and supply warning. Use Below minimum to focus on forecast shortages.راجع الرصيد المتاح والتوقع والحد والكمية المستهدفة والكمية المقترحة والموعد وتنبيه التوريد. استخدم دون الحد الأدنى للتركيز على العجز المتوقع.
  5. Archive a rule when it is no longer active; restore it from the Archived filter when it is needed again. Suggested quantities do not create a purchase order. Continue through the normal purchase-request approval flow.أرشف القاعدة عند توقفها، واستعدها من تصفية المؤرشف عند الحاجة. لا تنشئ الكميات المقترحة أمر شراء؛ تابع عبر مسار اعتماد طلب الشراء المعتاد.
A live isolated QA run verified a manager-created Odoo orderpoint for project stock with 3 units on hand, forecast 3, minimum 5, target 12 and suggested replenishment 9. A Warehouse Officer could see the alert but could not configure rules. No purchase order was generated.تحقق اختبار حي معزول من قاعدة Odoo أنشأها مدير المخزون لموقع مشروع: المتاح 3 وحدات والتوقع 3 والحد الأدنى 5 والمستهدف 12 والكمية المقترحة 9. شاهد مسؤول المخزون التنبيه ولم يتمكن من ضبط القاعدة. لم يُنشأ أمر شراء.
USER GUIDEدليل المستخدم / 23

Configure inspection templates in Reactاضبط قوالب الفحص في React

Build Engine owners can manage company quality templates in the React Quality & Safety workspace. Drafts define the project type, checklist kind, required items, evidence and sign-off role. Publishing freezes the version; create a draft version to make future changes.يمكن لمالكي Build Engine إدارة قوالب الجودة للشركة من مساحة الجودة والسلامة في React. تحدد المسودة نوع المشروع والقائمة وبنود الفحص المطلوبة والأدلة ودور الاعتماد. يثبت النشر الإصدار؛ أنشئ مسودة إصدار جديدة للتعديلات اللاحقة.

  1. Open Quality & Safety → Inspections & checklists, then choose Manage templates. This control is available to the Build Engine owner role.افتح الجودة والسلامة ← الفحوصات وقوائم التحقق ثم اختر إدارة القوالب. يظهر هذا الإجراء لدور مالك Build Engine.
  2. Choose New template. Enter a name, unique company code, project type and checklist kind. Add each inspection item and choose whether it is required, what evidence it needs and which role signs it.اختر قالباً جديداً. أدخل الاسم ورمز الشركة الفريد ونوع المشروع والقائمة. أضف بنود الفحص وحدد ما إذا كان البند مطلوباً ونوع الدليل ودور الاعتماد.
  3. Save draft and reopen it from the template register. Review company, state, version, last editor and Riyadh timestamp before publishing. Invalid items are reported with their field path; Odoo commits the template as one transaction.احفظ المسودة ثم أعد فتحها من سجل القوالب. راجع الشركة والحالة والإصدار وآخر محرر ووقت الرياض قبل النشر. تظهر البنود غير الصالحة مع مسار الحقل؛ ويحفظ Odoo القالب كمعاملة واحدة.
  4. Choose Publish template to freeze the current version. For a later change, open the published template and choose Create draft version; the item text is copied without modification.اختر نشر القالب لتثبيت الإصدار الحالي. لإجراء تغيير لاحق، افتح القالب المنشور واختر إنشاء إصدار مسودة؛ وتُنسخ نصوص البنود كما هي.
  5. Checklist templates are company-scoped and selected for projects by their project type and workflow. Only the owner role can currently configure them; confirmation of quality-officer permissions remains open.قوالب الفحص خاصة بالشركة وتُحدد للمشاريع حسب نوع المشروع وسير العمل. يقتصر ضبطها حالياً على دور المالك؛ ولا يزال اعتماد صلاحيات مسؤول الجودة مفتوحاً.
The live isolated QA journey created and edited a draft, published version 1, reopened its company/editor/timestamp, created draft version 2 with unchanged checklist text, and confirmed that a Site role has no template controls. Template-to-project binding and quality-officer configuration policy remain open.أنشأ اختبار QA الحي المعزول مسودة وعدلها ونشر الإصدار الأول ثم أعاد فتح الشركة والمحرر والوقت وأنشأ الإصدار الثاني بنصوص فحص مطابقة، كما تحقق من عدم ظهور أدوات الإعداد لدور الموقع. لا يزال ربط القالب بمشروع محدد وسياسة مسؤول الجودة مفتوحين.
USER GUIDEدليل المستخدم / 24

Record an inspection result in Reactسجّل نتيجة الفحص في React

Authorized site, project-manager and owner roles can sign their assigned inspection items. A failure requires a reason; signed results, signer, time and reason remain fixed in Odoo.يمكن للأدوار المخولة في الموقع وإدارة المشروع والمالك اعتماد بنود الفحص المسندة إليها. يتطلب الإخفاق سبباً؛ وتبقى النتيجة والمستخدم والوقت والسبب المسجل في Odoo ثابتة.

  1. Open Quality & Safety → Inspections & checklists and select a project checklist. Review the project, stage, required evidence and sign-off role.افتح الجودة والسلامة ← الفحوصات وقوائم التحقق واختر قائمة مشروع. راجع المشروع والمرحلة والدليل المطلوب ودور الاعتماد.
  2. Attach the required evidence before passing an item. A failed item can be recorded without a pass-evidence attachment, but you must enter a clear failure reason.أرفق الدليل المطلوب قبل اجتياز البند. يمكن تسجيل إخفاق دون مرفق دليل الاجتياز، لكن يجب إدخال سبب واضح.
  3. Choose Fail, enter the reason and choose Record failure. The gate status updates, and the failure reason appears with the signer and Riyadh timestamp.اختر إخفاق، وأدخل السبب، ثم اختر تسجيل الإخفاق. تتحدث حالة البوابة ويظهر سبب الإخفاق مع اسم المعتمد ووقت الرياض.
  4. After a sign-off, the item controls are removed. Reopening the checklist shows the same result and audit details; attempts to replace the signature or add evidence are rejected by Odoo.بعد الاعتماد تختفي أدوات تعديل البند. يعرض فتح القائمة مجدداً النتيجة وبيانات التدقيق نفسها؛ ويرفض Odoo استبدال الاعتماد أو إضافة دليل جديد.
The isolated live React → BFF → Odoo journey recorded a failure with its required reason and reopened the checklist to verify state and signer. Native Odoo tests reject repeat signing, direct signature edits and post-signature evidence changes. Retention policy and legal meaning of the electronic signature remain open.سجل اختبار حي معزول عبر React وBFF وOdoo إخفاقاً مع سببه المطلوب، ثم أعاد فتح القائمة للتحقق من الحالة والمعتمد. ترفض اختبارات Odoo إعادة الاعتماد والتعديل المباشر وإضافة دليل بعد الاعتماد. لا تزال سياسة الاحتفاظ والمعنى القانوني للتوقيع الإلكتروني مفتوحة.
USER GUIDEدليل المستخدم / 25

Review material request fulfillmentراجع تنفيذ طلب المواد

Material request lines show the requested quantity beside the quantity on purchase orders, quantity received into stock and quantity still outstanding. These figures come from the native OCA Purchase Request allocations and update after receipt validation.تعرض بنود طلب المواد الكمية المطلوبة والكمية المدرجة في أوامر الشراء والكمية المستلمة في المخزون والكمية المتبقية. تأتي الأرقام من تخصيصات طلبات الشراء الأصلية في OCA وتتحدث بعد اعتماد الاستلام.

  1. Open Purchase → Material requests and find the request by its reference, description or product.افتح المشتريات ← طلبات المواد وابحث عن الطلب بالمرجع أو الوصف أو المنتج.
  2. For each displayed line, compare Requested with Ordered, Received and Outstanding. Ordered is sourced from linked non-cancelled purchase lines; Received and Outstanding follow the OCA request allocation and receipt quantities.قارن لكل بند بين المطلوب والمطلوب شراؤه والمستلم والمتبقي. تأتي كمية الشراء من بنود أوامر الشراء غير الملغاة؛ وتعكس الكميتان المستلمة والمتبقية تخصيصات OCA وكميات الاستلام.
  3. After Stock validates a partial receipt, choose Refresh requests. The request shows the received quantity and its new outstanding balance; create a further RFQ only for the remaining approved amount.بعد اعتماد المخزون لاستلام جزئي، اختر تحديث الطلبات. يعرض الطلب الكمية المستلمة والرصيد المتبقي الجديد؛ وأنشئ طلب عرض إضافياً للكمية المعتمدة المتبقية فقط.
An isolated live React → BFF → Odoo run reopened a request for 8 units after native OCA approval, RFQ creation, PO confirmation and receipt of 3 units. React displayed 8 ordered, 3 received and 5 outstanding; native verification confirmed the same figures and company.أعاد اختبار حي معزول عبر React وBFF وOdoo فتح طلب لثماني وحدات بعد اعتماد OCA وإنشاء طلب عرض وتأكيد أمر الشراء واستلام ثلاث وحدات. عرض React ثماني وحدات مطلوبة للشراء وثلاثاً مستلمة وخمساً متبقية؛ وأكد Odoo الأرقام والشركة نفسها.
USER GUIDEدليل المستخدم / 26

Compare and flag supplier quotesقارن عروض الموردين وسجّل الملاحظات

Purchase users can compare open supplier alternatives for a confirmed project material BOQ line. Landed unit price, peer median and variance help the buyer identify a quote for human review; the comparison never selects a supplier automatically.يمكن لمستخدمي المشتريات مقارنة عروض الموردين المفتوحة لبند مواد معتمد في جدول كميات المشروع. تساعد تكلفة الوحدة الواصلة ووسيط العروض والفارق على تحديد عرض يحتاج إلى مراجعة بشرية؛ ولا يختار النظام مورداً تلقائياً.

  1. Open Purchase → Quote review. Search by project, product or supplier if needed.افتح المشتريات ← مراجعة العروض. ابحث حسب المشروع أو المنتج أو المورد عند الحاجة.
  2. Review the landed price, peer median, difference, delivery date and number of comparable offers. Estimates use the current company currency and allocated estimated fees.راجع التكلفة الواصلة ووسيط العروض والفارق وموعد التسليم وعدد العروض المقارنة. تستخدم التقديرات عملة الشركة الحالية والرسوم التقديرية الموزعة.
  3. Choose Flag for review and enter a reason of at least 10 characters. Save review flag records the quote for a human decision; it does not confirm an order or award the supplier.اختر تسجيل للمراجعة وأدخل سبباً لا يقل عن ١٠ أحرف. يحفظ تسجيل المراجعة العرض ليقرره شخص؛ ولا يؤكد أمر الشراء أو يرسي على المورد.
  4. The Human review history shows the saved quote, project, BOQ item, reason, author and time. Sign out and back in to verify that the audit entry remains available.يعرض سجل المراجعة البشرية العرض المحفوظ والمشروع وبند جدول الكميات والسبب والمستخدم والوقت. سجّل الخروج ثم الدخول للتحقق من بقاء سجل التدقيق.
  5. Quotes appear only when a Purchase user can access the current company, project and confirmed material BOQ line, and at least one comparable alternative is available.تظهر العروض فقط لمستخدم مشتريات لديه صلاحية للشركة والمشروع وبند المواد المعتمد، مع توفر عرض بديل واحد على الأقل.
The screenshots show a live isolated QA journey. Its sample company uses USD; the configured currency of a live company is used by the feature. The disposable QA database was removed after verification, so these screenshots are not records in the demo database. BE-064 remains partial while field-level validation feedback and wider project/company privacy acceptance are verified.تُظهر الصور اختباراً حياً معزولاً. عملة الشركة التجريبية فيه الدولار؛ وتستخدم الميزة عملة الشركة الفعلية المضبوطة. حُذفت قاعدة الاختبار المؤقتة بعد التحقق، لذلك لا تمثل هذه الصور سجلات في قاعدة العرض لديك. تظل BE-064 جزئية إلى حين التحقق من رسائل التحقق التفصيلية وقبول خصوصية المشروع والشركة على نطاق أوسع.
USER GUIDEدليل المستخدم / 27

Track project punch items to closeoutتابع ملاحظات المشروع حتى الإغلاق

Use the React Punch list tab to capture a remaining defect by project and exact location, assign an owner and due date, record corrective work, then require another project manager to verify it before closeout.استخدم تبويب قائمة الإقفال في React لتسجيل العيب المتبقي مع المشروع والموقع، وتعيين مسؤول وموعد استحقاق، وتوثيق العمل التصحيحي، ثم اطلب من مدير مشروع آخر التحقق قبل الإغلاق.

  1. Open Quality & Safety → Punch list. The register is scoped by your Odoo company and project access.افتح الجودة والسلامة ← قائمة الإقفال. يخضع السجل لصلاحيات الشركة والمشروع في Odoo.
  2. Create an item with a clear title, project, location, description, priority and due date. Odoo assigns the company and reporter from the authenticated session.أنشئ ملاحظة بعنوان واضح ومشروع وموقع ووصف وأولوية وموعد استحقاق. يحدد Odoo الشركة والمبلّغ من جلسة الدخول.
  3. A project manager assigns an internal project user and confirms the due date. The assignment actor and time are retained in Odoo.يعيّن مدير المشروع مستخدماً داخلياً لديه صلاحية للمشروع ويؤكد موعد الاستحقاق. يحفظ Odoo اسم من أسند العمل ووقت الإسناد.
  4. The assigned user starts work and records the corrective work when finished. A different project manager verifies the repair and closes the item. Closed history cannot be edited or deleted.يبدأ المستخدم المعيّن العمل ثم يوثّق الإجراء التصحيحي عند إنجازه. يتحقق مدير مشروع آخر من الإصلاح ويغلق الملاحظة. لا يمكن تعديل سجل الإغلاق أو حذفه.
  5. Attach PNG, JPEG, WebP or PDF evidence up to 3 MB per file. Odoo archives are blocked until every punch item is closed; close each item only after independent verification.أرفق صور PNG أو JPEG أو WebP أو ملفات PDF بحجم يصل إلى 3 ميغابايت للملف. يمنع Odoo أرشفة المشروع حتى إغلاق جميع الملاحظات؛ لا تغلق الملاحظة إلا بعد التحقق المستقل.
The closed-item screenshot shows the React detail reopened after an isolated live Site/Project Manager workflow. Odoo verified its linked evidence and immutable actor/time history. Formal closeout certification blocks until open punch items are closed; its broader approval/evidence policy remains under DEC-21.تعرض صورة الملاحظة المغلقة تفاصيل React بعد سير عمل مباشر ومعزول للموقع ومدير المشروع. تحقق Odoo من الدليل المرتبط وسجل المستخدمين والأوقات الثابت. تمنع شهادة إغلاق المشروع حتى إغلاق جميع الملاحظات؛ وتبقى سياسة الاعتماد والأدلة الأوسع ضمن DEC-21.
USER GUIDEدليل المستخدم / 28

Configure project lifecycle stagesأعد مراحل دورة حياة المشروع

Build Engine owners can maintain project lifecycle templates in React. Published versions are locked; edits start from a new draft version so existing project process definitions remain reviewable.يستطيع مالكو Build Engine إدارة قوالب دورة حياة المشروع في React. تُقفل النسخ المنشورة؛ وتبدأ التعديلات من مسودة إصدار جديد للحفاظ على مراجعة تعريفات الإجراءات السابقة.

  1. Open Projects & BOQ → Lifecycle setup. Choose New template and enter a name and a unique template code.افتح المشاريع وجداول الكميات ← إعداد دورة الحياة. اختر قالباً جديداً وأدخل الاسم ورمزاً فريداً للقالب.
  2. Add the stages in the intended order. Mark exactly one stage as Start and at least one stage as Complete; choose Fold for stages that should collapse in a project kanban.أضف المراحل حسب الترتيب المطلوب. حدد مرحلة بداية واحدة فقط ومرحلة اكتمال واحدة على الأقل؛ واختر طي للمراحل التي تريد إخفاءها في لوحة المشروع.
  3. Add allowed transitions between different stages. A transition may use a validated Odoo condition and no approval, a Build Engine role, a current-company Odoo group or one or more named internal users. Group and user choices show only active internal users in the current company. Save the graph as a draft and review the stage/transition diagram.أضف الانتقالات المسموحة بين مراحل مختلفة. يمكن أن يتضمن الانتقال شرط Odoo متحققاً منه، أو بلا موافقة، أو موافقة دور Build Engine، أو مجموعة Odoo بالشركة الحالية، أو مستخدم داخلي محدد. تظهر المجموعات والمستخدمون النشطون في الشركة الحالية فقط. احفظ المخطط كمسودة وراجع رسم المراحل والانتقالات.
  4. Choose Publish only after reviewing the graph. Odoo locks the published version. To change it, choose New version, edit the copied draft and publish that version after review.اختر نشر بعد مراجعة المخطط. يقفل Odoo النسخة المنشورة. لتغييرها، اختر نسخة جديدة وعدّل المسودة المنسوخة ثم انشرها بعد المراجعة.
  5. Open Project type assignments. Project managers and owners can create a company project type and assign a published lifecycle. New projects of that type inherit the selected lifecycle; existing projects are unchanged.افتح تعيينات أنواع المشاريع. يستطيع مديرو المشاريع والمالكون إنشاء نوع مشروع للشركة وربطه بدورة حياة منشورة. ترث المشاريع الجديدة من هذا النوع دورة الحياة المحددة، ولا تتغير المشاريع القائمة.
  6. Only Build Engine owners and administrators can create, edit, publish or version templates and configure approval sources. Group and named-user choices are checked against active internal users in the current company. Project managers can read templates and assign published versions.يقتصر إنشاء القوالب وتعديلها ونشرها وإصدار نسخها وإعداد مصادر الاعتماد على مالكي Build Engine والمسؤولين. تتحقق المجموعات والمستخدمون المحددون من الانتماء إلى الشركة الحالية ومن كونهم مستخدمين داخليين نشطين. يستطيع مديرو المشاريع عرض القوالب وتعيين النسخ المنشورة.
The screenshots show the live React lifecycle editor and project-type assignment flow on a disposable Odoo QA clone. Native verification confirmed that a new project inherits its selected type lifecycle. The clone was dropped after verification; role, group and named-user approval choices are verified; ordinary-role acceptance and remaining BE-044 criteria are still open.تُظهر الصور محرر دورة الحياة في React وتعيينها لأنواع المشاريع في اختبار Odoo معزول. أكد التحقق الأصلي أن المشروع الجديد يرث دورة حياة نوعه المحددة. حُذفت قاعدة الاختبار بعد التحقق؛ تم التحقق من موافقات الأدوار والمجموعات والمستخدمين المحددين؛ ولا يزال قبول الأدوار العادية وبقية معايير BE-044 مفتوحاً.
USER GUIDEدليل المستخدم / 29

Escalate a safety incident or overdue inspectionصعّد واقعة سلامة أو فحصاً متأخراً

React lets an authorized site user send an open safety incident, overdue corrective action or overdue daily safety checklist to a same-company Owner or Project Manager. Odoo records who escalated it, when, the reason and recipient, then creates a native activity and a chatter entry.يتيح React لمستخدم الموقع المخوّل تصعيد واقعة سلامة مفتوحة أو إجراء تصحيحي متأخر أو قائمة سلامة يومية متأخرة إلى مالك أو مدير مشروع في الشركة نفسها. يسجل Odoo من قام بالتصعيد ووقته وسببه ومستلمه، ثم ينشئ نشاطاً أصلياً ورسالة في سجل المحادثات.

  1. Open Quality & Safety → Findings & safety, select an eligible open incident or overdue corrective action, then choose Manage. For a daily checklist, open Daily safety and select a pending checklist dated before today.افتح الجودة والسلامة ← الملاحظات والسلامة، واختر واقعة مؤهلة مفتوحة أو إجراءً تصحيحياً متأخراً ثم اختر إدارة. لقائمة يومية افتح السلامة اليومية واختر قائمة معلّقة بتاريخ يسبق اليوم.
  2. Choose an Owner or Project Manager who has access to the same project and company. Enter a reason of at least 10 characters and choose Raise escalation.اختر مالكاً أو مدير مشروع لديه صلاحية للمشروع والشركة نفسيهما. أدخل سبباً لا يقل عن ١٠ أحرف ثم اختر إرسال التصعيد.
  3. The selected recipient receives an Odoo activity. The escalation history shows the recipient, raiser, time and saved reason. Escalation entries cannot be edited or deleted.يتلقى المستلم المحدد نشاطاً في Odoo. يعرض سجل التصعيد المستلم والمبلّغ والوقت والسبب المحفوظ. لا يمكن تعديل سجل التصعيد أو حذفه.
  4. Only unresolved safety findings, overdue corrective actions and pending past-date daily safety checklists can be escalated. A current or completed inspection is not eligible.لا يمكن تصعيد إلا ملاحظات السلامة غير المحلولة أو الإجراءات التصحيحية المتأخرة أو قوائم السلامة اليومية المعلّقة ذات التاريخ السابق. لا يمكن تصعيد فحص حالي أو مكتمل.
  5. Owner approval of response deadlines, severity tiers and automatic repeat escalation is still pending. The screenshot is a mocked React/BFF walkthrough; no escalation was created in the connected demo.لا يزال اعتماد المالك لمهل الاستجابة ودرجات الخطورة والتصعيد الآلي المتكرر قيد الانتظار. الصورة مثال React/BFF وهمي؛ ولم يُنشأ أي تصعيد في العرض المتصل.
BE-107 is PARTIAL. Routing and timing remain provisional under DEC-20; confirm the contractor policy before relying on escalation as an SLA.تظل BE-107 جزئية. قواعد التوجيه والوقت مؤقتة وفق DEC-20؛ يجب اعتماد سياسة المقاول قبل اعتبار التصعيد اتفاقية مستوى خدمة.
USER GUIDEدليل المستخدم / 30

Report equipment breakdowns and repair costsسجّل أعطال المعدات وتكاليف إصلاحها

Use the React Maintenance workspace to report corrective work against company equipment, track its project and repair state, and keep itemized repair-cost entries with Odoo audit history.استخدم مساحة الصيانة في React لتسجيل أعمال الإصلاح للمعدات التابعة للشركة، ومتابعة المشروع والحالة، وحفظ بنود تكاليف الإصلاح مع سجل التدقيق في Odoo.

  1. Open Maintenance and choose Report breakdown. Select active equipment, enter an issue title and description, assign an active maintenance team, set the schedule, estimated duration and priority, then create the work order. Odoo derives company and current project from the authenticated company and equipment custody; do not enter another company or project.افتح الصيانة واختر تسجيل عطل. حدّد معدة نشطة، وأدخل عنوان العطل ووصفه، وأسند فريق صيانة نشطاً، وحدد الموعد والمدة التقديرية والأولوية، ثم أنشئ أمر العمل. يستمد Odoo الشركة والمشروع الحالي من الشركة المسجلة وعهدة المعدة؛ لا تدخل شركة أو مشروعاً آخر.
  2. The corrective work-order register shows equipment, company, readable project, state, reporter and creation time, plus the last updater and time. Authorized maintenance managers can complete, cancel or reopen a corrective order. Refresh the workspace to confirm saved changes.يعرض سجل أوامر العمل التصحيحية المعدة والشركة والمشروع المسموح بعرضه والحالة والمبلّغ ووقت الإنشاء وآخر من حدّث السجل ووقت التحديث. يستطيع مديرو الصيانة المخولون إكمال الأمر أو إلغاءه أو إعادة فتحه. حدّث مساحة العمل للتحقق من حفظ التغييرات.
  3. Choose Costs on a work order to review recorded entries and the company-currency total. An authorized cost recorder can add labor, parts/materials, external service or other costs with date, quantity, unit amount and optional reference. Entries are immutable; use a separate correction entry to adjust the total.اختر التكاليف في أمر العمل لمراجعة البنود المسجلة والإجمالي بعملة الشركة. يستطيع مسجل التكاليف المخول إضافة العمالة أو القطع والمواد أو الخدمات الخارجية أو غيرها مع التاريخ والكمية وسعر الوحدة ومرجع اختياري. لا تُعدّل البنود بعد حفظها؛ أضف بند تصحيح مستقلاً لتعديل الإجمالي.
  4. When the work order has a project with an analytic account and your Odoo account can read journal items, use Link a posted vendor bill. Choose an expense line already tagged to that project and allocate only the remaining quantity. This links the repair-cost ledger to its posted accounting source; it does not create another journal entry.عندما يرتبط أمر العمل بمشروع له حساب تحليلي ويملك حساب Odoo صلاحية قراءة القيود، استخدم ربط فاتورة مورد مرحلة. اختر بند مصروف مرتبطاً بالمشروع وخصّص الكمية المتبقية فقط. يربط ذلك سجل تكلفة الإصلاح بمصدره المحاسبي المرحل ولا ينشئ قيداً إضافياً.
  5. When issuing material from a project BOQ, you can optionally select an open corrective work order for the same project. Odoo copies the exact stock valuation into the repair ledger after issue validation. When unused material is returned, Odoo adds a linked negative correction so the work-order total reflects net consumption. The work-order link is optional; project issues without it keep their existing behavior.عند صرف مادة من جدول كميات المشروع، يمكنك اختيار أمر إصلاح تصحيحي مفتوح للمشروع نفسه. ينسخ Odoo قيمة المخزون الفعلية إلى سجل الإصلاح بعد اعتماد الصرف. وعند إعادة المواد غير المستخدمة، يضيف Odoo تصحيحاً سالباً مرتبطاً ليعكس إجمالي أمر العمل صافي الاستهلاك. ربط أمر العمل اختياري؛ وتستمر عمليات صرف المشروع بدونه كما هي.
  6. Cost access depends on the Odoo role: Owners, Project Managers and equipment managers can record; Finance can review; Site users do not see cost amounts. A user must also have access to the current company and work order.تخضع التكاليف لصلاحيات Odoo: يستطيع المالك ومدير المشروع ومدير المعدات تسجيلها؛ ويستطيع قسم المالية مراجعتها؛ ولا تظهر مبالغ التكاليف لمستخدمي الموقع. يجب أن يملك المستخدم أيضاً صلاحية للشركة الحالية وأمر العمل.
  7. Isolated QA screenshots show a posted project bill line allocated to a repair order for SAR 300 and a linked stock issue/return ledger with SAR 240 issued, SAR 80 reversed and SAR 160 net repair cost. They come from disposable Odoo QA clones and do not show shared customer records.تعرض صور الاختبار المعزولة بند فاتورة مشروع مرحلاً بقيمة 300 ريال، وسجل صرف وإعادة مرتبطاً بأمر إصلاح: 240 ريالاً مصروفة و80 ريالاً معكوسة وصافي تكلفة 160 ريالاً. مصدرها قواعد Odoo معزولة ولا تعرض سجلات عملاء فعلية.
BE-097 remains PARTIAL while broader actual-cost reconciliation, the alignment of stock issues that are not linked to a corrective work order, and remaining role/company acceptance are unverified. Screenshot evidence comes from disposable Odoo QA clones and does not show shared customer records.تظل BE-097 جزئية حتى اكتمال المطابقة الأوسع للتكاليف الفعلية، ومواءمة عمليات صرف المخزون غير المرتبطة بأوامر الإصلاح، والتحقق المتبقي من الصلاحيات والشركات. مصدر الصور قواعد Odoo معزولة للاختبار ولا تعرض سجلات عملاء فعلية.
USER GUIDEدليل المستخدم / 30

Draft a technical proposal from a customer templateأعد مسودة عرض فني من نموذج العميل

Sales can draft a source-cited technical response from a CRM opportunity. Odoo stores it as a pending suggestion for human review.يمكن للمبيعات إعداد رد فني مستند إلى مصادر من فرصة CRM. يحفظه Odoo كمقترح بانتظار المراجعة البشرية.

  1. Open CRM and choose the opportunity linked to the customer organization. Open Technical proposal · customer template.افتح CRM واختر الفرصة المرتبطة بالعميل، ثم افتح العرض الفني · نموذج العميل.
  2. Enter the customer template name, paste the relevant template text, and list every required heading on its own line in the original order. File upload and PDF extraction are not available in this workflow.أدخل اسم نموذج العميل، والصق النص المطلوب، واكتب كل عنوان في سطر مستقل وبترتيبه الأصلي. لا يتوفر رفع الملفات أو استخراج PDF في هذا المسار.
  3. Choose Draft technical proposal. Review the generated responses, assumptions, exclusions, information gaps and source IDs. The app keeps the exact headings supplied in the form.اختر إعداد مسودة العرض الفني. راجع الردود والافتراضات والاستثناءات والمعلومات الناقصة ومعرّفات المصادر. يحتفظ التطبيق بالعناوين كما أُدخلت.
  4. The pending draft can be reopened from the opportunity. It does not create or approve a quotation and does not contact the customer.يمكن إعادة فتح المسودة المعلقة من الفرصة. لا تنشئ عرض سعر ولا تعتمده ولا تتواصل مع العميل.
Use a Sales/Owner account with access to the active company and opportunity. Template file intake, Arabic quality checks and full proposal approval remain open.استخدم حساب مبيعات أو مالك يملك صلاحية الشركة والفرصة الحالية. لا يزال رفع القوالب وتقييم جودة العربية واعتماد العرض الكامل قيد التنفيذ.
USER GUIDEدليل المستخدم / 31

Export a saved project archiveصدّر حزمة محفوظة للمشروع

A Project Manager can export the existing approved proposal and confirmed BOQ archive as a private ZIP, then reopen the Odoo-backed export history.يمكن لمدير المشروع تصدير أرشيف العرض المعتمد ونسخة جدول الكميات المؤكدة كملف ZIP خاص، ثم مراجعة سجل التصدير المحفوظ في Odoo.

  1. Open Projects & BOQ, then Proposal archive. Select a project you can access in the active company.افتح المشاريع وجدول الكميات، ثم أرشيف العروض. اختر مشروعاً تملك صلاحية الوصول إليه في الشركة الحالية.
  2. For a saved approved proposal + BOQ pack, enter an export rationale of 10–2,000 characters and choose Export project pack ZIP.لحزمة محفوظة من عرض معتمد وجدول كميات، أدخل سبب التصدير بطول 10 إلى 2000 حرف واختر تصدير حزمة المشروع ZIP.
  3. Review the saved export history, actor, time, project/company and checksum. Download ZIP retrieves the immutable saved package.راجع سجل التصدير المحفوظ والمنفذ والتاريخ والمشروع والشركة وبصمة التحقق. ينزّل رابط ZIP الحزمة المحفوظة الثابتة.
  4. The ZIP contains approved-proposal.pdf, confirmed-boq-baseline.pdf, attached issued/superseded drawing files, attachments from immutable approved submittal revisions, files linked directly to the project record and manifest.json with source IDs/revisions/approval time/checksums. Draft drawings and pending/rejected submittals are excluded. It is an internal record and does not email or publish documents.يحتوي ZIP على approved-proposal.pdf وconfirmed-boq-baseline.pdf ورسومات المشروع الصادرة أو المستبدلة ومرفقات إصدارات مستندات التقديم المعتمدة وmanifest.json بمعرّفات المصادر والإصدارات وأوقات الاعتماد وبصمات التحقق. تُستبعد المسودات والتقديمات غير المعتمدة. وهو سجل داخلي ولا يرسل المستندات أو ينشرها.
This feature passed live acceptance on an isolated Odoo QA clone; it is not enabled in the shared namaa_ksa demo database yet. The package includes approved submittal revision files and binary attachments linked directly to the project record. OCA directory-managed DMS files and knowledge items remain outside it pending DMS ACL repair. Use a Project Manager/Owner account.اجتازت هذه الميزة اختباراً فعلياً على نسخة Odoo معزولة؛ ولم تُفعّل بعد في قاعدة عرض namaa_ksa المشتركة. تتضمن الحزمة ملفات إصدارات مستندات التقديم المعتمدة والمرفقات الثنائية المرتبطة مباشرة بسجل المشروع. ولا تشمل ملفات OCA DMS أو عناصر المعرفة لحين إصلاح صلاحيات DMS. استخدم حساب مدير مشروع أو مالك.
USER GUIDEدليل المستخدم / 32

What is done and what remainsما أُنجز وما تبقى

This status snapshot is generated from the full 164-story requirements traceability matrix. DONE means the supplied acceptance criteria were verified. PARTIAL means implementation exists but acceptance remains. MISSING means no story-specific implementation was found. BLOCKED means a dependency or decision prevents acceptance.يُنشأ هذا الملخص من مصفوفة تتبع المتطلبات الكاملة التي تضم ١٦٤ قصة. تعني DONE أن معايير القبول المقدمة قد تم التحقق منها. وتعني PARTIAL وجود تنفيذ مع بقاء التحقق. وتعني MISSING عدم العثور على تنفيذ خاص بالقصة. وتعني BLOCKED وجود اعتماد أو قرار يمنع القبول.

  1. Current verified progress: 156 of 164 stories DONE (95.1%); 1 PARTIAL; 0 MISSING; 7 BLOCKED. Next target: at least 85%, requiring 140 verified stories.التقدم المتحقق حالياً: 156 من 164 قصة مكتملة (95.1٪)، و1 جزئية، و0 مفقودة، و7 متوقفة. الهدف التالي 85٪ على الأقل، أي 140 قصة متحققاً منها.
  2. Latest verified work includes initial Excel master imports, reviewed source links and fit rationale, mandatory exit quality gates, manual ticket/SLA and safety escalation, weighted supplier quote comparisons, BOQ consumption/cost source records, and posted project margins and approved budget/actual reports. Open each story below for its supplied criteria and evidence.يشمل أحدث تحقق استيراد البيانات الأساسية من إكسل، وروابط المصادر ومبررات الملاءمة، وبوابات الخروج الإلزامية، وتصعيد التذاكر والسلامة يدوياً، ومقارنة عروض الموردين المرجحة، ومصادر فعلي الكميات والتكلفة، وهوامش المشاريع المرحلة والميزانيات مقابل الفعلي. افتح القصة أدناه لمعاييرها وأدلتها.
  3. The RFQ AI draft is never sent automatically. It shows its sources and uncertainty, waits for a separate reviewer, and creates an unsent draft purchase order only after authorization. Risk-owner assignments create internal Odoo activities; they do not send email.لا تُرسل مسودة عرض السعر التي أنشأها الذكاء الاصطناعي تلقائياً. تعرض المصادر ونقاط عدم اليقين وتنتظر مراجعاً مستقلاً، ثم تنشئ أمر شراء كمسودة غير مرسلة بعد الترخيص فقط. تنشئ إحالات مسؤول المخاطر أنشطة داخلية في Odoo ولا ترسل بريداً إلكترونياً.
  4. For the detailed source/test links, see the live requirements traceability page at /docs/REQUIREMENTS_TRACEABILITY.md. This guide also embeds every story title, status and supplied acceptance criterion below for offline review.لروابط المصدر والاختبارات التفصيلية، راجع صفحة تتبع المتطلبات على /docs/REQUIREMENTS_TRACEABILITY.md. يضم هذا الدليل أيضاً عناوين القصص وحالتها ومعايير قبولها أدناه للمراجعة دون اتصال.
A DONE classification applies only to the supplied story criteria. It does not certify an entire feature area, statutory compliance, or all production role policies.ينطبق تصنيف DONE على معايير القصة المقدمة فقط. ولا يثبت اعتماد مجال كامل أو الامتثال النظامي أو جميع سياسات الأدوار في بيئة الإنتاج.
USER GUIDEدليل المستخدم / 33

Record employee expenses against a projectسجّل مصروفات الموظفين على المشروع

The React Projects workspace provides an optional project expense register over native Odoo Expenses. It supports a draft claim, project and expense category, date, amount, reimbursement method and native submission for review.توفر مساحة المشاريع في React سجلاً اختيارياً لمصروفات المشروع مرتبطاً بمصروفات Odoo الأصلية. يدعم إنشاء مسودة وربطها بالمشروع وفئة المصروف والتاريخ والمبلغ وطريقة السداد ثم إرسالها للمراجعة الأصلية.

  1. Sign in to React and open Projects & BOQ → Project expenses. The live tab appears only when native Expenses and the Build Engine expense add-on are installed, and your user has native expense access plus an active employee linked in the current company.سجّل الدخول إلى React وافتح المشاريع وجداول الكميات ← مصروفات المشروع. يظهر التبويب الفعلي عند تثبيت المصروفات الأصلية وإضافة Build Engine، وامتلاك حسابك صلاحية المصروفات وموظف نشط مرتبط بالشركة الحالية.
  2. Choose the project and an expense category marked as Can be Expensed. Enter the date, positive amount, short description and who paid: employee reimbursement or company.اختر المشروع وفئة مصروف مفعّل لها خيار قابل للصرف. أدخل التاريخ والمبلغ الموجب والوصف القصير والجهة التي دفعت: الموظف أو الشركة.
  3. Choose Save draft expense to create a native Odoo draft. If the project has an analytic account, the expense is allocated to that project for cost reporting. A retry with the same request is protected from duplicate creation.اختر حفظ كمسودة لإنشاء مسودة مصروف أصلية في Odoo. إذا كان للمشروع حساب تحليلي، يخصص المصروف للمشروع في تقارير التكلفة. تحمي إعادة الطلب نفسها من إنشاء نسخة مكررة.
  4. Review the draft, then choose Submit when ready. Odoo checks native employee and manager rules and controls approval, accounting posting and reimbursement. React does not post the expense or mark it paid.راجع المسودة ثم اختر إرسال عند جاهزيتها. يتحقق Odoo من قواعد الموظف والمدير الأصلية ويتولى الاعتماد والترحيل المحاسبي والتعويض. لا يرحّل React المصروف ولا يعلّمه مدفوعاً.
  5. Explore design preview shows synthetic expenses and is read-only. The local live demo also has one clearly labelled SAR 10 draft used to smoke-check React to Odoo; it remains unsubmitted, with no journal entry or reimbursement.تعرض معاينة التصميم مصروفات اصطناعية للقراءة فقط. ويتضمن العرض الحي المحلي مسودة واحدة بقيمة ١٠ ريالات تحمل وصفاً تجريبياً واضحاً لفحص الربط بين React وOdoo؛ لم تُرسل ولم تُنشأ لها قيود أو تعويضات.
  6. Receipt file capture and broader role/company acceptance are not included in this workflow yet.لا يشمل هذا المسار رفع الإيصالات أو قبول جميع الأدوار والشركات بعد.
The feature is installed in the local namaa_ksa demo. Admin is linked to a clearly labelled synthetic demo employee so the workspace can be exercised; this is not a real HR identity. The smoke-test expense is a draft only. Use actual employee records and role checks for business acceptance. Receipt capture and full multi-role acceptance are still open.الميزة مثبتة في قاعدة العرض المحلية namaa_ksa. رُبط حساب المدير بموظف تجريبي اصطناعي واضح الاسم لتمكين تجربة المساحة؛ وهذا ليس هوية موارد بشرية حقيقية. مصروف الاختبار مسودة فقط. استخدم سجلات الموظفين الفعلية واختبارات الأدوار للقبول العملي. لا يزال رفع الإيصالات والقبول الكامل للأدوار المتعددة قيد العمل.
USER GUIDEدليل المستخدم / 35

Import, review and compare authoritative recordsاستيراد السجلات الأصلية ومراجعتها ومقارنتها

The November 8 continuation completes the validated import, source review, manual escalation and cost/financial comparison journeys described below.أكملت متابعة الثامن من نوفمبر مسارات الاستيراد والتحقق ومراجعة المصادر والتصعيد اليدوي ومقارنات التكلفة والبيانات المالية الموضحة أدناه.

  1. Master data: as an Owner/Admin with native creation rights, choose customers, vendors or products and upload an XLSX workbook of up to 200 rows. Map reference/name and optional columns, validate, correct row errors, then import. Reopen the saved receipt to see the created records, actor, time and company. Retrying the same operation does not duplicate records.البيانات الأساسية: بصلاحية المالك أو المدير مع حق الإنشاء الأصلي، اختر العملاء أو الموردين أو المنتجات وارفع ملف إكسل حتى مئتي صف. اربط المرجع والاسم والأعمدة الاختيارية، وتحقق وصحح أخطاء الصفوف ثم استورد. افتح الإيصال للسجلات والمنشئ والوقت والشركة. لا تكرر إعادة المحاولة سجلات العملية نفسها.
  2. CRM → Scouting → Source links and fit rationale: record a public HTTPS link, source title, organization, review note and fit explanation. The saved review preserves its source revision and reviewer/time/company. Refresh if the lead or mandate changed. These are human review notes, not independent automated organization verification.إدارة العملاء ← الاستكشاف ← روابط المصادر ومبررات الملاءمة: أدخل رابطاً عاماً آمناً وعنوان المصدر والجهة وملاحظة المراجعة ومبررات الملاءمة. تحفظ المراجعة نسخة المصدر والمراجع والوقت والشركة. حدّث إذا تغير العميل أو المعايير. هذه ملاحظات بشرية وليست تحققاً آلياً مستقلاً من الجهة.
  3. Quality & Safety → Internal tickets: open a ticket, choose a permitted Owner/PM, future response deadline in local time and routing reason. Route, reopen history, and use Escalate missed SLA only after the recorded deadline has passed. A recorded breach can be escalated once. Routing and escalation remain explicit manual actions.الجودة والسلامة ← التذاكر الداخلية: افتح التذكرة واختر مالكاً أو مدير مشروع مصرحاً به وموعد استجابة مستقبلياً بالتوقيت المحلي وسبب التوجيه. وجّه وافتح السجل، وصعّد تجاوز الموعد بعد مرور الموعد المسجل فقط. يصعّد التجاوز المسجل مرة واحدة. التوجيه والتصعيد إجراءان يدويان صريحان.
  4. Quality & Safety: open an eligible safety incident, overdue corrective action or pending daily inspection whose date has passed. Choose an authorized same-company Owner/PM and enter the escalation reason. Reopen history to inspect the reporter, timestamp and company; Odoo creates the manager activity.الجودة والسلامة: افتح واقعة سلامة مؤهلة أو إجراءً تصحيحياً متأخراً أو تفتيشاً يومياً معلقاً مضى موعده. اختر مالكاً أو مدير مشروع مصرحاً به من الشركة واكتب سبب التصعيد. راجع المبلّغ والوقت والشركة في السجل؛ ينشئ أودو نشاطاً للمسؤول.
  5. Projects → Lifecycle setup: bind a published quality gate to a stage. The required evidence and authorized sign-offs must pass before the project can leave the stage.المشاريع ← إعداد دورة الحياة: اربط بوابة جودة منشورة بالمرحلة. يجب استكمال الأدلة والتوقيعات المطلوبة قبل مغادرة المشروع المرحلة.
  6. Purchasing → open RFQ → Compare landed prices: compare company-currency unit estimates and expected dates. Repeated product/unit lines use quantity-weighted cost and the last delivery needed to fulfill the offer. Lowest price and earliest delivery are highlighted separately; comparison does not award or confirm an order.المشتريات ← افتح طلب التسعير ← مقارنة التكلفة الواصلة: قارن تقديرات الوحدة بعملة الشركة والمواعيد المتوقعة. تستخدم البنود المتكررة للمنتج والوحدة تكلفة مرجحة بالكمية وآخر تسليم لاستكمال العرض. يميّز أقل سعر وأقرب تسليم بصورة منفصلة؛ المقارنة لا ترسي ولا تؤكد الطلب.
  7. Projects → Bills of quantities: compare planned, committed and actual quantity/cost. Variance is actual minus plan. View actual source records to see native issue/return entries with actor/time/company. Site capture drafts stay separate and do not change stock or actuals. Relevant native source-read permissions are required.المشاريع ← جداول الكميات: قارن الكمية والتكلفة المخططة والملتزم بها والفعلية. الانحراف هو الفعلي ناقص المخطط. اعرض مصادر الفعلي لقيود الصرف والمرتجع مع المنفذ والوقت والشركة. تبقى مسودات تسجيل الموقع منفصلة ولا تغير المخزون أو الفعلي. تلزم صلاحيات قراءة المصادر الأصلية.
  8. Dashboard: an Owner with accounting read access can view project status and posted financial margin for a chosen period. Margin equals posted project revenue minus posted project expenses; the percentage is blank without positive revenue. Accounting → Financial reports → Project budget vs actual shows approved budgets, posted actuals and source actors/times. Overlapping budgets do not multiply actuals; unbudgeted posted costs remain visible.لوحة التحكم: يمكن للمالك مع صلاحية القراءة المحاسبية عرض حالة المشاريع والهامش المالي المرحل لفترة مختارة. الهامش هو الإيراد المرحل ناقص المصروف المرحل؛ لا تظهر نسبة دون إيراد موجب. المحاسبة ← التقارير المالية ← ميزانية المشاريع مقابل الفعلي تعرض الميزانيات المعتمدة والفعلي المرحل والمنفذين والأوقات. لا تكرر الميزانيات المتداخلة الفعلي، وتبقى التكاليف المرحلة غير المدرجة في ميزانية ظاهرة.
Engineering acceptance does not approve automatic escalation tiers, independent source legitimacy, inventory/GL valuation policy or regulatory compliance. Native company/project and accounting permissions remain authoritative.لا يمثل القبول الهندسي اعتماداً لطبقات التصعيد الآلي أو شرعية المصادر المستقلة أو سياسة تقييم المخزون والقيود أو الامتثال النظامي. تبقى صلاحيات الشركة والمشروع والمحاسبة الأصلية هي المرجع.
USER GUIDEدليل المستخدم / 36

Work offline and reconcile site capturesالعمل دون اتصال وتسوية تسجيلات الموقع

Download an assigned project while signed in, then keep site captures in an encrypted device vault until reconnection.نزّل مشروعاً مسنداً أثناء تسجيل الدخول، ثم احفظ تسجيلات الموقع في خزنة الجهاز المشفرة حتى عودة الاتصال.

  1. In Projects → Offline site work, an Owner enables downloads and chooses a retention period of 1–72 hours with an audit reason. Site users can download only currently assigned projects.في المشاريع ← عمل الموقع دون اتصال، يمكّن المالك التنزيل ويحدد مدة من ساعة إلى 72 ساعة مع سبب مسجل. ينزّل مستخدم الموقع المشاريع المسندة إليه حالياً فقط.
  2. Create a device passphrase of at least 12 characters. Choose the project and optional readable files, then Download assigned project. Every page is verified before the saved project is replaced. Interrupted downloads preserve the previous copy.أنشئ عبارة مرور للجهاز من 12 حرفاً على الأقل. اختر المشروع وملفاته المتاحة ثم نزّل المشروع المسند. تُفحص كل صفحة قبل استبدال النسخة؛ يحافظ الانقطاع على النسخة السابقة.
  3. While offline, queue task progress, a material-use observation or a daily site report. Attach a photo to a saved or pending capture. A material observation does not post a stock issue or change BOQ actuals.دون اتصال، أضف تسجيل تقدم المهمة أو ملاحظة استعمال المواد أو تقرير الموقع اليومي. أرفق صورة بتسجيل محفوظ أو معلق. لا ترحّل ملاحظة المواد صرف مخزون ولا تغير فعلي جدول الكميات.
  4. After a reload, choose Open saved offline site work on the sign-in screen and unlock with the device passphrase. Downloaded project data expires; pending work and receipts remain encrypted until sent or erased.بعد إعادة التحميل، اختر فتح أعمال الموقع المحفوظة دون اتصال في شاشة الدخول وافتح الخزنة بعبارة مرور الجهاز. تنتهي صلاحية بيانات المشروع؛ تبقى الأعمال المعلقة والإيصالات مشفرة حتى الإرسال أو الحذف.
  5. Reconnect using the original signed-in account and company. The queue syncs automatically after permission checks. Unknown network outcomes retry the same operation identity, including photos. Reopen Odoo sync history to check actor, time and company.أعد الاتصال بالحساب والشركة الأصليين. تُزامن الأعمال تلقائياً بعد فحص الصلاحيات. تعيد النتيجة الشبكية المجهولة المحاولة بالهوية نفسها، بما فيها الصور. افتح سجل المزامنة لمراجعة المستخدم والوقت والشركة.
  6. A conflict shows your queued fields and the current server fields. Keep server version records your decision without changing the capture. Apply my reviewed change submits the reviewed fields against the current version.يعرض التعارض حقولك المعلقة وحقول الخادم الحالية. يسجل الاحتفاظ بنسخة الخادم قرارك دون تغيير التسجيل. يرسل تطبيق تغييري بعد المراجعة الحقول المراجعة مقابل الإصدار الحالي.
Cached device identity is not a live login. Synchronization always requires the current Odoo session and permissions. Disconnected devices cannot learn of assignment revocation until reconnection. Lock the vault or erase it when finished.هوية الجهاز المحفوظة ليست تسجيل دخول فعلياً. تتطلب المزامنة جلسة أودو وصلاحياته الحالية. لا يعرف الجهاز المنقطع إلغاء الإسناد حتى يعود الاتصال. اقفل الخزنة أو احذفها عند الانتهاء.
USER GUIDEدليل المستخدم / 38

Configure independent company approvalsإعداد الاعتمادات المستقلة للشركة

An Owner configures which eligible reviewers may decide promotions and charters.يحدد المالك المراجعين المؤهلين لقرارات ترقية العملاء والمواثيق.

  1. Open Onboarding → Company approval policies. CRM promotion review requires an independent Owner. For charters, choose independent PM/Owner or independent Owner only.افتح الإعداد الأولي ← سياسات اعتماد الشركة. تتطلب ترقية العميل مالكاً مستقلاً، وللميثاق اختر مدير مشروع أو مالكاً مستقلاً، أو مالكاً مستقلاً فقط.
  2. Leave reviewer names unchecked to allow all eligible company reviewers, or select names to restrict authority. Enter a policy reason, save and review the immutable actor/time history. Foreign-company and ineligible reviewers are rejected.اترك الأسماء دون تحديد للسماح لجميع المراجعين المؤهلين، أو حدد أسماء لحصر الصلاحية. أدخل سبب السياسة واحفظ وراجع سجل المستخدم والوقت الثابت. يُرفض المراجع غير المؤهل أو من شركة أخرى.
  3. Sales requests promotion for a lead qualified yes. A different configured reviewer approves conversion or rejects it with a reason. Approval history can be reopened after a new sign-in; rejection leaves the source as a lead.يطلب فريق المبيعات ترقية عميل مؤهل بنعم. يوافق مراجع آخر محدد على التحويل أو يرفضه بسبب مسجل. يُفتح سجل القرار بعد تسجيل دخول جديد، ويبقي الرفض السجل كعميل محتمل.
  4. In Project charter, create and submit the manual content. An independent configured reviewer requests changes or approves. After changes, the author edits and resubmits. Use Refresh charters to load another reviewer’s latest decision. Earlier snapshots remain in history.في ميثاق المشروع، أنشئ المحتوى اليدوي وأرسله. يطلب مراجع مستقل محدد التعديل أو يعتمد. يعدّل المؤلف ثم يعيد الإرسال. استخدم تحديث المواثيق لتحميل قرار المراجع الآخر، وتبقى النسخ السابقة في السجل.
Policy changes invalidate earlier review revisions. No requester can approve their own submission; approval does not send a proposal or generate AI charter content.تُلغي تغييرات السياسة صلاحية رموز المراجعة السابقة. لا يعتمد مقدم الطلب طلبه، ولا يرسل الاعتماد عرضاً ولا يولد محتوى ميثاق بالذكاء الاصطناعي.
USER GUIDEدليل المستخدم / 39

Report a client snag after handoverتسجيل ملاحظة عميل بعد التسليم

Clients use a separate sign-in and can submit snag tickets only for their own certified handed-over projects.يستخدم العميل دخولاً مستقلاً ويرسل الملاحظات لمشاريعه المسلمة والمعتمدة فقط.

  1. On the sign-in screen, choose Client aftercare sign-in. Use the client account supplied for the correct database; internal staff accounts cannot use this client-only workflow.في شاشة الدخول، اختر دخول خدمة العميل. استخدم حساب العميل وقاعدة البيانات الصحيحين؛ لا تستخدم حسابات الموظفين الداخلية هذه الخدمة المخصصة للعملاء.
  2. Choose a listed handed-over project. Enter a subject and description and optionally attach up to five valid PNG/JPEG/WebP photos of at most 3 MB each. Submit the snag ticket.اختر مشروعاً مسلماً من القائمة. أدخل العنوان والوصف وأرفق اختيارياً حتى خمس صور صالحة بحد أقصى 3 ميغابايت للصورة. أرسل تذكرة الملاحظة.
  3. If the connection interrupts, Retry pending submission sends the exact same saved operation without creating a duplicate. Reopen Your snag tickets to inspect project/company, author, timestamp and photos.عند انقطاع الاتصال، تعيد محاولة الإرسال المعلق العملية المحفوظة نفسها دون إنشاء نسخة مكررة. أعد فتح تذاكر ملاحظاتك لمراجعة المشروع والشركة والمستخدم والوقت والصور.
  4. A company Owner can disable new client submissions in Company approval policies. Certified handover remains mandatory. Client sign-out destroys the native session; client identities cannot access internal workspace APIs.يمكن لمالك الشركة تعطيل الإرسال الجديد في سياسات اعتماد الشركة. يبقى التسليم المعتمد إلزامياً. ينهي خروج العميل الجلسة الأصلية، ولا تدخل هويات العملاء إلى واجهات مساحة العمل الداخلية.
This verifies client snag reporting after the recorded handover. It does not certify that every project ledger or stock reconciliation is complete.يتحقق هذا من تسجيل الملاحظات بعد التسليم المسجل، ولا يشهد باكتمال كل تسويات الدفاتر أو المخزون للمشروع.
USER GUIDEدليل المستخدم / 34

Review workflow versions and CRM decisionsمراجعة نسخ دورات العمل وقرارات العملاء

Create controlled lifecycle versions, review CRM merges and proposals, and export authorized operational records.أنشئ نسخاً محكومة لدورات الحياة وراجع دمج سجلات العملاء والعروض وصدّر السجلات التشغيلية المصرح بها.

  1. In Projects → Lifecycle setup, select a published lifecycle and choose Use as template. Enter a new name/code, review stages and transitions, then save the draft. Every stage needs a route from the start to completion.في المشاريع ← إعداد دورة الحياة، اختر نسخة منشورة ثم استخدام كقالب. أدخل اسماً ورمزاً جديدين وراجع المراحل والانتقالات ثم احفظ المسودة. يجب أن تكون كل مرحلة متصلة بالبداية ولها مسار إلى الاكتمال.
  2. To change an existing lifecycle, create a New version and publish it after review. Existing projects remain on their pinned version. In Workflow execution, an authorized Owner selects a target publication, records the migration rationale and explicitly migrates the selected project.لتغيير دورة حياة قائمة، أنشئ نسخة جديدة وانشرها بعد المراجعة. تبقى المشاريع الحالية على نسختها المثبتة. في تنفيذ دورة العمل، يختار المالك المصرح له نسخة منشورة ويسجل مبرر الترحيل ثم يرحّل المشروع المحدد صراحة.
  3. Migration requires matching stage names, start/completion meaning and quality gates. Resolve pending approvals first. Workflows with completed gate evidence remain pinned. The screen explains a refused migration without changing the project.يتطلب الترحيل تطابق أسماء المراحل ومعنى البداية والاكتمال وبوابات الجودة. أكمل الموافقات المعلقة أولاً. تبقى دورات العمل التي لها أدلة بوابات مكتملة على نسختها المثبتة. توضح الشاشة سبب رفض الترحيل دون تغيير المشروع.
  4. To restore an earlier configuration, select its published version and choose Restore as new draft. Record a reason, review and publish the copy. Configuration history shows the responsible actor, time, company and recorded changes. Applying the restored version to a project is a separate explicit migration.لاستعادة إعداد سابق، اختر نسخته المنشورة ثم استعادة كمسودة جديدة. سجل السبب وراجع النسخة وانشرها. يعرض سجل الإعدادات المستخدم المسؤول والوقت والشركة والتغييرات المسجلة. يتطلب تطبيق النسخة المستعادة على مشروع ترحيلاً مستقلاً وصريحاً.
  5. In Customer relationships, open an opportunity and choose Find matches. Confirm organization identity before reviewing the merge. Opportunity merges use native survivor ranking; organization merges keep the linked master and require contact-management permission. Reopen the surviving record to read the merge receipts in React.في إدارة العملاء، افتح فرصة واختر البحث عن تطابقات. تحقق من هوية المنشأة قبل مراجعة الدمج. يحدد الترتيب الأصلي الفرصة المتبقية، ويحافظ دمج المنشآت على السجل المرتبط ويتطلب صلاحية إدارة جهات الاتصال. أعد فتح السجل المتبقي لقراءة إيصالات الدمج داخل التطبيق.
  6. A proposal author cannot review their own draft. A separate Sales Manager or Owner enters a rationale and approves for internal release, rejects, or requests a revision. Reopening shows the reviewer and decision history. Revisions retain the earlier version. Approval does not send a customer message.لا يستطيع مؤلف العرض مراجعة مسودته بنفسه. يسجل مدير مبيعات أو مالك آخر المبرر ثم يعتمد العرض للإصدار الداخلي أو يرفضه أو يطلب تعديله. تظهر هوية المراجع وسجل القرار عند إعادة الفتح، ويحتفظ التعديل بالنسخة السابقة. لا يرسل الاعتماد رسالة إلى العميل.
  7. Use the Excel export in BOQ, daily site reports, correspondence, purchase receipts or timesheets. Select project/date filters first. Timesheet exports include both boundary dates, use Arabic headers when selected and exclude pay/cost fields. Narrow filters if the permitted row limit is exceeded.استخدم تصدير إكسل في جداول الكميات أو التقارير اليومية أو المراسلات أو استلام المشتريات أو سجلات الوقت. حدد المشروع والفترة أولاً. تشمل سجلات الوقت تاريخي البداية والنهاية وتستخدم عناوين عربية عند اختيارها وتستبعد حقول الأجر والتكلفة. ضيق التصفية إذا تجاوزت النتائج الحد المسموح.
Published history is retained. Authorization and company boundaries apply to every action.يبقى السجل المنشور محفوظاً. تطبق الصلاحيات وحدود الشركة على كل إجراء.
USER GUIDEدليل المستخدم / 40

Review financial proposal draftsمراجعة مسودات العروض المالية

Draft explanatory text from a confirmed sales order while keeping its exact prices unchanged.أنشئ شرح العرض من طلب بيع مؤكد مع الحفاظ على أسعاره الأصلية دون تغيير.

  1. Sales: open a confirmed order and Financial proposal drafts. Choose English or Arabic, then Draft proposal.المبيعات: افتح طلباً مؤكداً ثم مسودات المقترح المالي. اختر العربية أو الإنجليزية ثم إعداد مسودة.
  2. Review the generated prose, assumptions and missing terms alongside the exact native order prices. The model does not recalculate amounts or introduce numeric commercial terms.راجع النص والافتراضات والشروط الناقصة بجانب أسعار الطلب الأصلية. لا يعيد النموذج حساب المبالغ أو يضيف شروطاً تجارية رقمية.
  3. A different Sales Manager or Owner enters an independent rationale and approves or rejects the draft. Reopen the saved review history. Approval does not send a customer message.يدخل مدير مبيعات أو مالك آخر مبرر المراجعة المستقلة ويعتمد المسودة أو يرفضها. أعد فتح سجل المراجعة المحفوظ. لا يرسل الاعتماد رسالة للعميل.
AI wording requires human review. Access to the confirmed order and its linked private project remains mandatory.تتطلب صياغة الذكاء الاصطناعي مراجعة بشرية. تبقى صلاحية الطلب المؤكد والمشروع الخاص المرتبط به مطلوبة.
USER GUIDEدليل المستخدم / 41

Map bank files and review amendmentsربط ملفات البنك ومراجعة التعديلات

Save reusable CSV/XLSX layouts, including Arabic numbers and dates.احفظ تنسيقات سي إس في وإكسل القابلة لإعادة الاستخدام، بما فيها الأرقام والتواريخ العربية.

  1. Accounting → CSV / Excel maps: an accounting manager sets column names, date format, number separators and the bank transaction ID when available; save and assign the map to the active company bank journal.المحاسبة ← خرائط سي إس في وإكسل: يضبط مدير المحاسبة أسماء الأعمدة وتنسيق التاريخ وفواصل الأرقام ومعرف الحركة البنكي عند توفره، ثم يحفظ الخريطة ويربطها بدفتر البنك للشركة النشطة.
  2. In Statement import, select the journal and upload the mapped file. Exact retries do not duplicate transactions; Odoo retains a source file on each imported statement.في استيراد الكشف، اختر الدفتر وارفع الملف المطابق للخريطة. لا تكرر المحاولات المطابقة الحركات، ويحفظ أودو الملف الأصلي مع كل كشف مستورد.
  3. A changed bank ID or ambiguous same-date description without a bank ID requires review. Check the original statement and map a stable transaction ID before importing the correction. Imports do not overwrite existing transactions.يتطلب تغير تفاصيل معرف بنكي أو غموض وصف في التاريخ نفسه دون معرف مراجعة. افحص الكشف الأصلي واربط معرفاً ثابتاً للحركة قبل استيراد التصحيح. لا يستبدل الاستيراد الحركات القائمة.
  4. Bank reconciliation: review invoice matches and amounts, apply the selected proposal, and reopen its audit history. Undo reconciliation restores the selected open balance through Odoo.تسوية البنك: راجع مطابقة الفواتير والمبالغ وطبق المقترح المحدد ثم أعد فتح سجل التدقيق. يعيد إلغاء التسوية الرصيد المفتوح المحدد عبر أودو.
Use your configured native accounting rules and explicit human review. These synthetic acceptance files do not certify a particular bank format or tax policy.استخدم قواعد المحاسبة الأصلية المضبوطة والمراجعة البشرية الصريحة. لا تعتمد ملفات الاختبار المصطنعة تنسيق بنك محدد أو سياسة ضريبية.
USER GUIDEدليل المستخدم / 42

Read AR/AP and active-company cash forecastsقراءة الذمم وتوقع النقد للشركة النشطة

Reports use native posted balances and the active company currency.تستخدم التقارير الأرصدة الأصلية المرحلة وعملة الشركة النشطة.

  1. Accounting → Financial reports: select Aged Receivable or Aged Payable, set As of, and Run report. Partial settlements and credit notes affect remaining balances at the selected cutoff.المحاسبة ← التقارير المالية: اختر أعمار الذمم المدينة أو الدائنة وحدد تاريخ كما في ثم عرض التقرير. تؤثر التسويات الجزئية والإشعارات الدائنة على الأرصدة المتبقية عند التاريخ المحدد.
  2. Open Cash forecast, choose its start date, periods and overdue handling, then Run forecast. Review receipts, payments, opening and closing cash. Partner detail is optional.افتح توقع التدفق النقدي وحدد تاريخ البداية والفترات ومعالجة المتأخرات ثم أنشئ التوقع. راجع المقبوضات والمدفوعات والرصيدين الافتتاحي والختامي. تفاصيل الأطراف اختيارية.
  3. The forecast labels its active company, currency, viewer and generation time. Child-company balances are excluded. Include draft invoices and bills only when you deliberately enable that option.يعرض التوقع الشركة النشطة والعملة والمستخدم ووقت الإنشاء. تُستبعد أرصدة الشركات التابعة. لا تدرج مسودات الفواتير إلا عند تفعيل الخيار صراحة.
Forecasts are estimates from current native residuals and recorded expected cash items. Read-only finance access can view reports; running a report does not post or reverse accounting entries.التوقع تقدير من الأرصدة الأصلية الحالية والتدفقات المتوقعة المسجلة. يمكن لصلاحية المحاسبة للقراءة عرض التقارير، ولا يرحل تشغيل التقرير قيوداً أو يعكسها.
USER GUIDEدليل المستخدم / 43

Prevent insufficient stockمنع المخزون غير الكافي

An Owner records the company stock policy in Onboarding. When enabled, insufficient-stock transactions are blocked in internal and transit locations.يسجل المالك سياسة مخزون الشركة في التهيئة. عند تفعيلها تُمنع عمليات المخزون غير الكافي في المواقع الداخلية ومواقع النقل.

  1. Open Onboarding → Prevent insufficient stock. Review the current company and recorded decisions.افتح التهيئة ← منع المخزون غير الكافي. راجع الشركة الحالية والقرارات المسجلة.
  2. An Owner selects Block negative stock, enters a reason, then saves. Refresh to confirm the responsible user and UTC timestamp.يحدد المالك منع المخزون السالب ويسجل السبب ثم يحفظ. حدّث الصفحة للتحقق من المستخدم المسؤول والوقت بالتوقيت العالمي.
  3. When an issue or delivery exceeds stock, correct the quantity or receive/return stock, then retry. There is no transaction bypass.عند تجاوز الصرف أو التسليم للمخزون، صحح الكمية أو سجل الاستلام أو الإرجاع ثم أعد المحاولة. لا يوجد تجاوز للعملية.
The policy requires an explicit company decision. It does not create receipts, adjust stock, or replace native valuation.تتطلب السياسة قراراً صريحاً للشركة. لا تنشئ استلاماً ولا تعدل المخزون ولا تستبدل التقييم الأصلي.
USER GUIDEدليل المستخدم / 44

Preview PDF and DXF drawingsمعاينة مخططات PDF وDXF

Authorized project users can preview supported drawings while retaining the original file and revision.يمكن لمستخدمي المشروع المصرح لهم معاينة المخططات المدعومة مع الاحتفاظ بالملف الأصلي وإصداره.

  1. Open Projects → Drawings and choose Preview drawing beside a PDF or supported DXF file.افتح المشاريع ← المخططات واختر معاينة المخطط بجوار ملف PDF أو DXF مدعوم.
  2. Wait for the preview. Use PDF page controls and the Zoom selector. Close the dialog to return to the drawing register.انتظر المعاينة. استخدم أزرار صفحات PDF ومحدد التكبير. أغلق النافذة للعودة إلى سجل المخططات.
  3. Use Download original for the source file. DWG and IFC are download-only and are labelled accordingly. If access is removed, cached previews become unavailable.استخدم تنزيل الأصل للحصول على الملف المصدر. يقتصر DWG وIFC على التنزيل ويظهر ذلك بوضوح. عند سحب الصلاحية تصبح المعاينات المخزنة غير متاحة.
DXF preview supports two-dimensional model space. External references, unsupported entities, corrupt or encrypted files may be rejected. Previewing does not edit CAD files or certify quantity takeoff accuracy.تدعم معاينة DXF مساحة النموذج ثنائية الأبعاد. قد ترفض المراجع الخارجية والعناصر غير المدعومة والملفات التالفة أو المشفرة. لا تعدل المعاينة ملفات CAD ولا تشهد بدقة حصر الكميات.
USER GUIDEدليل المستخدم / 46

Review project closeout with Financeمراجعة إقفال المشروع مع المالية

A PM requests review, a different Finance user checks evidence, and the requesting PM certifies handover against the current reviewed records.يطلب مدير المشروع المراجعة ويتحقق مستخدم آخر من المالية من الأدلة ثم يعتمد المدير الطالب التسليم وفق السجلات الحالية المراجعة.

  1. Open Projects → Project closeout and select the project. Resolve every listed punch, stock, equipment and invoice/bill blocker.افتح المشاريع ← إقفال المشروع واختر المشروع. عالج كل موانع الملاحظات والمخزون والمعدات والفواتير المعروضة.
  2. The PM enters financial and bank evidence references and requests Finance closeout review. A different authorized Finance user refreshes the evidence, reviews source invoices and references, and records approval or rejection.يدخل مدير المشروع مراجع الأدلة المالية والبنكية ويطلب المراجعة. يحدّث مستخدم آخر مخول من المالية الأدلة ويراجع الفواتير والمراجع ويسجل الاعتماد أو الرفض.
  3. After Finance approval, the requesting PM refreshes, confirms all seven handover/reconciliation items, enters the closeout summary and certifies. Reopen to inspect responsible users and timestamps. Changed evidence requires a new review.بعد اعتماد المالية يحدّث المدير الطالب الصفحة ويؤكد عناصر التسوية والتسليم السبعة ويدخل الملخص ويعتمد الإقفال. أعد الفتح لمراجعة المسؤولين والأوقات. يتطلب تغير الأدلة مراجعة جديدة.
Finance must review bank statement rows and financial records without project links and record the evidence. Approval does not perform bank matching, accounting posting, stock cleanup or project archiving. Historical certifications retain their recorded evidence.على المالية مراجعة حركات البنك والسجلات المالية غير المرتبطة بمشروع وتسجيل الدليل. لا ينفذ الاعتماد مطابقة بنكية أو ترحيلاً محاسبياً أو تصفية مخزون أو أرشفة مشروع. تحتفظ الشهادات السابقة بأدلتها المسجلة.
USER GUIDEدليل المستخدم / 47

Review assessment runs and source reliabilityمراجعة تشغيل التقييمات وموثوقية المصادر

CRM scouting records a receipt for each fit-assessment request. An Owner can disable an unreliable CRM source for the current company.يسجل استكشاف العملاء إيصالاً لكل طلب تقييم ملاءمة. يمكن للمالك تعطيل مصدر غير موثوق للشركة الحالية.

  1. Open Customer relationships → Scouting → Scouting runs and source controls. Generate a fit assessment from a candidate, then refresh its run history.افتح إدارة العملاء ← الاستكشاف ← تشغيل الاستكشاف والتحكم بالمصادر. أنشئ تقييم ملاءمة لمرشح ثم حدّث سجل التشغيل.
  2. Review status, lead/source, responsible user, start/finish time, duration and saved finding. Failures identify model unavailability, rejected output, changed context or save unavailability. A run without completion for ten minutes is marked interrupted.راجع الحالة والعميل والمصدر والمستخدم ووقت البداية والنهاية والمدة والتقييم المحفوظ. يوضح الفشل تعذر النموذج أو رفض الناتج أو تغير السياق أو تعذر الحفظ. تظهر العملية دون إكمال لعشر دقائق كعملية منقطعة.
  3. An Owner chooses a CRM source, disables or enables it for this company, records a reliability reason and saves. Expand Source decision history to inspect the immutable actor/time record.يختار المالك مصدر العميل وتعطيله أو تفعيله للشركة ويسجل سبب القرار ويحفظ. افتح سجل قرارات المصادر لمراجعة سجل المستخدم والوقت الثابت.
  4. Disabled sources disappear from company candidates and cannot complete an assessment already in progress. History is retained and other companies are unaffected. Load older runs when more history is available.تختفي المصادر المعطلة من مرشحي الشركة ولا يمكنها إكمال تقييم قيد التشغيل. يبقى السجل محفوظاً ولا تتأثر الشركات الأخرى. حمّل العمليات الأقدم عند توفرها.
This covers assessments of existing company CRM records. External discovery is not connected. Source decisions and human lead review remain manual; no outreach is sent automatically.يغطي هذا تقييم سجلات العملاء الموجودة بالشركة. الاستكشاف الخارجي غير متصل. تبقى قرارات المصادر ومراجعة العميل البشرية يدوية ولا ترسل مراسلات تلقائياً.
USER GUIDEدليل المستخدم / 48

Set up and manage an isolated company workspaceإعداد مساحة شركة مستقلة وإدارتها

An allowlisted platform operator provisions the native company and its separate application, database and files.يعد مسؤول المنصة المدرج في قائمة السماح الشركة الأصلية وتشغيلها وقاعدة بياناتها وملفاتها المستقلة.

  1. Onboarding → Tenant operations: enter the legal identity and Owner email, request setup, then refresh the audited native job status. Customer Owners cannot use platform controls.الإعداد الأولي ← إدارة مساحات الشركات: أدخل الهوية النظامية وبريد المالك واطلب الإعداد ثم حدّث حالة المهمة الأصلية المدققة. لا تتاح أدوات المنصة لمالكي الشركات العملاء.
  2. After setup, retrieve the Owner activation link for manual delivery. The Owner chooses a private password. Current customer links are local to this computer; public DNS/TLS is a separate deployment.بعد الإعداد أظهر رابط تفعيل المالك للتسليم اليدوي. يختار المالك كلمة مرور خاصة. روابط الشركات الحالية محلية لهذا الجهاز؛ يتطلب النطاق العام وشهادة الحماية نشراً منفصلاً.
  3. To suspend a tenant, wait for the worker receipt before exporting. Download the protected database/agent/filestore archive with its checksum. Resume retains records and requires a new login.لتعليق مساحة شركة انتظر إيصال العامل قبل التصدير. نزّل حزمة قواعد البيانات والملفات المحمية مع بصمتها. يحتفظ الاستئناف بالسجلات ويتطلب دخولاً جديداً.
Legal identity is recorded as provided, with identifier syntax checks. Official verification and production hosting are separate.تسجل الهوية كما قدمت مع التحقق من تنسيق المعرفات. التحقق الرسمي والاستضافة الإنتاجية منفصلان.
USER GUIDEدليل المستخدم / 49

Invite your team and assign project accessدعوة الفريق وتعيين صلاحيات المشاريع

An Owner creates manually delivered invitations and manages native project scope.ينشئ المالك دعوات تسلم يدوياً ويدير نطاق المشاريع الأصلي.

  1. Onboarding → Team invitations and project roles: enter the person and email, choose a role and select the assigned projects. PM, Site and QS roles require projects; company-wide roles are clearly labeled.الإعداد الأولي ← دعوات الفريق وأدوار المشاريع: أدخل الشخص والبريد واختر الدور والمشاريع المسندة. تتطلب أدوار مدير المشروع والموقع وحصر الكميات مشاريع، وتوضح أدوار الشركة صراحة.
  2. Deliver the activation link manually. It expires after24hours and works once. The invited person sets a private password, continues to sign-in and uses the assigned database.سلم رابط التفعيل يدوياً. تنتهي صلاحيته بعد24ساعة ويستخدم مرة واحدة. يعين المدعو كلمة مرور خاصة ثم يتابع الدخول إلى قاعدة البيانات المسندة.
  3. Select a new role/projects and apply it to a managed person, or revoke access. Reopen the native audit history to see who changed access and when.اختر الدور والمشاريع الجديدة وطبقها على مستخدم مدار أو اسحب الصلاحية. راجع سجل التدقيق الأصلي لمعرفة من غير الصلاحية ومتى.
Invitations and first activation send no invitation email. Project restrictions apply in Odoo as well as the visible React screens.لا ترسل الدعوات والتفعيل الأول بريداً للدعوة. تنطبق قيود المشاريع في أودو وفي شاشات React.
LIVE REQUIREMENTS SNAPSHOT · 2026-11-17ملخص المتطلبات · تحديث 2026-11-17

All 164 stories, with their current statusحالة القصص الـ١٦٤ كاملة

As of 2026-11-17: 156 DONE (95.1%), 1 PARTIAL (0.6%), 0 MISSING (0.0%), and 7 BLOCKED (4.3%). DONE counts only stories whose supplied criteria have documented verification. PARTIAL is not a completion score.حتى 2026-11-17: مكتملة DONE عددها 156 (95.1٪)، وجزئية PARTIAL عددها 1 (0.6٪)، ومفقودة MISSING عددها 0 (0.0٪)، ومتوقفة BLOCKED عددها 7 (4.3٪). لا تُحسب القصة مكتملة إلا بعد توثيق معايير القبول المقدمة. PARTIAL ليست نسبة إنجاز.

Open each story below to read its persona, requirement and supplied acceptance criteria. The traceability matrix in the project docs links each story to source code, tests and remaining work.افتح كل قصة أدناه لقراءة المستخدم والمتطلب ومعايير القبول المقدمة. تربط مصفوفة التتبع في وثائق المشروع كل قصة بالكود والاختبارات والعمل المتبقي.

Open detailed code and test traceability ↗افتح تفاصيل ربط القصص بالكود والاختبارات ↗ · Open generated progress report ↗افتح تقرير التقدم المولّد ↗

BE-001 · Create tenant and configure legal company identityDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to create tenant and configure legal company identity, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create tenant and configure legal company identity”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-002 · Invite users and assign project-scoped rolesDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to invite users and assign project-scoped roles, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Invite users and assign project-scoped roles”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-003 · Configure company trades, regions and tender thresholdsDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to configure company trades, regions and tender thresholds, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure company trades, regions and tender thresholds”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-004 · Configure company branding and document templatesDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to configure company branding and document templates, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure company branding and document templates”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-005 · Import initial master data with validationDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to import initial master data with validation, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Import initial master data with validation”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-006 · View onboarding checklist and first-value sample projectDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to view onboarding checklist and first-value sample project, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View onboarding checklist and first-value sample project”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-007 · Configure Arabic/English language and timezoneDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to configure Arabic/English language and timezone, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure Arabic/English language and timezone”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-008 · Suspend tenant and export customer dataDONE · مكتملة

Owner/Admin: As a Owner/Admin, I want to suspend tenant and export customer data, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Suspend tenant and export customer data”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-009 · Create lead from manual entryDONE · مكتملة

Sales Representative: As a Sales Representative, I want to create lead from manual entry, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create lead from manual entry”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-010 · Classify government vs private leadDONE · مكتملة

Sales Representative: As a Sales Representative, I want to classify government vs private lead, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Classify government vs private lead”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-011 · Deduplicate organization and leadDONE · مكتملة

Sales Representative: As a Sales Representative, I want to deduplicate organization and lead, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Deduplicate organization and lead”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-012 · Qualify lead yes/no/maybe with reasonDONE · مكتملة

Sales Representative: As a Sales Representative, I want to qualify lead yes/no/maybe with reason, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Qualify lead yes/no/maybe with reason”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-013 · Approve lead-to-opportunity promotionDONE · مكتملة

Sales Representative: As a Sales Representative, I want to approve lead-to-opportunity promotion, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Approve lead-to-opportunity promotion”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-014 · Manage pipeline stage and probabilityDONE · مكتملة

Sales Representative: As a Sales Representative, I want to manage pipeline stage and probability, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Manage pipeline stage and probability”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-015 · Create tender and bid checklistDONE · مكتملة

Sales Representative: As a Sales Representative, I want to create tender and bid checklist, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create tender and bid checklist”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-016 · Track bid deadline and submission evidenceDONE · مكتملة

Sales Representative: As a Sales Representative, I want to track bid deadline and submission evidence, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track bid deadline and submission evidence”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-017 · Convert won opportunity to projectDONE · مكتملة

Sales Representative: As a Sales Representative, I want to convert won opportunity to project, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Convert won opportunity to project”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-018 · View win rate and pipeline valueDONE · مكتملة

Sales Representative: As a Sales Representative, I want to view win rate and pipeline value, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View win rate and pipeline value”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-019 · Configure scouting mandate and source allowlistDONE · مكتملة

Owner: As a Owner, I want to configure scouting mandate and source allowlist, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure scouting mandate and source allowlist”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-020 · Schedule periodic tender and public signal discoveryBLOCKED · متوقفة

Owner: As a Owner, I want to schedule periodic tender and public signal discovery, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Schedule periodic tender and public signal discovery”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-021 · Filter by project size, region and sectorDONE · مكتملة

Owner: As a Owner, I want to filter by project size, region and sector, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Filter by project size, region and sector”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-022 · Verify sources and organization legitimacyBLOCKED · متوقفة

Owner: As a Owner, I want to verify sources and organization legitimacy, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Verify sources and organization legitimacy”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-023 · Classify lead as yes/no/maybeDONE · مكتملة

Owner: As a Owner, I want to classify lead as yes/no/maybe, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Classify lead as yes/no/maybe”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-024 · Route yes/maybe to human review and archive noDONE · مكتملة

Owner: As a Owner, I want to route yes/maybe to human review and archive no, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Route yes/maybe to human review and archive no”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-025 · Prevent duplicate CRM handoffDONE · مكتملة

Owner: As a Owner, I want to prevent duplicate CRM handoff, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Prevent duplicate CRM handoff”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-026 · Show source links and fit rationaleDONE · مكتملة

Owner: As a Owner, I want to show source links and fit rationale, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Show source links and fit rationale”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-027 · Chat with scouting agent about findingsDONE · مكتملة

Owner: As a Owner, I want to chat with scouting agent about findings, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Chat with scouting agent about findings”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-028 · Review run logs and disable unreliable sourcesDONE · مكتملة

Owner: As a Owner, I want to review run logs and disable unreliable sources, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Review run logs and disable unreliable sources”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-029 · Generate account research and opening message draftDONE · مكتملة

Sales Representative: As a Sales Representative, I want to generate account research and opening message draft, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Generate account research and opening message draft”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-030 · Require human first contact and consent to proceedDONE · مكتملة

Sales Representative: As a Sales Representative, I want to require human first contact and consent to proceed, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Require human first contact and consent to proceed”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-031 · Draft technical proposal from customer templateDONE · مكتملة

Sales Representative: As a Sales Representative, I want to draft technical proposal from customer template, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft technical proposal from customer template”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-032 · Draft financial proposal from approved pricingDONE · مكتملة

Sales Representative: As a Sales Representative, I want to draft financial proposal from approved pricing, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft financial proposal from approved pricing”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
  6. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-033 · Apply tenant logo and letterheadDONE · مكتملة

Sales Representative: As a Sales Representative, I want to apply tenant logo and letterhead, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Apply tenant logo and letterhead”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-034 · Produce final PDF preview for approvalDONE · مكتملة

Sales Representative: As a Sales Representative, I want to produce final PDF preview for approval, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Produce final PDF preview for approval”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-035 · Approve/reject/revise outgoing proposalDONE · مكتملة

Sales Representative: As a Sales Representative, I want to approve/reject/revise outgoing proposal, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Approve/reject/revise outgoing proposal”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-036 · Save approved PDF to opportunity/project archiveDONE · مكتملة

Sales Representative: As a Sales Representative, I want to save approved PDF to opportunity/project archive, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Save approved PDF to opportunity/project archive”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-037 · Generate daily follow-up listDONE · مكتملة

Sales Representative: As a Sales Representative, I want to generate daily follow-up list, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Generate daily follow-up list”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-038 · Block autonomous sending and stage promotionDONE · مكتملة

Sales Representative: As a Sales Representative, I want to block autonomous sending and stage promotion, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Block autonomous sending and stage promotion”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-039 · Create project from awarded opportunityDONE · مكتملة

Project Manager: As a Project Manager, I want to create project from awarded opportunity, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create project from awarded opportunity”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-040 · Create phases tasks subtasks and dependenciesDONE · مكتملة

Project Manager: As a Project Manager, I want to create phases tasks subtasks and dependencies, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create phases tasks subtasks and dependencies”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-041 · Assign crew and responsible personsDONE · مكتملة

Project Manager: As a Project Manager, I want to assign crew and responsible persons, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Assign crew and responsible persons”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-042 · Display Gantt and critical deadlinesDONE · مكتملة

Project Manager: As a Project Manager, I want to display Gantt and critical deadlines, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Display Gantt and critical deadlines”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-043 · Detect crew and equipment double-bookingDONE · مكتملة

Project Manager: As a Project Manager, I want to detect crew and equipment double-booking, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Detect crew and equipment double-booking”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-044 · Configure project lifecycle stage templateDONE · مكتملة

Project Manager: As a Project Manager, I want to configure project lifecycle stage template, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure project lifecycle stage template”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-045 · Track project milestones and stakeholder obligationsDONE · مكتملة

Project Manager: As a Project Manager, I want to track project milestones and stakeholder obligations, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track project milestones and stakeholder obligations”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-046 · Draft project charter and obtain approvalDONE · مكتملة

Project Manager: As a Project Manager, I want to draft project charter and obtain approval, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft project charter and obtain approval”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-047 · Record schedule baseline and change historyDONE · مكتملة

Project Manager: As a Project Manager, I want to record schedule baseline and change history, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record schedule baseline and change history”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-048 · Close project after required reconciliationsDONE · مكتملة

Project Manager: As a Project Manager, I want to close project after required reconciliations, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Close project after required reconciliations”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-049 · Create versioned project BOQDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to create versioned project BOQ, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create versioned project BOQ”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-050 · Import BOQ spreadsheet with mappingDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to import BOQ spreadsheet with mapping, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Import BOQ spreadsheet with mapping”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-051 · Capture labor material equipment and work linesDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to capture labor material equipment and work lines, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Capture labor material equipment and work lines”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-052 · Draft BOQ from drawings and scope with AIDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to draft BOQ from drawings and scope with AI, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft BOQ from drawings and scope with AI”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-053 · Validate units rates and quantity totalsDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to validate units rates and quantity totals, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Validate units rates and quantity totals”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-054 · Approve BOQ baseline and lock revisionDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to approve BOQ baseline and lock revision, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Approve BOQ baseline and lock revision”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-055 · Create variation order with impact analysisDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to create variation order with impact analysis, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create variation order with impact analysis”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-056 · Approve/reject variation order with audit trailDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to approve/reject variation order with audit trail, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Approve/reject variation order with audit trail”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
  6. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-057 · Compare estimated vs actual consumption and costsDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to compare estimated vs actual consumption and costs, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Compare estimated vs actual consumption and costs”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-058 · Link manufacturing BOM where applicableDONE · مكتملة

Quantity Surveyor: As a Quantity Surveyor, I want to link manufacturing BOM where applicable, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Link manufacturing BOM where applicable”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-059 · Maintain approved supplier directoryDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to maintain approved supplier directory, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Maintain approved supplier directory”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
  6. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-060 · Create material request linked to BOQDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to create material request linked to BOQ, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create material request linked to BOQ”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-061 · Draft and review RFQ to selected suppliersDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to draft and review RFQ to selected suppliers, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft and review RFQ to selected suppliers”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-062 · Record supplier quotations and validityDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to record supplier quotations and validity, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record supplier quotations and validity”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-063 · Compare landed prices and delivery datesDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to compare landed prices and delivery dates, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Compare landed prices and delivery dates”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-064 · Flag quote anomalies for human reviewDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to flag quote anomalies for human review, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Flag quote anomalies for human review”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-065 · Approve purchase before commitmentDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to approve purchase before commitment, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Approve purchase before commitment”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-066 · Receive materials into correct locationDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to receive materials into correct location, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Receive materials into correct location”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-067 · Detect stock shortage against scheduleDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to detect stock shortage against schedule, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Detect stock shortage against schedule”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-068 · Track vendor performance and RFQ historyDONE · مكتملة

Procurement Officer: As a Procurement Officer, I want to track vendor performance and RFQ history, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track vendor performance and RFQ history”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-069 · Create warehouses and site stock locationsDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to create warehouses and site stock locations, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create warehouses and site stock locations”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-070 · Receive materials against purchase orderDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to receive materials against purchase order, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Receive materials against purchase order”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-071 · Transfer material to project siteDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to transfer material to project site, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Transfer material to project site”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-072 · Issue material to project and BOQ lineDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to issue material to project and BOQ line, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Issue material to project and BOQ line”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-073 · Return unused material to yardDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to return unused material to yard, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Return unused material to yard”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-074 · Perform stock count and variance approvalDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to perform stock count and variance approval, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Perform stock count and variance approval”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-075 · Track minimum stock and reorder alertsDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to track minimum stock and reorder alerts, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track minimum stock and reorder alerts”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-076 · Prevent negative stock per configurationDONE · مكتملة

Warehouse Officer: As a Warehouse Officer, I want to prevent negative stock per configuration, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Prevent negative stock per configuration”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-077 · Assign analytic project cost centerDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to assign analytic project cost center, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Assign analytic project cost center”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-078 · Create customer invoice from milestoneDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to create customer invoice from milestone, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create customer invoice from milestone”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-079 · Record vendor bill and match purchase orderDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to record vendor bill and match purchase order, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record vendor bill and match purchase order”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-080 · Reconcile bank payments and receiptsDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to reconcile bank payments and receipts, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Reconcile bank payments and receipts”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-081 · View project P&L and cash flowDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to view project P&L and cash flow, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View project P&L and cash flow”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-082 · Generate compliant Saudi tax invoiceBLOCKED · متوقفة

Finance Accountant: As a Finance Accountant, I want to generate compliant Saudi tax invoice, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Generate compliant Saudi tax invoice”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-083 · Clear/report electronic invoice via approved ZATCA adapterBLOCKED · متوقفة

Finance Accountant: As a Finance Accountant, I want to clear/report electronic invoice via approved ZATCA adapter, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Clear/report electronic invoice via approved ZATCA adapter”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-084 · Handle credit and debit notesDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to handle credit and debit notes, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Handle credit and debit notes”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-085 · Track failed compliance submission and retryBLOCKED · متوقفة

Finance Accountant: As a Finance Accountant, I want to track failed compliance submission and retry, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track failed compliance submission and retry”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-086 · Export finance reports with restricted permissionsDONE · مكتملة

Finance Accountant: As a Finance Accountant, I want to export finance reports with restricted permissions, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Export finance reports with restricted permissions”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-087 · Manage employee records and assignmentsDONE · مكتملة

HR Officer: As a HR Officer, I want to manage employee records and assignments, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Manage employee records and assignments”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-088 · Onboard and offboard staffDONE · مكتملة

HR Officer: As a HR Officer, I want to onboard and offboard staff, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Onboard and offboard staff”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-089 · Record project task timesheetsDONE · مكتملة

HR Officer: As a HR Officer, I want to record project task timesheets, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record project task timesheets”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-090 · Review and approve attendance entriesDONE · مكتملة

HR Officer: As a HR Officer, I want to review and approve attendance entries, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Review and approve attendance entries”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-091 · Allocate labor cost to projectDONE · مكتملة

HR Officer: As a HR Officer, I want to allocate labor cost to project, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Allocate labor cost to project”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-092 · Export basic payroll inputs with authorizationBLOCKED · متوقفة

HR Officer: As a HR Officer, I want to export basic payroll inputs with authorization, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Export basic payroll inputs with authorization”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-093 · Register equipment and acquisition dataDONE · مكتملة

Asset Manager: As a Asset Manager, I want to register equipment and acquisition data, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Register equipment and acquisition data”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-094 · Assign equipment to projectDONE · مكتملة

Asset Manager: As a Asset Manager, I want to assign equipment to project, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Assign equipment to project”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-095 · Check out and return toolsDONE · مكتملة

Asset Manager: As a Asset Manager, I want to check out and return tools, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Check out and return tools”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-096 · Schedule preventive maintenanceDONE · مكتملة

Asset Manager: As a Asset Manager, I want to schedule preventive maintenance, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Schedule preventive maintenance”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-097 · Record breakdown and repair costsDONE · مكتملة

Asset Manager: As a Asset Manager, I want to record breakdown and repair costs, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record breakdown and repair costs”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-098 · Track utilization and idle timeDONE · مكتملة

Asset Manager: As a Asset Manager, I want to track utilization and idle time, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track utilization and idle time”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-099 · Retire or dispose asset with approvalDONE · مكتملة

Asset Manager: As a Asset Manager, I want to retire or dispose asset with approval, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Retire or dispose asset with approval”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-100 · Configure quality gate checklistDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to configure quality gate checklist, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure quality gate checklist”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-101 · Attach inspection evidence and signaturesDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to attach inspection evidence and signatures, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Attach inspection evidence and signatures”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-102 · Prevent advancing past mandatory unsigned gateDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to prevent advancing past mandatory unsigned gate, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Prevent advancing past mandatory unsigned gate”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-103 · Map regulatory checkpoint to current referenceBLOCKED · متوقفة

Quality/Safety Officer: As a Quality/Safety Officer, I want to map regulatory checkpoint to current reference, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Map regulatory checkpoint to current reference”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-104 · Log nonconformance and corrective actionDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to log nonconformance and corrective action, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Log nonconformance and corrective action”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-105 · Track incident and near missDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to track incident and near miss, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track incident and near miss”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-106 · Complete daily safety checklistDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to complete daily safety checklist, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Complete daily safety checklist”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-107 · Escalate overdue inspection or safety incidentDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to escalate overdue inspection or safety incident, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Escalate overdue inspection or safety incident”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-108 · Maintain punch list until closeoutDONE · مكتملة

Quality/Safety Officer: As a Quality/Safety Officer, I want to maintain punch list until closeout, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Maintain punch list until closeout”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-109 · Create RFI and assign respondentDONE · مكتملة

Site Engineer: As a Site Engineer, I want to create RFI and assign respondent, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create RFI and assign respondent”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-110 · Track RFI response deadline and statusDONE · مكتملة

Site Engineer: As a Site Engineer, I want to track RFI response deadline and status, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track RFI response deadline and status”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-111 · Create submittal with drawing revisionDONE · مكتملة

Site Engineer: As a Site Engineer, I want to create submittal with drawing revision, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create submittal with drawing revision”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-112 · Record approval or resubmissionDONE · مكتملة

Site Engineer: As a Site Engineer, I want to record approval or resubmission, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record approval or resubmission”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-113 · Capture daily site report offlineDONE · مكتملة

Site Engineer: As a Site Engineer, I want to capture daily site report offline, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Capture daily site report offline”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
  6. Each queued operation has stable client operation ID, server version check, retry policy and user-visible conflict resolution.
BE-114 · Log manpower deliveries weather and delaysDONE · مكتملة

Site Engineer: As a Site Engineer, I want to log manpower deliveries weather and delays, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Log manpower deliveries weather and delays”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-115 · Generate consolidated RFI and submittal logsDONE · مكتملة

Site Engineer: As a Site Engineer, I want to generate consolidated RFI and submittal logs, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Generate consolidated RFI and submittal logs”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-116 · Register client subcontractor and supplier contractsDONE · مكتملة

Operations Lead: As a Operations Lead, I want to register client subcontractor and supplier contracts, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Register client subcontractor and supplier contracts”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-117 · Track expiry renewal and milestone datesDONE · مكتملة

Operations Lead: As a Operations Lead, I want to track expiry renewal and milestone dates, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Track expiry renewal and milestone dates”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-118 · Draft contract clause checklist for reviewDONE · مكتملة

Operations Lead: As a Operations Lead, I want to draft contract clause checklist for review, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft contract clause checklist for review”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-119 · Flag potentially missing contract clausesDONE · مكتملة

Operations Lead: As a Operations Lead, I want to flag potentially missing contract clauses, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Flag potentially missing contract clauses”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-120 · Create internal defect or blocked-task ticketDONE · مكتملة

Operations Lead: As a Operations Lead, I want to create internal defect or blocked-task ticket, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create internal defect or blocked-task ticket”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-121 · Create client snag ticket after handoverDONE · مكتملة

Operations Lead: As a Operations Lead, I want to create client snag ticket after handover, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create client snag ticket after handover”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-122 · Route ticket and escalate SLA breachDONE · مكتملة

Operations Lead: As a Operations Lead, I want to route ticket and escalate SLA breach, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Route ticket and escalate SLA breach”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-123 · Record ticket resolution evidenceDONE · مكتملة

Operations Lead: As a Operations Lead, I want to record ticket resolution evidence, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record ticket resolution evidence”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-124 · Create dedicated project document foldersDONE · مكتملة

Project Manager: As a Project Manager, I want to create dedicated project document folders, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create dedicated project document folders”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-125 · Upload and version drawingsDONE · مكتملة

Project Manager: As a Project Manager, I want to upload and version drawings, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Upload and version drawings”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-126 · Preview supported drawing formats without CAD editingDONE · مكتملة

Project Manager: As a Project Manager, I want to preview supported drawing formats without CAD editing, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Preview supported drawing formats without CAD editing”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-127 · Link drawing revision to task and submittalDONE · مكتملة

Project Manager: As a Project Manager, I want to link drawing revision to task and submittal, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Link drawing revision to task and submittal”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-128 · Archive approved proposal and BOQ PDFsDONE · مكتملة

Project Manager: As a Project Manager, I want to archive approved proposal and BOQ PDFs, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Archive approved proposal and BOQ PDFs”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-129 · Search archived decisions and lessons learnedDONE · مكتملة

Project Manager: As a Project Manager, I want to search archived decisions and lessons learned, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Search archived decisions and lessons learned”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-130 · Enforce tenant/project document ACLsDONE · مكتملة

Project Manager: As a Project Manager, I want to enforce tenant/project document ACLs, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Enforce tenant/project document ACLs”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-131 · Isolate archive indexing from live transaction performanceDONE · مكتملة

Project Manager: As a Project Manager, I want to isolate archive indexing from live transaction performance, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Isolate archive indexing from live transaction performance”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-132 · Export archived project packDONE · مكتملة

Project Manager: As a Project Manager, I want to export archived project pack, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Export archived project pack”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-133 · Create workflow from standard templateDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to create workflow from standard template, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create workflow from standard template”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-134 · Build stages and transitions in visual editorDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to build stages and transitions in visual editor, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Build stages and transitions in visual editor”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-135 · Configure transition conditions and role permissionsDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to configure transition conditions and role permissions, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure transition conditions and role permissions”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-136 · Bind mandatory quality gates to transitionsDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to bind mandatory quality gates to transitions, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Bind mandatory quality gates to transitions”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-137 · Validate workflow before publishingDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to validate workflow before publishing, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Validate workflow before publishing”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-138 · Version workflow and migrate active instances safelyDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to version workflow and migrate active instances safely, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Version workflow and migrate active instances safely”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-139 · Audit configuration changes and rollbackDONE · مكتملة

Tenant Administrator: As a Tenant Administrator, I want to audit configuration changes and rollback, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Audit configuration changes and rollback”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-140 · Download offline-ready assigned project dataDONE · مكتملة

Site Engineer: As a Site Engineer, I want to download offline-ready assigned project data, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Download offline-ready assigned project data”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Each queued operation has stable client operation ID, server version check, retry policy and user-visible conflict resolution.
BE-141 · Create queued task updates while disconnectedDONE · مكتملة

Site Engineer: As a Site Engineer, I want to create queued task updates while disconnected, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Create queued task updates while disconnected”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-142 · Capture material usage and daily report offlineDONE · مكتملة

Site Engineer: As a Site Engineer, I want to capture material usage and daily report offline, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Capture material usage and daily report offline”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
  6. Each queued operation has stable client operation ID, server version check, retry policy and user-visible conflict resolution.
BE-143 · Sync queued changes on reconnectDONE · مكتملة

Site Engineer: As a Site Engineer, I want to sync queued changes on reconnect, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Sync queued changes on reconnect”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Each queued operation has stable client operation ID, server version check, retry policy and user-visible conflict resolution.
BE-144 · Resolve optimistic-version conflicts visiblyDONE · مكتملة

Site Engineer: As a Site Engineer, I want to resolve optimistic-version conflicts visibly, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Resolve optimistic-version conflicts visibly”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-145 · Retry failed uploads without duplicate recordsDONE · مكتملة

Site Engineer: As a Site Engineer, I want to retry failed uploads without duplicate records, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Retry failed uploads without duplicate records”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-146 · Import validated Excel template and show row errorsDONE · مكتملة

Site Engineer: As a Site Engineer, I want to import validated Excel template and show row errors, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Import validated Excel template and show row errors”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-147 · Export BOQ and operational reports to ExcelDONE · مكتملة

Site Engineer: As a Site Engineer, I want to export BOQ and operational reports to Excel, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Export BOQ and operational reports to Excel”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-148 · Draft project charter and baseline planDONE · مكتملة

Project Manager: As a Project Manager, I want to draft project charter and baseline plan, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft project charter and baseline plan”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
  6. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-149 · Suggest task sequencing and resource allocationDONE · مكتملة

Project Manager: As a Project Manager, I want to suggest task sequencing and resource allocation, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Suggest task sequencing and resource allocation”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-150 · Generate BOQ draft from scope and drawingsPARTIAL · جزئية

Project Manager: As a Project Manager, I want to generate BOQ draft from scope and drawings, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Generate BOQ draft from scope and drawings”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-151 · Identify schedule cost and quality risksDONE · مكتملة

Project Manager: As a Project Manager, I want to identify schedule cost and quality risks, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Identify schedule cost and quality risks”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-152 · Draft supplier RFQ for human authorizationDONE · مكتملة

Project Manager: As a Project Manager, I want to draft supplier RFQ for human authorization, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft supplier RFQ for human authorization”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-153 · Propose change order impactDONE · مكتملة

Project Manager: As a Project Manager, I want to propose change order impact, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Propose change order impact”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-154 · Draft RFI site report and status reportDONE · مكتملة

Project Manager: As a Project Manager, I want to draft RFI site report and status report, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft RFI site report and status report”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-155 · Notify role-specific risk ownersDONE · مكتملة

Project Manager: As a Project Manager, I want to notify role-specific risk owners, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Notify role-specific risk owners”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-156 · Record approve/edit/reject feedbackDONE · مكتملة

Project Manager: As a Project Manager, I want to record approve/edit/reject feedback, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Record approve/edit/reject feedback”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. Given a consequential action, when approval is absent, then the official state remains unchanged; approval/rejection and rationale are immutable audit events.
BE-157 · Draft closeout and lessons learnedDONE · مكتملة

Project Manager: As a Project Manager, I want to draft closeout and lessons learned, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Draft closeout and lessons learned”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
  5. AI content is clearly marked draft, shows sources or uncertainty where available, and never self-approves official actions.
BE-158 · View portfolio status and marginDONE · مكتملة

Owner: As a Owner, I want to view portfolio status and margin, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View portfolio status and margin”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-159 · View budget vs actual by projectDONE · مكتملة

Owner: As a Owner, I want to view budget vs actual by project, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View budget vs actual by project”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-160 · View receivables payables and cash forecastDONE · مكتملة

Owner: As a Owner, I want to view receivables payables and cash forecast, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View receivables payables and cash forecast”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-161 · View overdue quality gates and risksDONE · مكتملة

Owner: As a Owner, I want to view overdue quality gates and risks, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “View overdue quality gates and risks”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-162 · Drill into material variance and open ticketsDONE · مكتملة

Owner: As a Owner, I want to drill into material variance and open tickets, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Drill into material variance and open tickets”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-163 · Configure role-based alerts and digestDONE · مكتملة

Owner: As a Owner, I want to configure role-based alerts and digest, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Configure role-based alerts and digest”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
BE-164 · Export dashboard reportsDONE · مكتملة

Owner: As a Owner, I want to export dashboard reports, so that my construction business can execute the process with traceability and minimal manual re-entry.

  1. Given a signed-in user with the required tenant/project permission, when the user performs “Export dashboard reports”, then the record is validated and persisted in the authoritative Odoo model.
  2. Given invalid or missing mandatory input, when submitted, then the API returns a field-level error and no partial business transaction is committed.
  3. Given a successful change, when the record is reopened, then the new state, responsible actor, timestamps and related project/company are visible.
  4. Given a user without permission or from another tenant, when the same action is attempted, then access is denied and no sensitive data is disclosed.
AI LOGIC · نسخة AI Logic، نُسخت في 17 نوفمبر 2026 من namaa-react-ksa.ngrok-free.app/demo.html