When processing batches, the BatchSize
value would vary during the processing of the batch. This is now greatly
improved, with the remark that BatchSize can still
vary if, during the processing of the batch, documents with outgoing references
are encountered.
When binding an Auto property to a VB property,
the displayed Effectivity Type of the VB would not always be correct.
This is now fixed.
Two new possible flags are added for AMUIExtension.ClientDetails.Refresh,
AS_RF_CHANGED_CURRENTFOLDER and AS_RF_CHANGED_CURRENTVIEW,
for refreshing information in the PowerUser.
The methods UserHasPrivilege
and IsPrivilegeGrantedToUser on IAMRoleBasedSecuredObject3
would only return correct information for the current user. This is now
fixed.
When properties have been added or removed in
the past, displaying auto pages for older revisions of documents may not
have displayed the correct information. This is now fixed.
When an Auto page did not get focus during editing,
it may have occurred that a field on that page did not properly retrieve
its value from the server. This is now fixed.
When adding a column to a navigation view, that
column may have been rejected with 'is an invalid name' when the display
name of the property contained any characters that were invalid for internal
names, such as spaces and dots or other non-alphanumeric characters. This
is now fixed.
Vault.CurrentWorkArea.TemplateName
returned the display name of the Work Area Template instead of the internal
name. This is now fixed.
In the Visual Basic Designer, the PowerUser icon
did not work. This is now fixed.
The DocTemplate argument
to DocGenericEvent_BeforeNewDocument would be
different in PowerUser and WebAccess. In WebAccess it would pass the ID
of the Document Template, while in the PowerUser it would correctly pass
the template's display name. This is now fixed so that in both cases the
template's display name is passed.
The automatic “Synchronize Properties to File”
on the various events would typically be occurring before the final AfterSubmitWorkingCopy, AfterChangeState
and AfterChangeWFState events. This has been changed
so that the synchronize operation now always happens after these events
to make sure that any changes in property values made during these events
are also synchronized.