BMC Helix Intelligent Integrations 23.3

This topic describes and links to PDFs and videos that support this product release.

Here are the answers to some frequently asked questions about BMC Helix Intelligent Integrations and BMC Helix Developer Tools . 

1. Can I integrate a third-party product for which out-of-the-box integration is not available?

   Yes. Use BMC Helix Developer Tools to build custom integrations for third-party products for which the out-of-the-box integrations are not available.

2. What is the difference between an alert and an event in SolarWinds NPM?

   For this information, see the SolarWinds NPM documentation.

3. Why can't I see all the entities in BMC Helix AIOps?

   In  BMC Helix AIOps , you can see only business services. To view entities other than business services, go to the BMC Helix Discovery console. For example, to check the list of imported Configuration Items (CIs), do the following:

   1. In the BMC Helix Discovery console, from the main menu, select  Explore > Data .
      The Infrastructure page lists the number of each type of infrastructure item in the system as well as any infrastructure objects assigned to you. It also displays a list of infrastructure-related reports.

   2. To view a list of CIs, under the Miscellaneous section, click <count> Import Records.
      A list of CIs is displayed. For information about how to search or filter these infrastructure items, see Managing your IT infrastructure.

   3. Click any Dynatrace CI from the list to display the View Object page, which lists the attributes of the object and its relationships with other objects. For information about the attribute mappings, see ImportRecord  and for information about steps to modeling the services, see Start anywhere application modeling.

4. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
5. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
6. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
7. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.