Branch
Root folders of a Field Path Relation could not be deleted, because once
deleted they could not be re-created again. This is now fixed. As a side-effect
of this fix, Branch Root folders are no longer automatically created after
applying the FPR definition.17338 Cannot
undelete branch root
In the
Field Path Relation property values were treated as case-sensitive resulting
in an error message that 'the folder contains locked documents.' This
is now fixed.17326 FPR: 'folder contains
locked documents' message when type existed FPR property in lower case
In the
Application Integration it is now possible to use a custom property instead
of the display name in the tree view. Refer to the AutoManager Configuration
Guide for more information.000657 Alternative
Document Label in AI
It was
not possible to unmap branch levels in a Field Path Relation. This is
now fixed.12319 How to Unmap branch
levels
It was
not possible to create documents in the root of a vault with a Field Path
Relation. When all properties were left empty the documents would be created
in the current folder. This is now fixed.13791
Cannot create a document in the root of the vault with FPR
When
creating two documents in a vault with a Field Path Relation, but without
calculated filenames, creating the second document would result in an
error message saying the document already exists. This is now fixed.15943 Create new document twice in FPR results
in "document already exists"
The
Document Type settings for when to increase a document's revision number
have been improved, so it is now possible to have a revision number increase
when the initial revision of a document is released from a workarea, like
it worked in AM-Meridian 2.14.16395
Document Revision number for new document incorrect after release from
Workarea
The
calculated filename expression in a vault could be lost after importing
an Environment Template (.MET) and then editing and saving the expression.
This is now fixed.17761 "Calculate
filename" expression is lost in vaults created from Mechanical.met
When
importing an Environment Template (.MET) the Roles and Privileges table
from the MET file would be merged with the existing Roles and Privileges.
This is now fixed: the imported table from the MET file will overwrite
the existing table.18256 Roles and
Privileges tables are merged, instead of overwritten, when importing MET
in existing DB
When
importing an Environment Template (.MET) with an Event Script into a vault
that already had an Event Script, the script in the vault would not be
overwritten. Now a message is shown asking whether to overwrite the script
or not.18257 VBScript code is not updated
when importing MET in existing vault (with VB script code)
To be
able to derive to another folder it was necessary to have the Delete privilege
on the original document. This is now fixed.18312
Need Delete privilege when deriving to another folder
Under
certain circumstances it was not possible to delete an Autopage from an
Environment because the page appeared to be used by non-existing document
types. This is now fixed.18594 Unable
to remove autopages from vault