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.
The custom objects feature is available in certain editions of Vault. Refer to the following table to see if your edition supports this feature.
2012 | 2013 | 2014 | |
---|---|---|---|
Autodesk Vault Basic | |||
Autodesk Vault Workgroup | |||
Autodesk Vault Collaboration | |||
Autodesk Vault Professional |
Custom Object Definition
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
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.
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.
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.
Define Custom Object Definition Security
For more information on Roles in role-based security, see Roles and Permissions.
Edit Custom Object Definition Security
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
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.