This is an old post, but I tried to explain and answer these questions in my post The Pulse – Understanding tools and guidelines for extending your asset and CMDB data model last month.
Short answer is basically:
- Use CMDB best practices for adding any attributes to CMDB, which means Class Manager and Sync UI
- Use ARSystem best practices for customization to AST:LifecycleAttributes, which means overlays
- Decide between the two options based on whether the attribute belongs in the CMDB or AST:LifecycleAttributes.
I didn't get much feedback on that article, not sure if that means I covered it completely or if folks just got tired of reading it
I think after the initial confusion around the way AST:Attributes works AND the use of overlays, things went quiet as most people got it. Did you mean AST:LifecycleAttributes or AST:Attributes by the way?
I missed that article. Great article!
There is also a webinar tomorrow about this topic:
Thanks Jarl, Thanks Carey, and yes - I did mean AST:Attributes.