org.manager Version Upgrades and Releases

Navigo upgrades every org.manager Cloud Hosted environment to each new release as part of the managed service. Each release is tested by Navigo before it reaches any customer, applied in a window outside business hours with up to 60 minutes of downtime, and leaves your data, models and configuration exactly as they were.

This article covers org.manager Cloud Hosted. If you use org.manager for SAP SuccessFactors, releases are applied by Ingentis on the SAP Business Technology Platform on a separate calendar, with the test tenant upgraded about two weeks before production. See OMSF Release Notes for that cycle.

The release cycle

org.manager version updates are issued every four months, giving three releases a year. Versions are numbered by year and month, so 26.02, 26.06 and 26.10 are the three 2026 releases. Each release bundles new features, improvements, bug fixes and the security and performance updates for the application.

Windows patches for the servers that host your environment are applied separately, once a month after 9pm AEST, and take up to 60 minutes. Urgent security patches are applied as soon as practicable, with as much notice as the situation allows. Dates and times for releases, patching and any rare unplanned outage are published on the Navigo Status Page, which you can subscribe to for email updates.

Before a release reaches you

Navigo controls when each release is rolled out to Cloud Hosted customers. A release is not applied to any customer environment until Navigo has tested it.

When Ingentis publishes a release, Navigo deploys it to its own environments first and works through a regression test script covering data loads, publishing, access protection, visualisation, modelling and exports. Each new feature is tested individually and written up so that it can be configured for customers who want it, and the bug fixes are spot-checked. Anything that does not behave as described is raised with Ingentis before rollout, and the release is signed off internally before the customer schedule is set.

Customer release notes are written from this testing, so they describe what Navigo has verified rather than what the vendor announced. They are published on the Help Centre under SaaS Release Notes and linked from every upgrade notification.

How you are told

You receive an email ahead of each upgrade. It gives the scheduled window, a link to the release notes and a statement of what is required from you, which is normally nothing. A reminder goes out on the day as the window opens, and a completion notice follows as soon as access is restored.

Upgrades are scheduled in the evening, Australian Eastern time, so that users in Australia and New Zealand are not affected. If the proposed window falls in a critical period for your organisation, such as a payroll run or a restructure go-live, tell your Customer Success contact when you receive the notice and Navigo will work with you on the timing.

The upgrade window

During the window your users cannot open org.manager. Nothing else about your service changes: your scheduled data refreshes, SSO configuration and access rules are untouched, and the data feed from your HRIS continues on its normal schedule once the environment is back.

The application update itself takes up to 60 minutes per environment. The published window is longer than the update so that this testing has room, and the completion notice is sent as soon as your environment passes.

What is protected

An upgrade replaces the application software only. Your data, published charts, models, configuration, export profiles and access rules are held separately from the application and are carried forward unchanged. Navigo takes a backup of your environment before the upgrade begins, in addition to the daily backups described in org.manager Backups and Disaster Recovery.

If a release causes a problem in your environment, Navigo returns it to the previous version within the same window, either by redeploying the prior release or by restoring from the pre-upgrade backup, and investigates with Ingentis before rescheduling. Because the next scheduled data refresh reloads from your HRIS, a rollback does not leave your charts out of date.

After the upgrade

Navigo checks your environment before sending the completion notice: that the charts open, that every scheduled job runs, and that the directory, modelling and export features work. The following business day, the managed service team monitors your data refresh as usual and resolves anything the upgrade has affected.

New features are not switched on in your environment automatically. The upgrade makes them available, and your Navigo technical consultant configures the ones you want when you ask, so that a release never changes how your users work without your agreement. Read the release notes, decide what is useful, and raise a request with Navigo Support or your Customer Success contact to have it set up.

Test environments

Where your subscription includes a test environment, the release is applied there two weeks before production. You can use that fortnight to check the release against your own configuration and models and to try new features before they reach your users. Navigo applies the release to production on the scheduled date unless you raise an issue from your testing first.

Tips

Subscribe to the Status Page as well as receiving the notification emails, so that anyone in your team who administers org.manager sees patching and maintenance dates without relying on a forwarded email.

If you run a change advisory board, the notification email and the release notes are written to go straight into a change record. Ask your Solution Architect if you need the dates further ahead than the notification provides.

If you have questions about a release, or a feature in the release notes that you would like configured, contact Navigo Support.