If you don't see version number 23.25, please clear your browser's cache and refresh O3.

Please note this will be O3's last release for 2023. We'll see you again in 2024 with a combined release notes for 2023.26 and 2024.1!

Sorry, that sounded threatening.

What I'm trying to say is whenever you kicked off a background import for bulk-loading components to an IWP, any warnings (e.g., Component Already Exists on an IWP of the Same Purpose) were shown as errors. We're now showing those as warnings.

You've been warned!

Previously, if you forgot to add a CWP to an IWP upon creation, you'd have to do so from the IWP's Details form. This meant you missed out on inheriting the following fields from the parent CWP:

Now, whether you add a CWP to an IWP before or after creation (via the Construction Work Package field), the child IWP will inherit the above fields.

Internet on-site can be spotty, and this meant the push notifications for downloading reports in O3 could get lost.

To avoid this problem, we've reverted back to our previous method of downloading reports.

If it's a longer report, you can click OK and O3 will send you a notification via email when it's done.

Speaking of which, you might notice the option to download reports has gone missing!

Some projects included multiple report templates, which meant the action menu list was tedious to navigate.

Your new workflow will include (1) opening the action menu and (2) clicking on Generate Detail Report.

The Report Options menu now includes the Report Template field, where you'll choose which kind of report you want to use to download the Entity.

Previously, regardless of Contract, all users were able to select from the same list of Purposes.

We've introduced controls allowing you to restrict which users can select which Purposes when creating an IWP.

To set this up, go to (1) Project Settings > (2) Entity Settings (3) IWPs > (4) Purposes.

Then select any of your Purposes below or create a new one.

The following fields have been added to the Work Package Purpose Details form:

To restrict which contractors can see which Purposes, each of these fields needs to be populated. Leaving either of them blank means all users can access that Purpose.

When creating an IWP, input a Construction Work Package first to see the filters applied.

The Require > 0% Complete Pre-Condition now fires when an Entity's Earned Hours are greater than 0.

You can now add constraints to Team Boards in-bulk via import. All you need to do is include the destination Team Board in the import file.

We've added a tool tip to indicate which work packages were imported from the model.