CollaborationPre-Commit ValidationWe are introducing a new feature dedicated for server project validation - pre-commit validation. This validation will ensure that your project will be committed to the Teamwork Cloud without unwanted errors.
After pre-commit validation project was not committed and pre-commit validation result panel opened. Learn more about working with Pre-Commit Validation >> Teamwork Cloud Used Projects Auto Update PluginPreviously updating used projects to their latest versions was only possible manually which required a significant amount of effort. In this release, we are bringing a new plugin which fully covers the use case with two internal tools: - Command-line utility that performs the actual update of used projects,
- Used Project Auto Update Wizard that just in a few simple steps helps to configure the necessary input file for the command-line utility.
Used Projects Auto Update Wizard dialogs.Learn more about working with Used Projects Auto Update Plugin >> Back to top Major versions of Used ProjectsCollaborating in a team on a project which has a lot of used projects that tend to change frequently, results in a huge number of different used project versions on the server. However, only some of the versions are of significant importance, requiring to switch their versions in the using project. Considering that, we developed a mechanism which allows to specify when an update to a new used project version should be triggered. Learn more about working with Major versions of Used Projects >> Commit flow enhancementsUsability of Commit Project to the Server dialog was improved by: - automatically saves commit comment draft for later use,
- users can quickly mark server project version as major,
- commit information as commit comment and commit tag are remembered in case of unsuccessful commit.
Improved Commit Project to the Server dialog.Learn more about working with Commit flow enhancements >> Back to top Hide Used ProjectsThe Hidden Packages feature was improved. Now users can not only hide packages in their main model, but select a whole used project to be cut as well. This is useful whenever you want to avoid having unnecessary indirect project usages upon using a stripped-down version of your library or sub-system. Moreover, from now on a change in Hidden Packages configuration is treated as a model change and reported as such in various change-related panels. To finish-up Hidden Packages improvements for this release, we implemented a mechanism that notifies whenever a dedicated branch holding a stripped-down version of the model becomes inactive in other words - model content is no more hidden. Hide used projects as other packages. Changes will be shown in Containment tree and various change-related panels (e.g. Change Sets).Learn more about working with Hidden Packages >> Other Enhancements and Changes- The element locking feature was extended, now it is possible to lock elements without need to update a project to the latest version. However, this applies only for elements that are not modified in a latest version on the server.
For the convenience of the user, the Package permissions feature has been extended with an ability to assign permissions for the whole group of users. As project development goes, users might end up with a long list of branches, which consist of working branches and branches which are left only for historic purpose. To make it easier to navigate in lists like this, now user simply can archivate branches. - We extend usability of several collaboration-related dialogs by adding search bar. This will help to deal with a large amount of projects in dialogs like Use Server Project, History, Open Server Project.
- We improved Mount relation display in the containment tree, this improvement will allow easily distinguish mounted package and immediately know from which used project it came.
Back to top |