Before you begin: Verify the list of phases resides in the Phase data definition pull-down data set. This is the same list that is used when selecting a phase manually in the shell properties window. You can add or modify the default list as needed. This list makes the phases available for any shell instance or shell type template; for each shell or template, you select which of the phases to use. Create any business processes that you plan to use to drive gates conditions and phase completion.
Step 1: Define Phases. For each shell instance or shell type template, you define the list of phases to include in the setup, choosing from the entire list in the Phase data set.
Step 2: Define Gate Conditions. For each phase, define one or more gates conditions. A gate condition is a combination data element and trigger condition that enable transition to the next phase.
Step 3: Schedule Gates runs. The gates run the validation of gate conditions. You can schedule runs automatically. This is optional.
Step 4: Activate the Gates setup.
Step 5: Define permissions.
Note: If you create a new shell by copying a shell template or an existing shell, any existing gates setup in the source shell is copied into the new shell, including the gates status. The gates phases are restarted at the first phase in the new shell, and the scheduled gates run is activated.
Example of a gates setup and conditions
Add phases to the gates setup (Settings tab)
Access gate configuration view
Define gates runs schedule (Schedule tab)
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.