Working on setting up Aras and we are having a serious difference of opinion on what class structure is and classification. And how the two of them work. Can someone please define and give examples besides the geometric shapes ones in the help tool?
For example if I make cordless phones, desktop phones, wall phones and cell phones would each one have its own item type? One person is saying all if it was cordless phones fall under one class while another is saying cordless phones of the M class would all fall under their own class.
Hi Nirie1,
There is no hard and fast answer here. It depends on how much the "things" really have in common. When considering properties, forms, actions, lifecycles, workflows, permissions, etc... if those things are the same or similar they are probably diff classes of the same item type.
In your phone example - they are very likely to be the same item type. There will be some properties that apply to certain classes but by and large they are the same.
Then again if you consider something like Part vs Manufacturer Part - all of the above are going to be different. Different information to track, different permissions, differ states, etc. Even though they are both "parts" they don't naturally go together in one item type.
However you can also consider polyitems which can be used to put Part and Manufacturer Part on one search screen.
in the example posed, using classification is less work, you can set up one itemtype and deal with the differences via class-specific details vs. set up 4 different itemtypes with most of the same settings + a polyitem.
At the end of the day it's all about how you want to set it up; after considering all aspects. Both methods can be considered equally wonderful.
Are there any Configuration Management(CM) solutions in this forum or do you have any case? Part and Manufacturer Part is considered as a instance of Intemtype which called ''item'. That's a new opproach to solve complex problem in CM process.