Tell Us What You Think
Sending...
Thank you for your feedback
Keep all changes in central repository and perform modeling collaboratively and concurrently.
Concurrent modeling with VP Teamwork Server
VP Teamwork Server provides a central repository for storing Visual Paradigm project files. With VP Teamwork Server, team members can view and edit the same project or even same diagram simultaneously. The following movie demonstrates how to checkout project, commit changes to server and update changes from server. The latest version supports specifying read and write permissions when importing project to server.
Central File Repository
Keep files and documents in one single place. Comes with doors to past versions of files and their history. Prevent unwanted file overwriting by other users with conflict detection.
View and compare old revision with VP Teamwork Server
VP Teamwork Server keeps all histories of changes of diagrams and model elements. With VP Teamwork Server you can review and compare change histories of specific diagram and model element visually with the "Revision History" function. You can also export and open full project of old revisions. The following movie demonstrates how to open old revisions and use the revision history function to compare changes between revisions in diagram base and model element base.
Detect and resolve conflicts with VP Teamwork Server
VP Teamwork Server merges changes from different team members during commit or update. Let's say when two or more team members have modified the same model element, and performed commit or update one after the other, the merge engine will detect that there is a conflict occurred, and prompt to resolve the conflict. Conflicts can be resolved by overwrite (keep local change) or revert (keep server change). The following movie demonstrates how to resolve a conflict in Visual Paradigm for UML Teamwork Client.
