Release Notes

All platforms - CLI: You can now edit Xlinks in partial workspaces using the command line.

You can always edit a read-only Xlink to change the content that you are loading using it.

But you cannot do the same with a writable Xlink. You can only edit it to change the target branch and only until someone creates a change under the writable Xlink.

This happens because partial workspaces always point to the branch head, including writable Xlinks. As a result, writable Xlinks only care about branches instead of changeset IDs… even if you still have to specify changesets to create them.

Windows - Plastic: New Code Review system: If users apply the requested changes in a code review while having the code review window opened, the window will be updated correctly showing the requested changes as "Done", and the new changesets created as well.

Windows - Plastic: You can have multiple Branch Explorer windows open at the same time, showing different repositories. This means, if you're not paying full attention, you can switch to a branch or changeset that you didn't mean to and have to wait patiently while your workspace is overwritten by data from the wrong repository. You can switch back of course, but it can waste a lot of time.

We've added extra warning text to the confirmation dialog when we see that you are about to switch to a different repository, to reduce the chance of this mistake occurring.

Windows - Plastic: We've added dynamic date filtering to the Branch Explorer. You can easily set the Branch Explorer to show changesets from the past week, month or year. Most importantly, the filter updates dynamically so that it always only shows changesets within the specified time frame. Check it out in the gif below!

Screenshot

Windows - Plastic: The Workspace Explorer did not display errors properly. Now it's fixed.

macOS - Plastic: We've added dynamic date filtering to the Branch Explorer. You can easily set the Branch Explorer to show changesets from the past week, month or year. Most importantly, the filter updates dynamically so that it always only shows changesets within the specified time frame. Check it out in the gif below!

Screenshot

All platforms - Command line client: Now the "cm licenseinfo" command prints the information it was missing before for servers with Unlimited Users licenses. The information we omitted (because we considered it was somehow useless, sorry about that!) was the number of active users (the number of available users is useless if you have an unlimited number!) and the list of active and inactive users. Now, Unlimited Users licenses will see something like this:

$ cm licenseinfo

License information: server: very-secret-machine.home:8085

License information:

    Licensed to:            [c0d1c3]Personal license to test UnlimitedUsers
    Expiration date:        Unlimited
    Edition:                team
    Total licensed users:   Unlimited
    Total active users:     2

License usage:

    User                   Status
    ----------------------------------------------
    sergio                 ACTIVE
    pedro                  ACTIVE
    borja                  INACTIVE (Not licensed)
    enrique                INACTIVE (Not licensed)

Remember that you have some useful flags to further filter the users list - for example:

Print only active users:
    $ cm licenseinfo --active

Print only inactive users:
    $ cm licenseinfo --inactive

Windows - Plastic: Maybe you already know Plastic installation contains semantic merge tool feature out-of-the-box. However, in order to enable java files to be semantically merged, it is required a valid Java Virtual Machine (version >= 8). But, if no valid Java Virtual Machine is found, the merge operation for a java file will automatically fallback to regular, embedded text-based mergetool (a.k.a. XMerge tool).

Windows - Plastic: Added a dropdown button to the pending changes view to resolve pending Code Review change requests.

The new Code Review system allows the reviewer to request changes by the developer. Then, the developer can set those changes as resolved using pre-defined text in the checkin comment.

We added a dropdown button next to the checkin comment textbox:

Screenshot

When the developer selects a change, the checkin comment text is automatically filled and, after checking-in your changes, the change will be marked as applied in the changeset.

Screenshot

Command line client: Now, the "cm lock unlock" command help shows an example about undoing an item lock on a cloud server.

Windows - Plastic: Code reviews: Changed the default title. Now, it always use the reviewed object in the title.

Examples:

Review of branch /main/scm15425 - Refactor FileSystem.cs
Review of changeset 88 - Improve performance in tree filtering

Also, improved the alignment of titles and edit boxes in the header of the review, that were wrong before.