Cindy,
In a nutshell:
- the BMC join forms join classes together according to the class hirearchy
and are created by the cmdb application. You should not modify these in the
admin tool as your changes could get overwritten if changes are made to the
classes in the class manager. If you look at these forms you will see that
they are not laid out for user access.
- the AST join forms are effectively views of the BMC forms created as user
interface forms. They are generally not affected by changes to the CMDB. You
can lay these out as you want to in the admin tool, add fields from the
underlying BMC form and add display-only fields as you need for any specific
workflow you create.
HTH
Cheers
Peter
Cindy Sapochetti writes:
Hi Listers -
Happy Holidays!
I have a basic question regarding self join forms (I'm specifically looking
at AST: forms from the Asset 7.0 app). For example - AST:ComputerSystem is
a join of BMC.CORE:BMC_ComputerSystem to another
BMC.CORE:BMC_ComputerSystem.
What's the purpose of this? If I trace this all back from a database
standpoint, AST_ComputerSystem is a view, which is based on two other
views, those are based on four other views, which are based on joins of 5
tables, 2 views...etc...etc...lots of nesting.
I'm not sure I understand the design principle behind this, and it would be
helpful if someone could point me to the documentation that might speak to
this, or give me the "Remedy BackEnd Design for Dummies" synopsis.
Thanks!
Cindy
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
