Please help me that when we will create an object type with super type as null? where it will be useful in real time environment?
If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.
If you want a custom type that does not need any features of common base types, maybe because you are using this type as a separate data store for shared data. For example, if your data does not need ACLs or content, then you don't need to inherit from dm_sysobject.
a NULL super type object can be used in a similar manner as a registered table. As it is a Documentum object its content can be moved from one repository to another with Documentums API scripts (dump & load) or created and manged with DFC API.
Thank for your reply. If it doesn't contains ACLs and content what is its use in documentum? please clear me. when we have to use this object.As i know that it doesn't contain an content in it? I think that its doesn't provides any versions ? please suggest me when to use this object?
My recommendation would be to never use types without supertype, because there is absolutely no security support. In other words, any user would be able update, create, modify or delete these objects. Granted, they need to know DQL to do it. But if your application relies on such objects, it becomes easy for a malicious user to render your application disfonctional. If you don't need the overhead of sysobjects, use registered tables instead.
Not sure if this bug is fixed, but instances for null super type cannot be included in docapp (ie Application Builder). I dont know if this is true for Composer. See my blog entry on this:
http://johnnygee.wordpress.com/2008/04/09/when-good-intention-go-awry/
We can create an object type with super type as null using composer.
It is a persistent object then.
The purpose is just like a look up table which is registered in documentum.But you will not be using it to assign to documents/folders since it will not appear in the list of object types
