https://kb.phenomportal.com/api.php?action=feedcontributions&feedformat=atom&user=Derek 2026-04-27T17:23:04Z User contributions MediaWiki 1.44.2 https://kb.phenomportal.com/index.php?title=Review_Project&diff=1413 2025-02-06T16:56:03Z

<p>Derek: actual updates</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> Once users have altered the review status of proposed changes and other review project content, they can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a proposed change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> All proposed changes are initially pending and cannot be edited until accepted. Accepting a pending change indicates it is ready for merging. Once accepted and edited, the proposed change may not be reverted back to pending. Please note that pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> [[File:DetailsAccept.png|1000px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> [[File:DetailsUnAccept.png|1000px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> [[File:DetailsReject.png|1000px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1412 2025-02-06T16:55:48Z

<p>Derek: updates</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> Once users have altered the review status of proposed changes and other review project content, they can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1411 2025-02-06T16:48:06Z

<p>Derek: new action images</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> Once users have altered the review status of proposed changes and other review project content, they can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a proposed change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> [[File:DetailsAccept.png|1000px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> [[File:DetailsUnAccept.png|1000px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> [[File:DetailsReject.png|1000px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=File:DetailsReject.png&diff=1410 2025-02-06T16:47:26Z

<p>Derek: </p> <hr /> <div>details reject button</div>

Derek https://kb.phenomportal.com/index.php?title=File:DetailsUnAccept.png&diff=1409 2025-02-06T16:46:27Z

<p>Derek: </p> <hr /> <div>un accept button details</div>

Derek https://kb.phenomportal.com/index.php?title=File:DetailsAccept.png&diff=1408 2025-02-06T16:45:14Z

<p>Derek: </p> <hr /> <div>details accept button</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1407 2025-02-06T16:09:22Z

<p>Derek: text again</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> Once users have altered the review status of proposed changes and other review project content, they can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1406 2025-02-06T16:07:37Z

<p>Derek: text</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> When finished altering the review status of proposed changes and other review project content, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1405 2025-02-06T16:06:13Z

<p>Derek: /* Finalize Merge */ more text changes</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Finalizing the merge will implement all pending and accepted changes, as well as any additional modifications made during the review process. Additionally the destination Project may be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1404 2025-02-06T15:55:57Z

<p>Derek: text change</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary workspace created to show the user the outcome of a [[Push,_Pull,_and_Approve_Process|Push, Pull, or Approve]] before actual merging. This project provides unique tools to examine the proposed changes of a Push or Pull and enables users to modify their project without affecting the destination of the merge. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1403 2025-02-06T15:37:24Z

<p>Derek: text edit</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review projects can be modified like standard projects but cannot be copied, published, or restructured (changing the Models). Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1402 2025-01-31T22:12:31Z

<p>Derek: minor text change again</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accepting Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Rejecting Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Reviewing Changes&lt;/u&gt; ===<br /> Reviewing a change with the 'Review of Proposed Changes' popup enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1401 2025-01-31T22:10:40Z

<p>Derek: minor text edits</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending. Pending changes will be automatically accepted when finalizing the merge.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1400 2025-01-31T22:08:39Z

<p>Derek: edits</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|350px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|350px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|850px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1399 2025-01-31T22:07:50Z

<p>Derek: increased img size</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|400px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|400px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|900px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1398 2025-01-31T22:05:09Z

<p>Derek: size change</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|300px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|300px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|800px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1397 2025-01-31T22:04:49Z

<p>Derek: minor fix</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|300px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|300px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> <br /> [[File:PreviewPopup.png|1000px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1396 2025-01-31T22:03:47Z

<p>Derek: finished updates</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links, if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|300px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|300px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==<br /> These actions are crucial for managing proposed review changes and are accessible from the [[Review_Project#Finalize_Merge|Finalize Merge page]] or the details page of a review change.<br /> <br /> === &lt;u&gt;Accept Changes&lt;/u&gt; ===<br /> Accepting a pending change indicates it is ready for merging. Once accepted, changes can be edited. If no edits have been made post-acceptance, the changes can be reverted to pending.<br /> <br /> Click the check icon to accept changes: [[File:AcceptBtn.png|150px|border]]<br /> <br /> Click the question mark icon to revert accepted changes back to pending: <br /> [[File:UnacceptBtn.png|105px|border]]<br /> <br /> === &lt;u&gt;Reject Changes&lt;/u&gt; ===<br /> Rejecting a pending change will instantly restore it to its original state. Only changes that are still pending can be rejected. To safeguard against the irreversible nature of rejection, it is strongly advised to make a Commit before rejecting any changes.<br /> <br /> Click the x-mark icon to reject changes: [[File:RejectBtn.png|150px|border]]<br /> <br /> === &lt;u&gt;Review Changes&lt;/u&gt; ===<br /> Reviewing a change enables users to compare the original state with the current proposed modifications. Differences are highlighted in bold in the proposed changes column.<br /> <br /> Click the magnifying glass icon to review changes: [[File:ReviewBtn.png|152px|border]]<br /> <br /> <br /> Below is an example of reviewing proposed changes with edits.<br /> [[File:PreviewPopup.png|1000px|border]]</div>

Derek https://kb.phenomportal.com/index.php?title=File:PreviewPopup.png&diff=1395 2025-01-31T22:02:48Z

<p>Derek: </p> <hr /> <div>preview popup</div>

Derek https://kb.phenomportal.com/index.php?title=File:ReviewBtn.png&diff=1394 2025-01-31T21:57:03Z

<p>Derek: </p> <hr /> <div>reviewBtn</div>

Derek https://kb.phenomportal.com/index.php?title=File:RejectBtn.png&diff=1393 2025-01-31T21:56:00Z

<p>Derek: </p> <hr /> <div>rejectBtn</div>

Derek https://kb.phenomportal.com/index.php?title=File:UnacceptBtn.png&diff=1392 2025-01-31T21:54:40Z

<p>Derek: </p> <hr /> <div>unacceptBtn</div>

Derek https://kb.phenomportal.com/index.php?title=File:AcceptBtn.png&diff=1391 2025-01-31T21:53:14Z

<p>Derek: </p> <hr /> <div>Acceptbtn</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1390 2025-01-31T21:22:58Z

<p>Derek: finalize merge section</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge2.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change to its parent, as links if available. This list lets users quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> After altering the review project content and the review status of review nodes, users can complete the merge process by clicking the 'Finalize Merge' button located in the top bar. Please note that any pending changes will be automatically accepted and merged. Additionally the destination Project will have to be unlocked while finalizing the merge.<br /> <br /> [[File:FinalizeMergeFinalize.png|1000px|border]]<br /> <br /> <br /> Below is an example of the finalize merge confirmation where there are pending changes and the destination project is locked. To proceed with the merge, the user should click 'Yes'. To review the remaining changes or make other edits, click 'No'.<br /> <br /> [[File:ConfirmFinalizeMerge.png|300px|border]]<br /> <br /> <br /> If the destination Project isn't locked and has been altered during the review, a rebase will be required. Rebasing synchronizes the current review with the latest changes from the destination Project. After rebasing, the user can restart the process of finalizing the merge.<br /> <br /> [[File:Rebase2.png|300px|border]]<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==</div>

Derek https://kb.phenomportal.com/index.php?title=File:Rebase2.png&diff=1389 2025-01-31T21:21:38Z

<p>Derek: </p> <hr /> <div>updated rebase img</div>

Derek https://kb.phenomportal.com/index.php?title=File:Rebase.png&diff=1388 2025-01-31T21:20:20Z

<p>Derek: </p> <hr /> <div>this is an image of the rebase confirmation</div>

Derek https://kb.phenomportal.com/index.php?title=File:ConfirmFinalizeMerge.png&diff=1387 2025-01-31T21:02:16Z

<p>Derek: </p> <hr /> <div>confirming finalize merge</div>

Derek https://kb.phenomportal.com/index.php?title=File:FinalizeMergeFinalize.png&diff=1386 2025-01-31T20:54:33Z

<p>Derek: </p> <hr /> <div>finalize merge button</div>

Derek https://kb.phenomportal.com/index.php?title=File:FinalizeMerge2.png&diff=1385 2025-01-31T20:45:03Z

<p>Derek: </p> <hr /> <div>updated finalize merge page</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1384 2025-01-31T20:39:00Z

<p>Derek: init finalize merge</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page serves as a central hub where users can finalize their merge and review the changes they've selected, either from the initial Review Project creation or from updates made on the [[Review_Project#Update_Review|Update Review page]]. Users may create a Commit directly from the Finalize Merge page, allowing them to establish a safety net before [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting or rejecting]] changes, without having to visit the [[Review_Project#Commits|Commits page]].<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> [[File:FinalizeMerge.png|1000px|border]]<br /> <br /> The 'Review Nodes' list connects each review change its parent, if available. This list lets quickly access the change's details page to see the specific updates. Users can also view the review status from the Finalize Merge page, NavTree or the details page. For guidance on changing the review status of a change and or its children, please refer to the section on [[Review_Project#Accepting,_Rejecting,_&amp;_Reviewing_Changes|accepting, rejecting, &amp; reviewing Changes]].<br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==</div>

Derek https://kb.phenomportal.com/index.php?title=File:FinalizeMerge.png&diff=1383 2025-01-31T20:10:02Z

<p>Derek: </p> <hr /> <div>This is the finalize merge page.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1382 2025-01-31T19:23:50Z

<p>Derek: new section</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.<br /> <br /> == Accepting, Rejecting, &amp; Reviewing Changes ==</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1381 2025-01-31T19:20:04Z

<p>Derek: smaller image</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|600px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1380 2025-01-31T19:19:49Z

<p>Derek: image border updates</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|700px|border]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|1000px|border]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> <br /> [[File:ProjectLocking.png|1000px|border]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> <br /> [[File:CommitsInit.png|1000px|border]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> <br /> [[File:CommitRollback.png|1000px|border]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> <br /> [[File:UpdateReview2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Push,_Pull,_and_Approve_Process&diff=1379 2025-01-31T19:11:23Z

<p>Derek: fixed image positioning</p> <hr /> <div>== Pulling Changes from the Parent ==<br /> <br /> === &lt;u&gt;Pull Request&lt;/u&gt; ===<br /> Pulling allows you to get changes from the project you have inherited from. These changes can either be accepted or ignored.<br /> <br /> To pull from your parent project, open the tab shown below:<br /> <br /> [[File:Pull1 2.png|1000px|border]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Pull Review Project&lt;/u&gt; ===<br /> Instead of a traditional pull, you may decide to create a pull [[Review Projects | Review Project]]<br /> . Select the changes as you would in a traditional pull, but then check the 'New Review Project' option. You will need to specify a name and description of the pull [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable Project Locking. Only one pull [[Review Projects | Review Project]] can exist per child.<br /> <br /> To create a pull [[Review Projects | Review Project]], see the image below:<br /> <br /> [[File:PullReviewProject.png|1000px|border]]<br /> <br /> After the pull [[Review Projects | Review Project]] is created, the pull page will display it's details.<br /> <br /> == Pushing Changes to the Parent == <br /> To push your changes to your parent project with a push request, open the tab shown below:<br /> <br /> [[File:PushRequest.png|1000px|border]]<br /> <br /> You may select any changes made in the tree on the left or from the Merge Summary, specify the push requests name and description, then press the &quot;Request Push&quot; button. This will not result in any change to your parent project yet, as these changes must be approved by someone with the correct permissions on your parent project.<br /> <br /> == Approving Changes from a Child ==<br /> <br /> === &lt;u&gt;Push Request&lt;/u&gt; ===<br /> To approve changes that have been requested from one of your children projects, open the tab shown below:<br /> <br /> [[File:ApprovePushRequest2.png|1000px|border]]<br /> <br /> This tab shows any push requests as 'Merge Requests' that have been made by any of your child projects in addition to the completed and deleted push requests. On selection of one of these options, you may select which of the requested changes you would like to make to your model by selecting them in the tree on the left or from the Merge Summary, then hitting the 'Approve' button.<br /> <br /> The merge may fail and tell you that you are missing certain model elements. These could be something such as trying to merge and attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Push Review Project&lt;/u&gt; ===<br /> Instead of a traditional approve, you may decide to create a push [[Review Projects | Review Project]] instead. Select the changes as you would in a traditional push, but then check the 'New Review Project' option. You will need to specify a name and description of the push [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable the [[Review_Projects#Project_Locking|Project Lock]] for the destination Project. Note that only one [[Review Projects | Review Project]] may exist per push request.<br /> <br /> To create a push [[Review Projects | Review Project]], see the image below:<br /> <br /> [[File:ApproveReviewProject2.png|1000px|border]]<br /> <br /> After the [[Review Projects | Review Project]] is created, selecting the corresponding push request will display it's details.</div>

Derek https://kb.phenomportal.com/index.php?title=Push,_Pull,_and_Approve_Process&diff=1378 2025-01-31T19:07:59Z

<p>Derek: updated image borders</p> <hr /> <div>== Pulling Changes from the Parent ==<br /> <br /> === &lt;u&gt;Pull Request&lt;/u&gt; ===<br /> Pulling allows you to get changes from the project you have inherited from. These changes can either be accepted or ignored.<br /> <br /> To pull from your parent project, open the tab shown below:<br /> [[File:Pull1 2.png|1000px|border]]<br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Pull Review Project&lt;/u&gt; ===<br /> Instead of a traditional pull, you may decide to create a pull [[Review Projects | Review Project]]<br /> . Select the changes as you would in a traditional pull, but then check the 'New Review Project' option. You will need to specify a name and description of the pull [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable Project Locking. Only one pull [[Review Projects | Review Project]] can exist per child.<br /> <br /> To create a pull [[Review Projects | Review Project]], see the image below:<br /> [[File:PullReviewProject.png|1000px|border]]<br /> After the pull [[Review Projects | Review Project]] is created, the pull page will display it's details.<br /> <br /> == Pushing Changes to the Parent == <br /> To push your changes to your parent project with a push request, open the tab shown below:<br /> [[File:PushRequest.png|1000px|border]]<br /> <br /> You may select any changes made in the tree on the left or from the Merge Summary, specify the push requests name and description, then press the &quot;Request Push&quot; button. This will not result in any change to your parent project yet, as these changes must be approved by someone with the correct permissions on your parent project.<br /> <br /> == Approving Changes from a Child ==<br /> <br /> === &lt;u&gt;Push Request&lt;/u&gt; ===<br /> To approve changes that have been requested from one of your children projects, open the tab shown below:<br /> [[File:ApprovePushRequest2.png|1000px|border]]<br /> <br /> This tab shows any push requests as 'Merge Requests' that have been made by any of your child projects in addition to the completed and deleted push requests. On selection of one of these options, you may select which of the requested changes you would like to make to your model by selecting them in the tree on the left or from the Merge Summary, then hitting the 'Approve' button.<br /> <br /> The merge may fail and tell you that you are missing certain model elements. These could be something such as trying to merge and attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Push Review Project&lt;/u&gt; ===<br /> Instead of a traditional approve, you may decide to create a push [[Review Projects | Review Project]] instead. Select the changes as you would in a traditional push, but then check the 'New Review Project' option. You will need to specify a name and description of the push [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable the [[Review_Projects#Project_Locking|Project Lock]] for the destination Project. Note that only one [[Review Projects | Review Project]] may exist per push request.<br /> <br /> To create a push [[Review Projects | Review Project]], see the image below:<br /> [[File:ApproveReviewProject2.png|1000px|border]]<br /> <br /> After the [[Review Projects | Review Project]] is created, selecting the corresponding push request will display it's details.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Projects&diff=1377 2025-01-10T17:26:04Z

<p>Derek: Derek moved page Review Projects to Review Project: Removed plural projects -&gt; Review Project</p> <hr /> <div>#REDIRECT [[Review Project]]</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1376 2025-01-10T17:26:04Z

<p>Derek: Derek moved page Review Projects to Review Project: Removed plural projects -&gt; Review Project</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Review Projects folder only exists if a Review Project exists for the desination Project)]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|795x795px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Manage_Models&diff=1375 2025-01-10T17:23:25Z

<p>Derek: /* Review Projects */</p> <hr /> <div>==[[Projects and Models Management]]==<br /> <br /> ==[[Push, Pull, and Approve Process]]==<br /> Within Manage, the Branch tab is where users manage branching, including the ability to switch branches, pull changes from the parent branch, request to push changes to the parent branch, and approve push requests. Additionally, after initiating a push/pull request, users may create a Review Project, a snapshot of their project that allows for modification and review of the modeling content before finalizing the merge.<br /> <br /> ==[[Review Project]]==<br /> Before either pulling changes or approving a push request, users have the option to initiate a Review Project. This Review Project serves as a snapshot of the destination Project, incorporating the selected merge changes. Within the Review Project, users can find specific review pages within the Review tab to enhance the evaluation of review changes. After the review process is finished users may decide to finalize the merge and unlock the destination Project.<br /> <br /> ==[[Creating a Filtered Project]]==<br /> In some instances, a user may wish to share only a small part of a project with another user, without burdening them with the entirety of it. If the user you are sharing with only needs access to a few views or a subset of the measurements available, this functionality can be utilized to build a new filtered project that maintains its model inheritance relationship with the initial project. Any changes made to this new project can be pushed up to the initial project, and any changes made in the initial project can be pulled down to the filtered project so long as the changes are to a non-filtered element.<br /> <br /> ==[[Changesets]]==<br /> Within Manage, the Change Sets tab is where users can create or view a change set and its contents.<br /> <br /> == [[Permissions]] ==<br /> Permissions allow users to control who can see and edit project and model content.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1374 2025-01-08T19:11:52Z

<p>Derek: moved text review projects</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Review Projects folder only exists if a Review Project exists for the desination Project)]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> <br /> [[File:ReviewProjectSelect.png|795x795px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab when switched to a Review Project, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1373 2025-01-08T19:08:07Z

<p>Derek: image resizing</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Review Projects folder only exists if a Review Project exists for the desination Project)]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> &lt;br&gt;<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> [[File:ReviewProjectSelect.png|795x795px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Manage_Models&diff=1372 2025-01-08T19:02:30Z

<p>Derek: /* Review Projects */</p> <hr /> <div>==[[Projects and Models Management]]==<br /> <br /> ==[[Push, Pull, and Approve Process]]==<br /> Within Manage, the Branch tab is where users manage branching, including the ability to switch branches, pull changes from the parent branch, request to push changes to the parent branch, and approve push requests. Additionally, after initiating a push/pull request, users may create a Review Project, a snapshot of their project that allows for modification and review of the modeling content before finalizing the merge.<br /> <br /> ==[[Review Projects]]==<br /> Before either pulling changes or approving a push request, users have the option to initiate a Review Project. This Review Project serves as a snapshot of the destination Project, incorporating the selected merge changes. Within the Review Project, users can find specific review pages within the Review tab to enhance the evaluation of review changes. After the review process is finished users may decide to finalize the merge and unlock the destination Project.<br /> <br /> ==[[Creating a Filtered Project]]==<br /> In some instances, a user may wish to share only a small part of a project with another user, without burdening them with the entirety of it. If the user you are sharing with only needs access to a few views or a subset of the measurements available, this functionality can be utilized to build a new filtered project that maintains its model inheritance relationship with the initial project. Any changes made to this new project can be pushed up to the initial project, and any changes made in the initial project can be pulled down to the filtered project so long as the changes are to a non-filtered element.<br /> <br /> ==[[Changesets]]==<br /> Within Manage, the Change Sets tab is where users can create or view a change set and its contents.<br /> <br /> == [[Permissions]] ==<br /> Permissions allow users to control who can see and edit project and model content.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1371 2025-01-08T18:57:26Z

<p>Derek: text updates</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; Projects, the user can view the Review Projects they have access to under the destination Project within the Project Tree. Expand the destination Project in the Project Tree, then expand the Review Projects folder.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Review Projects folder only exists if a Review Project exists for the desination Project)]]<br /> <br /> To view the corresponding push/pull 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 push/pull request either on the pull or on the approve page where the Review Project was initiated.<br /> &lt;br&gt;<br /> <br /> Review Projects can be altered in every way that a normal project can, but they cannot be copied or published. Additionally, the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve pages]] are consolidated into the Review Tab, which contains [[Review_Projects#Review_Project_Specific_Pages| pages specific to the Review Project]].<br /> <br /> [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the modeling content while it's under review. Once the merge is ready to be finalized, the Project lock must be removed to finalize the merge. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any changes made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar of the page:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. Users can select additional changes from the push/pull request that were not initially chosen during the creation of the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1370 2025-01-08T18:42:46Z

<p>Derek: /* Review Projects 101 */</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace merge created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional pages to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; 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.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Only exists if a Review Project exists)]]<br /> <br /> 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 /> &lt;br&gt;<br /> <br /> Note that Review Projects cannot be copied or published.<br /> [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the model while it's under review. Once the merge is ready to be finalized, the Project lock can be removed. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any change made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]], in which the user may pull a subset of changes from the push/pull request that were not selected when creating the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.</div>

Derek https://kb.phenomportal.com/index.php?title=Push,_Pull,_and_Approve_Process&diff=1369 2025-01-08T18:41:35Z

<p>Derek: grammar</p> <hr /> <div>== Pulling Changes from the Parent ==<br /> <br /> === &lt;u&gt;Pull Request&lt;/u&gt; ===<br /> Pulling allows you to get changes from the project you have inherited from. These changes can either be accepted or ignored.<br /> <br /> To pull from your parent project, open the tab shown below:<br /> [[File:Pull1 2.png|none|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'Pull Changes' to immediately merge changes in a pull request.]]<br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Pull Review Project&lt;/u&gt; ===<br /> Instead of a traditional pull, you may decide to create a pull [[Review Projects | Review Project]]<br /> . Select the changes as you would in a traditional pull, but then check the 'New Review Project' option. You will need to specify a name and description of the pull [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable Project Locking. Only one pull [[Review Projects | Review Project]] can exist per child.<br /> <br /> To create a pull [[Review Projects | Review Project]], see the image below:<br /> [[File:PullReviewProject.png|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the pull Review Project from the pull page or from the Project Tree in Manage Models.]]<br /> After the pull [[Review Projects | Review Project]] is created, the pull page will display it's details.<br /> <br /> == Pushing Changes to the Parent == <br /> To push your changes to your parent project with a push request, open the tab shown below:<br /> [[File:PushRequest.png|none|thumb|800x800px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'Request Push' to create a push request. Push requests can be approved by the parent on the approve page.]]<br /> <br /> You may select any changes made in the tree on the left or from the Merge Summary, specify the push requests name and description, then press the &quot;Request Push&quot; button. This will not result in any change to your parent project yet, as these changes must be approved by someone with the correct permissions on your parent project.<br /> <br /> == Approving Changes from a Child ==<br /> <br /> === &lt;u&gt;Push Request&lt;/u&gt; ===<br /> To approve changes that have been requested from one of your children projects, open the tab shown below:<br /> [[File:ApprovePushRequest2.png|none|thumb|799x799px|none|none|A push request created from the child is selected in the parents approve page.]]<br /> <br /> This tab shows any push requests as 'Merge Requests' that have been made by any of your child projects in addition to the completed and deleted push requests. On selection of one of these options, you may select which of the requested changes you would like to make to your model by selecting them in the tree on the left or from the Merge Summary, then hitting the 'Approve' button.<br /> <br /> The merge may fail and tell you that you are missing certain model elements. These could be something such as trying to merge and attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Push Review Project&lt;/u&gt; ===<br /> Instead of a traditional approve, you may decide to create a push [[Review Projects | Review Project]] instead. Select the changes as you would in a traditional push, but then check the 'New Review Project' option. You will need to specify a name and description of the push [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable the [[Review_Projects#Project_Locking|Project Lock]] for the destination Project. Note that only one [[Review Projects | Review Project]] may exist per push request.<br /> <br /> To create a push [[Review Projects | Review Project]], see the image below:<br /> [[File:ApproveReviewProject2.png|none|thumb|799x799px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the push Review Project from the corresponding push request on the approve page or from the Project Tree in Manage Models.]]<br /> After the [[Review Projects | Review Project]] is created, selecting the corresponding push request will display it's details.</div>

Derek https://kb.phenomportal.com/index.php?title=Push,_Pull,_and_Approve_Process&diff=1368 2025-01-08T18:40:45Z

<p>Derek: /* Push Request */</p> <hr /> <div>== Pulling Changes from the Parent ==<br /> <br /> === &lt;u&gt;Pull Request&lt;/u&gt; ===<br /> Pulling allows you to get changes from the project you have inherited from. These changes can either be accepted or ignored.<br /> <br /> To pull from your parent project, open the tab shown below:<br /> [[File:Pull1 2.png|none|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'Pull Changes' to immediately merge changes in a pull request.]]<br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Pull Review Project&lt;/u&gt; ===<br /> Instead of a traditional pull, you may decide to create a pull [[Review Projects | Review Project]]<br /> . Select the changes as you would in a traditional pull, but then check the 'New Review Project' option. You will need to specify a name and description of the pull [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable Project Locking. Only one pull [[Review Projects | Review Project]] can exist per child.<br /> <br /> To create a pull [[Review Projects | Review Project]], see the image below:<br /> [[File:PullReviewProject.png|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the pull Review Project from the pull page or from the Project Tree in Manage Models.]]<br /> After the pull [[Review Projects | Review Project]] is created, the pull page will display its details.<br /> <br /> == Pushing Changes to the Parent == <br /> To push your changes to your parent project with a push request, open the tab shown below:<br /> [[File:PushRequest.png|none|thumb|800x800px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'Request Push' to create a push request. Push requests can be approved by the parent on the approve page.]]<br /> <br /> You may select any changes made in the tree on the left or from the Merge Summary, specify the push requests name and description, then press the &quot;Request Push&quot; button. This will not result in any change to your parent project yet, as these changes must be approved by someone with the correct permissions on your parent project.<br /> <br /> == Approving Changes from a Child ==<br /> <br /> === &lt;u&gt;Push Request&lt;/u&gt; ===<br /> To approve changes that have been requested from one of your children projects, open the tab shown below:<br /> [[File:ApprovePushRequest2.png|none|thumb|799x799px|none|none|A push request created from the child is selected in the parents approve page.]]<br /> <br /> This tab shows any push requests as 'Merge Requests' that have been made by any of your child projects in addition to the completed and deleted push requests. On selection of one of these options, you may select which of the requested changes you would like to make to your model by selecting them in the tree on the left or from the Merge Summary, then hitting the 'Approve' button.<br /> <br /> The merge may fail and tell you that you are missing certain model elements. These could be something such as trying to merge and attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Push Review Project&lt;/u&gt; ===<br /> Instead of a traditional approve, you may decide to create a push [[Review Projects | Review Project]] instead. Select the changes as you would in a traditional push, but then check the 'New Review Project' option. You will need to specify a name and description of the push [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable the [[Review_Projects#Project_Locking|Project Lock]] for the destination Project. Note that only one [[Review Projects | Review Project]] may exist per push request.<br /> <br /> To create a push [[Review Projects | Review Project]], see the image below:<br /> [[File:ApproveReviewProject2.png|none|thumb|799x799px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the push Review Project from the corresponding push request on the approve page or from the Project Tree in Manage Models.]]<br /> After the [[Review Projects | Review Project]] is created, selecting the corresponding push request will display its details.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1367 2025-01-08T18:39:59Z

<p>Derek: /* Update Review */</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace merge created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional features to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; 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.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Only exists if a Review Project exists)]]<br /> <br /> 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 /> &lt;br&gt;<br /> <br /> Note that Review Projects cannot be copied or published.<br /> [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the model while it's under review. Once the merge is ready to be finalized, the Project lock can be removed. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any change made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]], in which the user may pull a subset of changes from the push/pull request that were not selected when creating the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update Review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1366 2025-01-08T18:38:52Z

<p>Derek: /* Update Review */</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace merge created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional features to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; 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.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Only exists if a Review Project exists)]]<br /> <br /> 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 /> &lt;br&gt;<br /> <br /> Note that Review Projects cannot be copied or published.<br /> [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the model while it's under review. Once the merge is ready to be finalized, the Project lock can be removed. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any change made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]], in which the user may pull a subset of changes from the push/pull request that were not selected when creating the Review Project. These changes can either be accepted or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update review page with several additions not yet merged into the Review Project from the associated push/pull request.]]<br /> <br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.</div>

Derek https://kb.phenomportal.com/index.php?title=Push,_Pull,_and_Approve_Process&diff=1365 2025-01-08T18:38:30Z

<p>Derek: underline subheaders</p> <hr /> <div>== Pulling Changes from the Parent ==<br /> <br /> === &lt;u&gt;Pull Request&lt;/u&gt; ===<br /> Pulling allows you to get changes from the project you have inherited from. These changes can either be accepted or ignored.<br /> <br /> To pull from your parent project, open the tab shown below:<br /> [[File:Pull1 2.png|none|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'Pull Changes' to immediately merge changes in a pull request.]]<br /> Here you will be prompted to select nodes from the tree on the left or from the Merge Summary. You may choose to ignore certain changes and accept others. Any changes accepted will overwrite your current version of those model elements. The pull may fail and tell you that you are missing certain model elements. These could be something such as trying to merge an attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Pull Review Project&lt;/u&gt; ===<br /> Instead of a traditional pull, you may decide to create a pull [[Review Projects | Review Project]]<br /> . Select the changes as you would in a traditional pull, but then check the 'New Review Project' option. You will need to specify a name and description of the pull [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable Project Locking. Only one pull [[Review Projects | Review Project]] can exist per child.<br /> <br /> To create a pull [[Review Projects | Review Project]], see the image below:<br /> [[File:PullReviewProject.png|thumb|800x800px|none|none|After creating changes in the parent, switch to the child, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the pull Review Project from the pull page or from the Project Tree in Manage Models.]]<br /> After the pull [[Review Projects | Review Project]] is created, the pull page will display its details.<br /> <br /> == Pushing Changes to the Parent == <br /> To push your changes to your parent project with a push request, open the tab shown below:<br /> [[File:PushRequest.png|none|thumb|800x800px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'Request Push' to create a push request. Push requests can be approved by the parent on the approve page.]]<br /> <br /> You may select any changes made in the tree on the left or from the Merge Summary, specify the push requests name and description, then press the &quot;Request Push&quot; button. This will not result in any change to your parent project yet, as these changes must be approved by someone with the correct permissions on your parent project.<br /> <br /> == Approving Changes from a Child ==<br /> <br /> === &lt;u&gt;Push Request&lt;/u&gt; ===<br /> To approve changes that have been requested from one of your children projects, open the tab shown below:<br /> [[File:ApprovePushRequest2.png|none|thumb|799x799px|none|none|A push request created from the child is selected in the parents approve page.]]<br /> <br /> This tab shows any push requests as 'Merge Requests' that have been made by any of your child projects in addition to the completed and deleted push requests. On selection of one of these options, you may select which of the requested changes you would like to make to your model by selecting them in the tree on the left or from the Merge Summary, then hitting the &quot;Approve&quot; button.<br /> <br /> The merge may fail and tell you that you are missing certain model elements. These could be something such as trying to merge and attribute of an entity without including the entity itself, or a Service but not the view that it points to, etc.<br /> <br /> === &lt;u&gt;Push Review Project&lt;/u&gt; ===<br /> Instead of a traditional approve, you may decide to create a push [[Review Projects | Review Project]] instead. Select the changes as you would in a traditional push, but then check the 'New Review Project' option. You will need to specify a name and description of the push [[Review Projects | Review Project]]. To ensure that the integrity of the model contents is maintained during review, you may also decide to enable the [[Review_Projects#Project_Locking|Project Lock]] for the destination Project. Note that only one [[Review Projects | Review Project]] may exist per push request.<br /> <br /> To create a push [[Review Projects | Review Project]], see the image below:<br /> [[File:ApproveReviewProject2.png|none|thumb|799x799px|none|none|After creating changes in the child, switch to the parent, select any changes, then select 'New Review Project' to start creating the Review Project. After creation you may view the push Review Project from the corresponding push request on the approve page or from the Project Tree in Manage Models.]]<br /> After the [[Review Projects | Review Project]] is created, selecting the corresponding push request will display its details.</div>

Derek https://kb.phenomportal.com/index.php?title=Review_Project&diff=1364 2025-01-08T18:36:35Z

<p>Derek: /* Update Review */</p> <hr /> <div>== Review Projects 101 ==<br /> A '''Review Project''' in PHENOM is a temporary merge workspace merge created during the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]]. The objectives of a Review Project are to:<br /> * Allow data modeling prior to finalizing the merge<br /> * Facilitate a thorough review of incoming changes<br /> * Provide additional features to aid the review process<br /> <br /> == Review Project Management ==<br /> To learn about the creation of Review Projects, view the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]].<br /> <br /> When in PHENOM &gt; Manage Models &gt; 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.<br /> <br /> [[File:ReviewProjectInTree2.png|thumb|600px|none|Viewing the Review Projects folder. (Only exists if a Review Project exists)]]<br /> <br /> 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 /> &lt;br&gt;<br /> <br /> Note that Review Projects cannot be copied or published.<br /> [[File:ReviewProjectSelect.png|800x512px|thumb|none|Selecting the Review Project and viewing the associated Merge Request.]]<br /> <br /> == Project Locking ==<br /> When initiating a Review Project from either the pull or approve page, users have the option to secure the destination Project by selecting 'Lock Current Project During Review'. This lock ensures that no changes can be made to the model while it's under review. Once the merge is ready to be finalized, the Project lock can be removed. 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 /> &lt;br&gt;<br /> <br /> 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.<br /> [[File:ProjectLocking.png|800x512px|thumb|none|Creation of Review Project on the pull page with 'Lock Current Project During Review' enabled.]]<br /> <br /> == Review Project Specific Pages ==<br /> === &lt;u&gt;Finalize Merge&lt;/u&gt; ===<br /> The Finalize Merge page functions as a hub where users can review the changes selected from the push/pull request and finalize the merge directly.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Finalize Merge, as seen below:<br /> <br /> <br /> === &lt;u&gt;Commits&lt;/u&gt; ===<br /> The Commits page lists each Commit point for the Review Project. Commits enable users to roll back the Review Project to a previous version, reflecting the model content as it was at the time the Commit was created.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Commit, as seen below:<br /> [[File:CommitsInit.png|800x512px|thumb|none|Commits page with the initial Commit displayed within the list.]]<br /> <br /> When the Review Project is initiated, an initial Commit is always created. Additionally, the user can create a Commit at any time during the review from the Commit page or before rejection of review changes.<br /> &lt;br&gt;<br /> <br /> Users can rollback to any Commit at any time. It's crucial to understand that rolling back to a Commit will delete all subsequent Commits and revert any change made after that Commit. To rollback to a Commit, simply select the desired Commit from the list, then click the 'Rollback To Commit' icon located in the top bar:<br /> [[File:CommitRollback.png|800x512px|thumb|none|Selecting a Commit to rollback changes.]]<br /> <br /> === &lt;u&gt;Update Review&lt;/u&gt; ===<br /> The Update Review page is very similar to the pull page found in the [[Push,_Pull,_and_Approve_Process|Push, Pull, and Approve Process]], in which the user may pull a subset of changes from the push/pull request that were not selected when creating the Review Project. These changes can either be pulled or ignored.<br /> &lt;br&gt;<br /> <br /> Accessed from a Review Project in PHENOM &gt; Manage Models &gt; Review &gt; Update Review, as seen below:<br /> [[File:UpdateReview2.png|800x512px|thumb|none|Update review page with several additions not yet merged into the Review Project from the associated push/pull request.]]</div>

Derek