Skip to main content
A
Anonymous
September 21, 2015
Solved

Soft -Type VS Attributes | What would be more useful ?

  • September 21, 2015
  • 2 replies
  • 1335 views

Windchillers,

If given an option; what would be more beneficial to configure ?  an attribute or a soft type ?

Let us say there are 4  list available for configuration on WTDocument:

1) ID : {1,3,5,7}

2) MATERIAL : {St, Al, Br, Cu }

3) TYPE_INFO : { Decoration, Lab, commercial, Household}

4) Country : {US, FR, AU, LA}

Would it be more beneficial to configure TYPE_INFO as soft type of WTDocument and then add attributes ID, MATERIAL & Country on each soft Type (Decoration, Lab, Commercial & Houehold) ?

OR

Would it be optimal to add all the 4 as attributes on WTDocuments ?

why ?

Best answer by BhushanNehe

Hi Vaibhav,

This depends on many other factors. Do you want all objects to use same life cycle template ? Are you planning to have workflows for these objects based on TYPE_INFO. Do you want a separate OIR (numbering, folder, versioning scheme)? How do you prefer to search on these objects?

If you are planning to create separate types you may want to create a particular subtype first with all the required attributes and make it un-instantiable and then create other types under this which would be marked instantiable.

Regards,

Bhushan

2 replies

B
BhushanNehe16-PearlAnswer
16-Pearl
September 21, 2015

Hi Vaibhav,

This depends on many other factors. Do you want all objects to use same life cycle template ? Are you planning to have workflows for these objects based on TYPE_INFO. Do you want a separate OIR (numbering, folder, versioning scheme)? How do you prefer to search on these objects?

If you are planning to create separate types you may want to create a particular subtype first with all the required attributes and make it un-instantiable and then create other types under this which would be marked instantiable.

Regards,

Bhushan

A
Anonymous
September 21, 2015

Hi Bhushan,

Thanks for the pointers, Very useful. Yes, We might have workflows in future; and that would be an added advantage.

However from search perspective; would the search for an ATTRIBUTE be more resource intensive than that of a TYPE ?

Regards,

Vaibhav

Terms & ConditionsAccessibility statement