Enabling access to BMC Helix ITSM: Smart Reporting
As an administrator, you can enable other users to access the application usage reports in BMC Helix ITSM: Smart Reporting that help understand whether end users are using an application to its full potential.
To access BMC Helix ITSM: Smart Reporting, make sure you assign Fixed, or Floating licenses to the users to access the Smart Reporting Console, and you onboard users to BMC Helix ITSM: Smart Reporting.
To assign Fixed, or Floating licenses, see Creating and modifying users. For more information about the onboarding process, seeOnboarding.
Using custom reports in BMC Helix ITSM: Smart Reporting after upgrading to 21.3 or later
The Foundation data model differs between BMC Helix ITSM and BMC Helix Innovation Studio. After upgrading to BMC Helix Innovation Studio version 21.3 or later, if you use custom reports, you might have field conflicts while importing the custom reports to the upgraded system. To continue using the custom reports after you upgrade BMC Helix Innovation Studio to version 21.3 or later, you must map the Foundation data fields from BMC Helix Innovation Studio to fields in BMC Helix ITSM.
Field mappings in BMC Helix Innovation Studio Foundation data
The following table provides information about Foundation data field mappings between BMC Helix Innovation Studio and BMC Helix ITSM:
BMC Helix Innovation Studio Foundation data fields | BMC Helix Innovation Studio record definition | BMC Helix ITSM Foundation data fields | Description |
|---|---|---|---|
Person | com.bmc.arsys.rx.foundation:Person | CTM:People | Person only attributes |
CTM:People IS Bundle Access | Bundle Access Permission Associated to People. One entry is created per bundle. | ||
CTM:People IS Personas | Functional Roles associated with People. One entry is created per functional role. | ||
User | User login related details | ||
Primary Organization | com.bmc.arsys.rx.foundation:Primary Organization | COM:Company | Company only attributes |
COM:Company Alias | Company Alias details | ||
CTM:SYS-Access Permission Grps | Group association with Company | ||
Support Group | com.bmc.arsys.rx.foundation:Support Group | CTM:Support Group | Support Group only attributes |
CTM:Support Group Alias | Support Group Alias details | ||
CTM:Support Group Domain Tags | Support Group Association with domain tags | ||
CTM:SYS-Access Permission Grps | Group association with Support Group | ||
CTM:Support Group Association | Support Group Person Association | ||
CTM:Support Group Permission DomainTag | Join of Support Group Permission and Support Group Domain Tag | ||
Department | com.bmc.arsys.rx.foundation:Department | CTM:People Organization | Business Unit and Department Details |
Deprecated from Support Group hierarchy. It is not a permission-able entity in BMC Helix Innovation Suite | |||
Business Unit | com.bmc.arsys.rx.foundation:Business Unit | CTM:Support Group -> Support Organization | Business Unit associated with Support Group |
Operational Category | com.bmc.arsys.rx.foundation:Operational Category | CFG:Service Catalog | |
CFG:Service Catalog Assoc | |||
CFG:Service Catalog Domain Tag Assoc | |||
Site | com.bmc.arsys.rx.foundation:Site | SIT:Site | Site only details |
SIT:Site Alias | Site Alias details | ||
SIT:Site Company Association | Site association with Company | ||
Site Area | com.bmc.arsys.rx.foundation:Site Area | Deprecated | |
Region | com.bmc.arsys.rx.foundation:Region | CTM:Region | |
SIT:Site Alias Company LookUp -> Region | Region associated with Site | ||
Resolution Category | com.bmc.arsys.rx.foundation:Resolution Category | Deprecated | |
Root Cause Category | com.bmc.arsys.rx.foundation:Root Cause Category | Deprecated | |
Domain Tags | com.bmc.arsys.rx.foundation:Domain Tag Registry | CFG:Domain Tags | |
Functional Roles | Functional Roles | CFG:IS Personas |
To use custom reports in BMC Helix ITSM: Smart Reporting
To use the custom reports, make sure you resolve the field mapping conflicts while importing the custom reports to the upgraded system. For more information, see Resolving field conflicts in custom reports after upgrading to 21.3 or later.
Related topics