Custom Objects allow Vault administrators to use an extensible system to create new Vault entities to meet the needs of their
team, organization, or company. Right out-of-the-box, the administrator can create a Custom Object definition and assign it
categories, lifecycles, and properties. Once the Custom Object definition is created, users can create instances of that custom
object directly through the user interface. As with files and folders, users can perform many common Vault tasks with custom
objects.
Release Availability
The custom objects feature is available in certain editions of Vault. Refer to the following table to see if your edition
supports this feature.
|
|
2011 |
2012 |
2013 |
| Autodesk Vault Basic |
|
|
|
| Autodesk Vault Workgroup |
|
|
|
| Autodesk Vault Collaboration |
|
|
|
| Autodesk Vault Professional |
|
|
X
|
Learn About Custom ObjectsCustom Object Definition
- The Custom Object definition is the type of entity that is being created. For example, an administrator can create a custom
object definition called Contacts or Tasks.
Custom Object Definitions are created, edited, and deleted on the Configure Custom Objects Dialog. You can access the Configure
Custom Objects Dialog through the Custom Objects Tab on the Vault Settings dialog. You must be an administrator to create
and modify custom object definitions.
Custom Object Instance
- When the user creates a new custom object based on a definition, this is considered an instance. For example, an administrator
creates a custom object definition called Contact. A user could then create an instance of that custom object called Bob Smith.
- Users can attach files, folders, and other Vault entities to a custom object with a link.
For example, if a custom object definition has been created called Tasks and a user has created a task called Review John's
Design, the task (Review John's Design) can be linked to John's design in the vault.
- Custom Object instances can be checked in, checked out, undergo a change state, and managed with many common Vault commands.
Similarly, linked objects are also affected, depending on the user's settings for the Vault function.
For example, if a user wants to check out a custom object and the custom object has links to files, folders, items, or change
orders; the files associated with that linked data are gathered and checked out as well.
Manage Custom Object Definition Security
Security can be configured for a custom object definition. This security will be the system Access Control List (ACL) and
will apply to all instances of the custom object definition.
Perform a Security Override on a Custom Object Instance
Editing the security of the custom object changes the security of each instance created in the Vault. For example, editing
the security for a custom object definition called Contacts would change the security for each instance of a Contact (e.g.,
Bob Smith, Marla Green, Bakersfield Motors, etc.)
Additional security can be configured for each instance with a security override. The system Access Control List (ACL) configured
for the definition can only be modified in the administration dialog. Security overrides can be applied to each instance from
the properties dialog.
For more on security and security overrides, see Security Overrides.
Perform a security override on a custom object instance
- Right-click on a custom object instance in the Vault and select Properties.
- Select the Security tab to view and modify security for the instance.
- Notice the Security Mode field indicates that there is either role-based security or object-based security for the instance.
NoteLike files, the system ACL cannot be modified for an instance. The system ACL has to be set on the entire definition in the
administration dialog.
- Select the Security Override check box.
- Now that you are viewing the overriden security of the instance, add users to the access control list.
- Click OK.
A security override is applied to the custom object instance. This means that the system security is no longer the effective
security. The overriden security will be effective until it is removed. At that time, the system ACL will be the effective
security.