Commercial Notes can now create new folders and pages through the secured online workflow.
What changed
- Folder and page creation now sends the required device identity and idempotency key in the API request headers, preventing valid Commercial note changes from being rejected.
- Browser coverage now verifies creating both an independent Commercial folder and page.
Commercials now has its own private notes workspace, complete localized impact labels and category management within project financial settings.
What changed
- Approved and pending revenue and cost effects are translated naturally in every application language, and managers can add, rename or remove unused default and custom budget categories from Commercial settings.
- Commercial notes now use a dedicated permission-controlled notebook that shares no pages or folders with the Project Notebook and remains outside the project offline cache.
Language changes remain available while a pending database update resumes safely after an interrupted deployment.
What changed
- The Commercials database update can resume after a partial database change without trying to recreate completed columns or tables.
- Changing the application language no longer depends on the new currency and calendar columns being present during the short deployment transition.
Account-wide language, calendar, reference currency and marketing settings now live together, while Commercials gains contextual guidance, grouped values, attachments and direct project notes.
What changed
- Persian accounts default to the Solar Hijri calendar and Toman; other accounts default to the Gregorian calendar and USD, with both choices available from Global settings.
- Commercial forms now explain their fields, group financial digits, accept manager-quota private attachments for expenses, payments, receipts and commitments, and open the existing project notebook as Commercial notes.
Backup reminders can now use in-app, email and Telegram delivery together without rejecting the schedule.
What changed
- The reminder validator now accepts all three distinct supported channels while retaining the requirement to select at least one.
- Removed the redundant channel availability note from the scheduling form for a cleaner interface.
Project teams can manage budgets, costs, client receipts, commitments and modification impacts in one permission-controlled workspace.
What changed
- Added server-calculated commercial health, category forecasts, partial payment receipts, commitment conversion, localized spreadsheet import and export, verified private attachments and financial activity history.
- Financial access is off for members by default, granted as one explicit bundle, excluded from offline project caches and backed by optimistic locking, audit events and scheduled due-payment reminders.
Installed versions, backup verification and backup reminders now select their source from the project document and revision register.
What changed
- Users enter only the system name and choose a searchable document and revision instead of copying equipment or revision identifiers and repeating technical metadata.
- Software, version, service pack, file checksum and revision designations remain sourced from the controlled revision, while each new backup reminder retains its selected revision reference.
Project zones now organize Equipment, I/O and Industrial network records through one consistent structure.
What changed
- The I/O and Industrial network forms, lists and zone filters use the same project-defined zones and default Z01 assignment as Equipment.
- Zone names now round-trip through CSV and Excel export, validation and import for all three registers; existing I/O and network records move safely into the default zone.
Equipment can now be grouped into up to 40 project-defined zones with durable naming and spreadsheet support.
What changed
- Every project starts with the Z01 zone, and the equipment form places its required zone immediately after Manufacturer.
- The Equipment view can add and filter zones, rename them from the right-click menu, and retain zone names through CSV and Excel export, validation and import.
Email, bot and browser-push histories now identify recipients accurately and preserve their preferred language for delivery review.
What changed
- Accounts without a display name remain linked as unnamed accounts, while external or system recipients are distinguished from genuinely unavailable user records.
- Each user delivery stores and displays the channel-appropriate preferred-language snapshot beside the complete recorded content, and existing user delivery rows are backfilled during migration.
