updateActionEnum

• bibus » addOptions » updateAction

• bibus » copyOptions » updateAction

• bibus » moveOptions » updateAction

Specifies that the request should fail if a naming conflict exists.

Specifies that if an object already exists, the existing object and any descendants are deleted before the request is processed.

Adding, copying, or moving objects with this option deletes the original source object and creates a new one when there is a naming conflict, for example, if an object is copied to the same location using the content » copy(objects, targetPath, options) method instead of the content » copyRename(objects, targetPath, newNames, options) method. By default, any ID-based references to the object are cleared. You can set the bibus » addOptions » faultIfObjectReferenced, bibus » copyOptions » faultIfObjectReferenced, bibus » deleteOptions » faultIfObjectReferenced, and bibus » moveOptions » faultIfObjectReferenced to alter the default behavior, depending on the operation.

A bibus » shortcut refers to an object based on a search path, not an ID, and will still function if the target object still exists.

When replacing connections to databases, any database metadata that was previously imported into Framework Manager packages is not impacted. However, the action impacts existing Data Modules that referenced the connection. Any imported schemata is deleted and will not be re-assembled automatically when the new object is created.

Specifies that if an object already exists, the existing ID of the object is maintained and references to the object remain intact.