NotrinosERP 1.1.0

RELEASE DOWNLOAD

LASTEST UPDATE

NotrinosERP 1.1.0 brings major HRM and payroll improvements, stronger security, faster employee loading, and a single-step database upgrade from the official 1.0.0 release.
What’s new

  • Expanded HRM foundations for employee identities, employment records, organizational structure, and employee lifecycle workflows.
  • Employee and manager self-service improvements.
  • Payroll-core, country-pack, and global-payroll foundations with stronger authorization, auditability, and reconciliation controls.
  • Faster employee searches, attendance sheets, and leave-history loading.
  • Security fixes covering CRM authorization, translation-cache code injection, company-logo uploads, and SQL injection in financial reports.
  • Installation fixes and default-theme asset corrections.

Upgrading from 1.0.0
This upgrade supports the official 1.0.0 baseline, commit 3ce21901, including recognized installations that missed the earlier warranty and employee-document schema updates.

  1. Stop user activity and make a complete backup. Back up every company database, application files, configuration, uploads, attachments, and any private encryption or audit keys stored outside the application directory. Test the upgrade on a restored copy first.
  2. Deploy the complete 1.1.0 release (replace the source code). Preserve your config.php, config_db.php, company data, private storage, and customizations. The Software Upgrade screen updates the database; it does not download or replace application files.
  3. Log into the company being upgraded using an account with Software Upgrade permission.
  4. Open Setup → Software Upgrade, select that company, and click Upgrade once. Keep the page open until the operation finishes.
  5. Log in again. Confirm version 1.1.0, review the upgrade log, and check employees, documents, payroll, and financial reports. Review any document quarantine or migration notices.
  6. Repeat the process for each company database.

The installer creates a security backup before database changes, applies recognized legacy schema repairs, converts HRM records, and checks employee compatibility before accepting the new version. Keep the resulting private keys and files with future backups.
Do not run the installation wizard or import fresh-install SQL over an existing database.
If an upgrade fails, retain the log, security backup, and private recovery files. Review the reported recovery result before retrying. If restoration is required, restore the matching database, application files, and private storage together; do not manually change the database version marker.
See CHANGELOG.txt for the complete release history.