New in AM2006: Customization

Document retention

AutoManager 2006 now offers the possibility to purge a document from the vault.

When a document is purged, the following happens:

1. The document is no longer visible in any client, including customized clients.
2. All references to and from the document are removed.
3. All the properties of the document and all its versions are deleted from the database.
4. All stream data of the document are deleted from the file system. This includes:
1. Document content
2. Redlines
3. Workflow log
4. Data for Content Indexing

The AMDocument object implements a new interface IAMRetentionControl, which has the following additional properties:

• ExpirationDate property -the date and time the document will expire.
• RemoveLocalCopy property -when the value of this property is True, the document is not cached locally.
• RestrictedAccessDate property - the date after which certain operations, like copy outside vault, are no longer allowed. In AMM-2006 this property is not used yet; it will be used by retention management functionality in future versions.
• RetentionModified property - the date and time at which the value of any of the previous properties was changed.
• RetentionModifiedBy property - the name of the user that last changed the value of any of the previous properties.

A new interface IAMDocumentRepository13 with a new method Purge is implemented by AMDocumentRepository. Purge has a single parameter ID, which is a string representing an object ID, similar to GetFSObject. Purge will delete all content and data as described above.

In the AutoManager 2006 release this functionality is available for programmatic access only. Also be aware that the client part of the software does not remove local copies of purged documents, so copies of the document can be left in the local workspaces after being purged.

AMCreateObject

The new 'AMCreateObject' function can be used to invoke custom ActiveX controls from scripting (events). Compared to the standard 'CreateObject' function, 'AMCreateObject' allows the invoked code to work within the current AMM-Meridian server transaction.

Bug 22165: "Create CommandSet Object from script", RefNum Fv060113115327
 

Other changes

• For the use in configuration of the external pages the following new VBScript methods were implemented: Vault.RootURL, Vault.ServerName, Vault.WebAccessLocationID. 21942 Two additional VBScript functions for External AutoPage
   
• The transaction in which the VaultEvent_Open() event was fired was opened read-only, so any changes to made configuration or variables would not be stored. This is now fixed.Bug 21873: "Cannot set User.Initials in Vault_Open() event", RefNum AB051124212632 
   
• A new function (CallRemote) has been added to scripting in preparation for future functionality. The use of this function is not supported in AMM-2006.
   
• It is now possible to use the AMCompare ActiveX control on an HTML page. To achieve this use an object definition in your HTML page similar to this:

<OBJECT ID="AMCompareControlEx" WIDTH=700 HEIGHT=500

CLASSID="clsid:F8A86685-98C9-11D2-AE8E-008048EC3E75">

<PARAM NAME="LeftDocPath" VALUE="C:\TEMP\A.DWG">

<PARAM NAME="RightDocPath" VALUE="C:\TEMP\B.DWG">

</OBJECT>20925 using amcompare on html page
 

• Several system properties which were previously always read-only are now made writable. These properties are:
  AMFSObjectPropertySet._IMPORTEDFROM
  AMDocumentWorkflowPropertySet._COMMENT
  AMFSObjectPropertySet,_FILETYPE
  AMFSObjectPropertySet,_ARCHIVE Bug 20394: "._IMPORTEDFROM property is read-only, why?", RefNum VL050429115154
   
• If the visibility of the last wizard page was determined by a condition, for example the value of a lookup list, the Finish button would not always be available on the last visible wizard page. This is now fixed.Bug 22400: "Lookuplist value prevents wizard to complete", RefNum SB060221142210
   
• An new event has been introduced in both scripting and AMM-UIExtensions on the 'Replace document content' command.
  Bug 19253: "Missing events in scripting", RefNum MB041111102045
   
• When renaming a document from Application Integration the rename event was not fired.
  This has been resolved in AM-2006.
  Bug 22665: "Script is ignored in Application Integration", RefNum PM060413085212 
   
• Using the "Copy with References" command to create a copy of a document in the same folder would fail in some situations with the error "A document with this name already exists". This problem has been resolved.
  Bug 18094: "Copy with references to the same folder may fail with error: A document or folder with this name already exists", RefNum DQ040414105503