After taking ownership, use Release ownership to release the data
so other people can use it 
.
In TM1® Application Web , you must submit all nodes at the level at which you take ownership and you can only release ownership at the level you have taken ownership. For example, if you have taken ownership of a parent node, then decided that you wanted to submit a child node individually, you would first have to Release your ownership of the parent node, then take ownership of the child node in order to submit only the child node. You could then Release ownership of the child node and re-take ownership of the parent node.
If you attempt to take ownership of a node that is currently owned by another user, the system can provide a warning message and offer the opportunity to cancel out of taking ownership. Your administrator can configure the pmpsvc_config.xml to control whether a user who is about to "bounce" ownership of a node receives a warning message and the chance to cancel out.
An administrator can see who has ownership and determine which owner should be released. This "bouncing" behavior can also be controlled per application.
The modeler or administrator of your system can tell you how your system or applications is designed to handle bouncing and releasing.
The Ownership Change Behavior property set in IBM Cognos TM1 Performance Modeler determines the way the system responds when this specific application is released. Depending on that setting, you may see the following behaviors:
- Never warn
- Users may take ownership from one another freely, and no warnings are raised.
- Warn on active user
- Display a warning if the current owner has the node open in a client, but permit the change of ownership ("bouncing") to proceed if the warning is ignored.
- Prevent bouncing of active user
- Display a warning if the current owner has the node open in a client, and block the change of ownership--do not let the "bounce'" occur.
- Always warn
- Display a warning if the node for which the user is attempting to take ownership is already owned by another user, regardless of whether the current owner is in the system or not. Permit the change of ownership to take place if the user continues.
- Always prevent ownership change
- Display a warning if the node for which the user is attempting to take ownership is already owned by another user, regardless of whether the current owner is in the system or not. Never let the change of ownership proceed. In this situation, the current owner must Release their ownership before another user may attempt to take ownership.
These settings are available regardless of the client used. When users have ownership, an administrator can click the Release Ownership icon on the workflow page to display a dialog box that lists the current owners of nodes. The administrator can then choose which user to release.