When an object's vault is changed, by default the following occurs
behind the scenes:
- The original business object is cloned in the new vault with all
business object data except the related set data.
- The original business object is deleted from the "old" vault.
When a business object is deleted, it also gets removed from any
sets to which it belongs. This includes both user-defined sets and sets defined
internally. IconMail messages and the objects they contain are organized as
members of an internal set. So when the object's vault is changed, it is not
only removed from its sets, but it is also removed from all IconMail messages
that include it. In many cases the messages alone, without the objects, are
meaningless. To address this issue, you can add the object clone from the new
vault to all IconMail messages and user sets in which the original object was
included.
This additional functionality could affect the performance of the change
vault operation if the object belongs to many sets and/or IconMails. It is not
part of the function by default. Business Administrators can run the following
MQL
command to enable or disable this functionality for system-wide use:
set system changevault update set | on | off |;
For example, to turn the command on for all users, use:
set system changevault update set on;
After this command has been run, when users change an object's vault
using any application (that is, Web applications or custom Studio Customization
Toolkit applications), all IconMail messages that reference the object are
fixed, as well as user's sets.