In Dimensions CM 10.1.2 when a folder is deleted from a Dimensions project that folder is only removed from areas associated with the first stage. Other deployment areas are only affected when the AUDIT feature is used on the area. When AUDIT removes folders from a deployment area the same issue described in the 10.1.1 section above can occur.
... applies to all Dimensions CM customers on versions ... of files and folders ) in projects ... ... When files or folders are refactored ( ... ... affected file/ folder . ... is propagated to areas attached to a ... ... At that time Dimensions CM will correctly rename ... disk in any areas associated with the ... disk in any areas associated with " ... ... was addressed in Dimensions CM 10.1 ... ... all customers using Dimensions CM deployment functionality to upgrade to Dimensions CM 10.1 ... A patch for Dimensions CM 10.1.1 is being worked on and will be made available very shortly.
: For Dimensions 12.2.x and earlier, the jre version is 6.0. If you are on a UNIX or LINUX server, use forward slashes and replace the jre directory path with:
Dimensions 14.1 correctly prevents an item from being deleted if it is contained within a baseline created since the upgrade to CM 14.1 or in a baseline that has been upgraded to the new VRS format. We have discovered an issue in CM 14.1 with items that are only contained in baselines that have not yet been upgraded.
Expiring Certificate for Dimensions CM on September 24 2018 - this will result in "PRG7700117E Error: Untrusted endorsing credentials" when logging into Dimensions
