Re: best method to hide attributes in a cmdb class
Hi Lyle, when you install CMDB you get the AST forms as your user interface. As you observed, they are missing some tabs, specifically around financials. If you installed AM then you would get this extra functionality. Sam -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Saturday, 24 January 2009 8:15 a.m. To: ARSList Subject: Re: best method to hide attributes in a cmdb class We're not licensed for AM right now either, so I just did a test. I was able to create a new computer system and edit it using the AST:Computer System form. Several of the tabs were missing that you would normally see, but perhaps that's because that's what you need the license form. You may actually be able to use the AST forms to do what you need. Take a look and give it a try. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of patchsk Sent: Friday, January 23, 2009 11:41 AM To: arslist@ARSLIST.ORG Subject: Re: best method to hide attributes in a cmdb class This is the solution I am looking for. Yes the second option will be more appropriate in my scenario, because we don't have AM license. I will see if I can hide it on the base form itself or these changes are related to only a particular subclass, then I will try to create another interface and link it to the CMDB form via some push fields or DSO. Thanks. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
Hi Lyle, Thanks for the answer. It make sense. But what if the company is using only Change Management and CMDB. -- I guess even with just ChangeManagement and CMDB some basic Asset forms will be installed and all the Asset Classes will be available and we can use those to work with CI. What happens the next time we use CMDB2Asset utility, will it remove all the changes that were done so far to the Asset Classes. (Ex:AST:Computer System) ? Thanks On Jan 22, 12:57 pm, Lyle Taylor tayl...@ldschurch.org wrote: Actually, Sri has it right. The CMDB console is not really an appropriate place to be working with CIs in general except for under special circumstances. In general, you should have users creating and updating CIs using the Asset Management forms - it's a much better front end and can be customized. You should not be customizing the CMDB forms as they are system generated. You can, however, customize the Asset Management forms as much as you'd like with the caveat that once you do that, patches become more difficult to apply. I think a good rule of thumb is that users use the Asset Management forms, and you only work directly with the CMDB forms when creating/updating CIs via integrations or when you can't do what you need with the Asset Management forms. For example, running certain queries on the CMDB can be easier from the CMDB console, but most end users should not need to do that. That would be more limited to administrators and maybe your configuration manager. Lyle Taylor From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of SriVamsi Patchipulusu Sent: Wednesday, January 21, 2009 6:50 PM To: arsl...@arslist.org Subject: Re: best method to hide attributes in a cmdb class ** Hi Srinivas, Thanks for replying. The end users I meant are CMDB users that would be working on CMDB CIs. i.e., creating/updating CIs via cmdb console. Not the asset users. Thanks, Vamsi On Wed, Jan 21, 2009 at 5:36 PM, srinivas madhurakavi kavi1...@gmail.commailto:kavi1...@gmail.com wrote: ** Sri, If I understand your requirement correctly, these are endusers who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts as a regular form you could either 1) Hide the attributes on AST:ComputerSystem form from admin tool or 2) Accomplish it via workflow As far as I could tell, the best choice of the above two options depends on the number of attributes you want to hide combined with their inheritance property (if any). My 2 cents, -SrinivasOn Wed, Jan 21, 2009 at 6:41 PM, SriVamsi Patchipulusu vamsi.pshttp://vamsi.ps@gmail.comhttp://gmail.com wrote: ** All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option is disabled. Now what are the options available to hide those fields that are inherited from BMC_System onto BMC_ComputerSystem class ? 1. Directly hide it from admin tool. -- But I dont think this is an option because it wont update the meta data, changes will be deleted next the class is modifed from class manager. 2. Write an activelink to hide those fields on form open. 3.Create a new page hiddent page tab in that class and move the fields to that new tab? -- Can we do it because there is no option to create a page Tab from cmdb class manager? Thanks in advance. __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
You don't have to be doing Asset Management per se to use the Asset Management forms for working with the CMDB, although you probably do still need to be licensed for the application. You can simply ignore all the financial aspects of the application if you don't need them. At my last company, we weren't using AM for Asset Management (we had SAP and Maximo for that), but we used AM for the most part for working with CIs. In particular we had system managers do all their system updates, etc., in AM. That way we can use the OOB functionality for limiting who has access to change which CIs based on support group associations, and the system managers had a more user-friendly interface to work in. We would use the CMDB forms when administrators or the configuration manager needed to dig into some details about the data, but we rarely changed data in those forms. For example, if we needed to find all CIs with a certain name, regardless of class, BMC_BaseElement is the easiest place to do that. Or if you want to look at the CIs in various datasets, it's easier to do from the CMDB forms (because you can see them all at the same time). If I recall correctly, running CMDB2Asset doesn't undo previous customizations but will create new hidden tabs on the forms that contain your new fields that need to be exposed. You can then move those fields where you want to expose them. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of patchsk Sent: Friday, January 23, 2009 9:51 AM To: arslist@ARSLIST.ORG Subject: Re: best method to hide attributes in a cmdb class Hi Lyle, Thanks for the answer. It make sense. But what if the company is using only Change Management and CMDB. -- I guess even with just ChangeManagement and CMDB some basic Asset forms will be installed and all the Asset Classes will be available and we can use those to work with CI. What happens the next time we use CMDB2Asset utility, will it remove all the changes that were done so far to the Asset Classes. (Ex:AST:Computer System) ? Thanks On Jan 22, 12:57 pm, Lyle Taylor tayl...@ldschurch.org wrote: Actually, Sri has it right. The CMDB console is not really an appropriate place to be working with CIs in general except for under special circumstances. In general, you should have users creating and updating CIs using the Asset Management forms - it's a much better front end and can be customized. You should not be customizing the CMDB forms as they are system generated. You can, however, customize the Asset Management forms as much as you'd like with the caveat that once you do that, patches become more difficult to apply. I think a good rule of thumb is that users use the Asset Management forms, and you only work directly with the CMDB forms when creating/updating CIs via integrations or when you can't do what you need with the Asset Management forms. For example, running certain queries on the CMDB can be easier from the CMDB console, but most end users should not need to do that. That would be more limited to administrators and maybe your configuration manager. Lyle Taylor From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of SriVamsi Patchipulusu Sent: Wednesday, January 21, 2009 6:50 PM To: arsl...@arslist.org Subject: Re: best method to hide attributes in a cmdb class ** Hi Srinivas, Thanks for replying. The end users I meant are CMDB users that would be working on CMDB CIs. i.e., creating/updating CIs via cmdb console. Not the asset users. Thanks, Vamsi On Wed, Jan 21, 2009 at 5:36 PM, srinivas madhurakavi kavi1...@gmail.commailto:kavi1...@gmail.com wrote: ** Sri, If I understand your requirement correctly, these are endusers who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts as a regular form you could either 1) Hide the attributes on AST:ComputerSystem form from admin tool or 2) Accomplish it via workflow As far as I could tell, the best choice of the above two options depends on the number of attributes you want to hide combined with their inheritance property (if any). My 2 cents, -SrinivasOn Wed, Jan 21, 2009 at 6:41 PM, SriVamsi Patchipulusu vamsi.pshttp://vamsi.ps@gmail.comhttp://gmail.com wrote: ** All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option
Re: best method to hide attributes in a cmdb class
If you're not licensed for AM, and you don't want to go that route, you can hide attributes using the class manager like you said. But you would need to hide them from the class they first appear. So, if one of the attributes you want to hide is from BaseElement, you would need to hide it there. If you want it hidden from all subclasses, this shouldn't be a problem. But if you want it hidden from, say, only BMC_ComputerSystem, then you're kind of in a pickle. Another option you might have would be to create custom forms that join back to the CMDB forms, similar to how the Asset forms work. You could then customize those without messing around with the CMDB classes. Lyle -Original Message- From: Lyle Taylor Sent: Friday, January 23, 2009 10:58 AM To: arslist@ARSLIST.ORG Subject: RE: best method to hide attributes in a cmdb class You don't have to be doing Asset Management per se to use the Asset Management forms for working with the CMDB, although you probably do still need to be licensed for the application. You can simply ignore all the financial aspects of the application if you don't need them. At my last company, we weren't using AM for Asset Management (we had SAP and Maximo for that), but we used AM for the most part for working with CIs. In particular we had system managers do all their system updates, etc., in AM. That way we can use the OOB functionality for limiting who has access to change which CIs based on support group associations, and the system managers had a more user-friendly interface to work in. We would use the CMDB forms when administrators or the configuration manager needed to dig into some details about the data, but we rarely changed data in those forms. For example, if we needed to find all CIs with a certain name, regardless of class, BMC_BaseElement is the easiest place to do that. Or if you want to look at the CIs in various datasets, it's easier to do from the CMDB forms (because you can see them all at the same time). If I recall correctly, running CMDB2Asset doesn't undo previous customizations but will create new hidden tabs on the forms that contain your new fields that need to be exposed. You can then move those fields where you want to expose them. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of patchsk Sent: Friday, January 23, 2009 9:51 AM To: arslist@ARSLIST.ORG Subject: Re: best method to hide attributes in a cmdb class Hi Lyle, Thanks for the answer. It make sense. But what if the company is using only Change Management and CMDB. -- I guess even with just ChangeManagement and CMDB some basic Asset forms will be installed and all the Asset Classes will be available and we can use those to work with CI. What happens the next time we use CMDB2Asset utility, will it remove all the changes that were done so far to the Asset Classes. (Ex:AST:Computer System) ? Thanks On Jan 22, 12:57 pm, Lyle Taylor tayl...@ldschurch.org wrote: Actually, Sri has it right. The CMDB console is not really an appropriate place to be working with CIs in general except for under special circumstances. In general, you should have users creating and updating CIs using the Asset Management forms - it's a much better front end and can be customized. You should not be customizing the CMDB forms as they are system generated. You can, however, customize the Asset Management forms as much as you'd like with the caveat that once you do that, patches become more difficult to apply. I think a good rule of thumb is that users use the Asset Management forms, and you only work directly with the CMDB forms when creating/updating CIs via integrations or when you can't do what you need with the Asset Management forms. For example, running certain queries on the CMDB can be easier from the CMDB console, but most end users should not need to do that. That would be more limited to administrators and maybe your configuration manager. Lyle Taylor From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of SriVamsi Patchipulusu Sent: Wednesday, January 21, 2009 6:50 PM To: arsl...@arslist.org Subject: Re: best method to hide attributes in a cmdb class ** Hi Srinivas, Thanks for replying. The end users I meant are CMDB users that would be working on CMDB CIs. i.e., creating/updating CIs via cmdb console. Not the asset users. Thanks, Vamsi On Wed, Jan 21, 2009 at 5:36 PM, srinivas madhurakavi kavi1...@gmail.commailto:kavi1...@gmail.com wrote: ** Sri, If I understand your requirement correctly, these are endusers who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts
Re: best method to hide attributes in a cmdb class
This is the solution I am looking for. Yes the second option will be more appropriate in my scenario, because we don't have AM license. I will see if I can hide it on the base form itself or these changes are related to only a particular subclass, then I will try to create another interface and link it to the CMDB form via some push fields or DSO. Thanks. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
We're not licensed for AM right now either, so I just did a test. I was able to create a new computer system and edit it using the AST:Computer System form. Several of the tabs were missing that you would normally see, but perhaps that's because that's what you need the license form. You may actually be able to use the AST forms to do what you need. Take a look and give it a try. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of patchsk Sent: Friday, January 23, 2009 11:41 AM To: arslist@ARSLIST.ORG Subject: Re: best method to hide attributes in a cmdb class This is the solution I am looking for. Yes the second option will be more appropriate in my scenario, because we don't have AM license. I will see if I can hide it on the base form itself or these changes are related to only a particular subclass, then I will try to create another interface and link it to the CMDB form via some push fields or DSO. Thanks. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
Actually, Sri has it right. The CMDB console is not really an appropriate place to be working with CIs in general except for under special circumstances. In general, you should have users creating and updating CIs using the Asset Management forms - it's a much better front end and can be customized. You should not be customizing the CMDB forms as they are system generated. You can, however, customize the Asset Management forms as much as you'd like with the caveat that once you do that, patches become more difficult to apply. I think a good rule of thumb is that users use the Asset Management forms, and you only work directly with the CMDB forms when creating/updating CIs via integrations or when you can't do what you need with the Asset Management forms. For example, running certain queries on the CMDB can be easier from the CMDB console, but most end users should not need to do that. That would be more limited to administrators and maybe your configuration manager. Lyle Taylor From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of SriVamsi Patchipulusu Sent: Wednesday, January 21, 2009 6:50 PM To: arslist@ARSLIST.ORG Subject: Re: best method to hide attributes in a cmdb class ** Hi Srinivas, Thanks for replying. The end users I meant are CMDB users that would be working on CMDB CIs. i.e., creating/updating CIs via cmdb console. Not the asset users. Thanks, Vamsi On Wed, Jan 21, 2009 at 5:36 PM, srinivas madhurakavi kavi1...@gmail.commailto:kavi1...@gmail.com wrote: ** Sri, If I understand your requirement correctly, these are endusers who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts as a regular form you could either 1) Hide the attributes on AST:ComputerSystem form from admin tool or 2) Accomplish it via workflow As far as I could tell, the best choice of the above two options depends on the number of attributes you want to hide combined with their inheritance property (if any). My 2 cents, -Srinivas On Wed, Jan 21, 2009 at 6:41 PM, SriVamsi Patchipulusu vamsi.pshttp://vamsi.ps@gmail.comhttp://gmail.com wrote: ** All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option is disabled. Now what are the options available to hide those fields that are inherited from BMC_System onto BMC_ComputerSystem class ? 1. Directly hide it from admin tool. -- But I dont think this is an option because it wont update the meta data, changes will be deleted next the class is modifed from class manager. 2. Write an activelink to hide those fields on form open. 3.Create a new page hiddent page tab in that class and move the fields to that new tab? -- Can we do it because there is no option to create a page Tab from cmdb class manager? Thanks in advance. __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
best method to hide attributes in a cmdb class
All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option is disabled. Now what are the options available to hide those fields that are inherited from BMC_System onto BMC_ComputerSystem class ? 1. Directly hide it from admin tool. -- But I dont think this is an option because it wont update the meta data, changes will be deleted next the class is modifed from class manager. 2. Write an activelink to hide those fields on form open. 3.Create a new page hiddent page tab in that class and move the fields to that new tab? -- Can we do it because there is no option to create a page Tab from cmdb class manager? Thanks in advance. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
Sri, If I understand your requirement correctly, these are *endusers* who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts as a regular form you could either 1) Hide the attributes on AST:ComputerSystem form from admin tool or 2) Accomplish it via workflow As far as I could tell, the best choice of the above two options depends on the number of attributes you want to hide combined with their inheritance property (if any). My 2 cents, -Srinivas On Wed, Jan 21, 2009 at 6:41 PM, SriVamsi Patchipulusu vamsi...@gmail.comwrote: ** All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option is disabled. Now what are the options available to hide those fields that are inherited from BMC_System onto BMC_ComputerSystem class ? 1. Directly hide it from admin tool. -- But I dont think this is an option because it wont update the meta data, changes will be deleted next the class is modifed from class manager. 2. Write an activelink to hide those fields on form open. 3.Create a new page hiddent page tab in that class and move the fields to that new tab? -- Can we do it because there is no option to create a page Tab from cmdb class manager? Thanks in advance. __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: best method to hide attributes in a cmdb class
Hi Srinivas, Thanks for replying. The end users I meant are CMDB users that would be working on CMDB CIs. i.e., creating/updating CIs via cmdb console. Not the asset users. Thanks, Vamsi On Wed, Jan 21, 2009 at 5:36 PM, srinivas madhurakavi kavi1...@gmail.comwrote: ** Sri, If I understand your requirement correctly, these are *endusers* who do not want to see some attributes on one or more classes. So your starting form would be (to take the same example: Computer System Class) AST: ComputerSystem. Since AST: ComputerSystem form is a self join of BMC_ComputerSystem with BMC_computerSystem which acts as a regular form you could either 1) Hide the attributes on AST:ComputerSystem form from admin tool or 2) Accomplish it via workflow As far as I could tell, the best choice of the above two options depends on the number of attributes you want to hide combined with their inheritance property (if any). My 2 cents, -Srinivas On Wed, Jan 21, 2009 at 6:41 PM, SriVamsi Patchipulusu vamsi...@gmail.com wrote: ** All, I have a requirement from end users that they dont want to see some fields in the cmdb class(Ex:BMC_ComputerSystem). First I thougt of going to CMDB Class Manager, select the class, view attributes and change the property hidden No to Yes. But I can access this property only for the fields that are from BMC_ComputerSystem_ only. Any fields that are inherited from BMC_BaseElement, that option is disabled. Now what are the options available to hide those fields that are inherited from BMC_System onto BMC_ComputerSystem class ? 1. Directly hide it from admin tool. -- But I dont think this is an option because it wont update the meta data, changes will be deleted next the class is modifed from class manager. 2. Write an activelink to hide those fields on form open. 3.Create a new page hiddent page tab in that class and move the fields to that new tab? -- Can we do it because there is no option to create a page Tab from cmdb class manager? Thanks in advance. __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
