![O3 Solutions [Test] Help Center](https://downloads.intercomcdn.com/i/o/494610/c7673691aaf9ad5fa3d4b92e/920cc346e5bc700695f8563d6a7e929b.png)
Contents
Note: configuring Pre-conditions and automatic status transitions requires project admin access.
What are Pre-conditions?
Pre-conditions are a set of requirements for an Entity's status. In order to transition to a status, all of its Pre-conditions must be met.
When you try to transition an Entity to a status with unsatisfied Pre-conditions, you'll see a message similar to the one below.
Types of Pre-conditions
O3 supports the following Pre-conditions:
Name | Requirement |
Require 100% Developed | All Development Steps are completed |
Require 100% Constraint Free | All Constraints are completed; this does not include soft constraints or Constraints marked as N/A |
Require 100% Complete | All Execution Tasks are completed |
Require 100% Documented | All Deliverables are completed |
Require 100% Approved | All Approvals are completed |
Require > 0 % Complete | Entity has at least one Earned Hour |
Pre-conditions & Automatic Status Transitions
Automatic status transitions can be configured between two statuses in O3. These transitions are triggered once the later status's Pre-conditions are met.
For example, I have an automatic transition set up for my IWP between the Ready for Review and Approved statuses.
My Approved status has a Pre-condition of Require 100% Approved.
Once I am in the Ready for Review status and I clear the final approval, my IWP will automatically transition to Approved.
Want to learn more about work packaging in O3? Check out our XWP Overview article collection.