Review Projects: Difference between revisions
m (captions) |
|||
| Line 10: | Line 10: | ||
When in PHENOM > Manage Models > Projects, the user can see the Review Projects they have access to under the destination Project. Expand the destination project in the Project Tree, and then expand the Review Projects folder. | When in PHENOM > Manage Models > Projects, the user can see the Review Projects they have access to under the destination Project. Expand the destination project in the Project Tree, and then expand the Review Projects folder. | ||
[[File:ReviewProjectInTree2.png|thumb|600px|none]] | [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Only exists if a Review Project exists)]] | ||
To view the corresponding merge request for your Review Project, simply select the Review Project from the Project Tree. The user can also access the the related Review Project for a merge request on the pull or approve page where the Review Project was initiated. | To view the corresponding merge request for your Review Project, simply select the Review Project from the Project Tree. The user can also access the the related Review Project for a merge request on the pull or approve page where the Review Project was initiated. | ||
<br> | <br> | ||
Note that Review Projects cannot be copied or published. | Note that Review Projects cannot be copied or published. | ||
[[File:ReviewProjectSelect.png|800x512px|thumb|none]] | [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]] | ||
== Project Locking == | == Project Locking == | ||
While creating a review project from either the pull or approve page, the user may decide to enable the Project lock on the destination Project. While a Review Project is locked, model changes are completely restricted. The project lock may be lifted when finalizing the merge. Additionally, multiple Review Projects can exist simultaneously so it is important for the user to manage the single lock on the destination project during review. | |||
<br> | |||
Please note that while Project locking is optional, it is encouraged to use the Project lock to prevent external changes being made to the destination Project during review. | |||
[[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with locking destination project enabled.]] | |||
== Review Project Specific Pages == | == Review Project Specific Pages == | ||
== Sample Workflow == | == Sample Workflow == | ||
Revision as of 11:50, 8 January 2025
Review Projects 101
A Review Project in PHENOM is a temporary merge workspace merge created during the Push, Pull, and Approve Process. The objectives of a Review Project are to:
- Allow data modeling prior to finalizing the merge
- Facilitate a thorough review of incoming changes
- Provide additional features to aid the review process
Review Project Management
To learn about the creation of Review Projects, view the Push, Pull, and Approve Process.
When in PHENOM > Manage Models > Projects, the user can see the Review Projects they have access to under the destination Project. Expand the destination project in the Project Tree, and then expand the Review Projects folder.
To view the corresponding merge request for your Review Project, simply select the Review Project from the Project Tree. The user can also access the the related Review Project for a merge request on the pull or approve page where the Review Project was initiated.
Note that Review Projects cannot be copied or published.
Project Locking
While creating a review project from either the pull or approve page, the user may decide to enable the Project lock on the destination Project. While a Review Project is locked, model changes are completely restricted. The project lock may be lifted when finalizing the merge. Additionally, multiple Review Projects can exist simultaneously so it is important for the user to manage the single lock on the destination project during review.
Please note that while Project locking is optional, it is encouraged to use the Project lock to prevent external changes being made to the destination Project during review.
