Typically Business Capabilities are hierarchical and do not have any prescribed relationships to one another other than their hierarchical relationship. They have relationships down to the Business Applications and the Business Services.
For EUC applications, you can manage it as a business application. I would look to your enterprise architecture team and determine if it is in their scope. If it is in the EA scope it could/should be in the application portfolio, regardless of whether it has any infrastructure other than the EUC devices. Normally the best CI to use for incidents would be the EUC node itself. The business application can be related to the incident via a separate related list called Impacted Business Applications, but cannot/should not be used as the CI for the incident. You will find similar posts on the community about this with different approaches, so there is no one right or wrong answer. Some people have proposed creating Dynamic CI Groups that would collect information about the EUC devices that have a particular Software Installation on them, and in that case you could technically treat these applications the same as Server based applications, with the idea that the supporting infrastructure is all of the computers that have that application installed on them. Whether that is worth the effort is up to you and your needs. From my perspective the biggest value probably comes from identifying where the incident has occurred, which for EUC is on the device itself. But it really depends on several factors, including the metrics you need to have around software support (including anything that you want to roll up to EA for portfolio rationalization), and how your software support is routed in your organization.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
