EPIC Goal

Allow customers to show incidents without the Backstage Entity ID column. Instead, any column should be usable.

Background/Feature Origin

The new ServiceNow plugin 1.0 requires customers to configure their ServiceNow incident table by adding a new Backstage entity ID column and assign a catalog entity value to show these incidents in RHDH/Backstage.

This is a good, secure way to ensure that we don't expose any data. On the other side this requires our customers to change their ServiceNow configuration and each incident they want to see in RHDH.

We should add an additional, optional, opt-in approach that customers can show ServiceNow incidents without any ServiceNow change.

Why is this important?

User Scenarios

1. Allow customers to show incidents without the Backstage Entity ID column.
   • Any column should be usable.
   • Check the solution with the Security team
   • The current solution with the Backstage Entity ID should work as well
2. Allow customers to configure multiple ServiceNow endpoints
   • Might be the same instance with another API Key or other configurations
3. Move the ServiceNow scaffolder actions into the servicenow workspace
   • Test if both works together

Dependencies (internal and external)

Some changes to the frontend

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>