Rename, Copy or Remove Project
Projects may be copied, renamed or removed as full databases on the server directly from the application.
Projects may be copied, renamed or removed as full databases on the server directly from the application.
Note! Do not perform this operation when users are logged in to the project. This operation dettaches and reattaches the underlying database. The dettach action disconnects the database from the server. As a consequence, all users working in the project will lose the connection to the project and also lose all currently edited data.
Make sure affected users are notified before the remove action is initiated so they can log off in due time!
A Web Admin may copy an existing project on the server. This copy function, performs a complete copy of the database (as opposed to using branching in Project Hierarchy which only includes the latest revisions of selected objects) and you are requested to give the copy a new name before starting the operation.
To copy a project, select a project in the Select a Project dropdown.
Then check the Copy the Project checkbox.
Give the copied project a new name.
Note! The new name must not be the same as an existing project name (case-insensitive)!
Finally, click OK to initiate the copy operation. Wait for the confirmation message that indicates the success of the operation.
Since the source project will be temporarily unavailable for other users during the copying operation, make sure affected users are notified before the copy action is initiated so they can log off in due time!
All objects in the created copied project will be internally updated to reflect the new name, including objects in Word Documents.
Note! Copying in linked projects: If the project to be copied is a project in a linked project structure with items in other projects tracing to items in the project to be copied, these incoming traces from document objects in other projects will not be automatically copied and tracing to the resulting project. These traces need to be recreated manually!!
Note! Backlinks in External Issues: if the project contains document object that trace to items in external systems (such as Jira, GitHub, Azure DevOps etc.), these traces will be recreated in the project BUT if the external items contain fields for backlink information to Aligned Elements Document Objects, these backlinks in the external items are not updated to reflect that items in the resulting project now also point to these external items!
Note! Do not perform this operation when users are logged in to the project. This operation dettaches and reattaches the underlying database. The dettach action disconnects the database from the server. As a consequence, all users working in the project will lose the connection to the project and also lose all currently edited data.
Make sure affected users are notified before the action is initiated so they can log off in due time!
A Web Admin may also rename any existing project. This operation is very similar to Copy Project, with the difference that only the new copy will remain. Any objects in the created copy will be internally updated to reflect the new name, including objects in Word Documents.
To rename a project, select a project in the Select a Project dropdown.
Then check the Rename the Project checkbox.
Enter the new name.
Finally, click OK to initiate the rename operation. Wait for the confirmation message that indicates the success of the operation.
Since the source project will be temporarily unavailable for other users during the renaming operation, make sure affected users are notified before the rename action is initiated so they can log off in due time!
For safety, the source project database files (with the original names, mdf, ldf), are kept on the server and would need to be manually deleted or removed. To restore the source project again, an 'Attach Database' operation could be performed using e.g. SQL Management Studio.
Note! Do not perform this operation when users are logged in to the project. This operation dettaches the underlying database. The dettach action disconnects the database from the server. As a consequence, all users working in the project will lose the connection to the project and also lose all currently edited data.
Make sure affected users are notified before the remove action is initiated so they can log off in due time!
To remove any project, the Web Admin may do so using the Remove the Project from the Server operation.
To remove a project, select a project in the Select a Project dropdown.
Then check the Remove the Project from the Server checkbox.
Finally, click OK to initiate the removal operation. Wait for the confirmation message that indicates the success of the operation.
For safety, the source project database files, are kept on the server and would need to be manually deleted or removed. To restore the source project again, an 'Attach Database' operation could be performed using e.g. SQL Management Studio.
