1. Proposed title of this feature request?

The UI and the REST API should show the same results.   Currently, this is a customer pain point generating several tickets. 

2. What is the nature and description of the request?

The UI uses GraphQL, whereas the supported ACS API is a REST API.   Given the differences, it is difficult for customers to obtain the same results. shanna_chan has worked closely with the customer (Union Bank) on this issue. 

Related KCS articles:

• Where can I find the API documentation
• Why are RHACS API results different from what is in the UI
• GraphQL query and schema changes

Related customer cases:

• 03435163
• 03439769

Related documents:

• ROX-11438
• RHACS API doc improvements
• MUFG-ACS-2023
• ROX-13587 (Customer use cases of GraphQL API)

3. Why does the customer need this? (List the business requirements here)

From 03435163 the customer (Union Bank) stated: 

We have different stakeholders in the bank , some looking at the reports we generate through REST API and others looking only through UI(like auditors).  Expected behavior is to see the API response and UI data are same. We cannot justify the inconsistencies pointing to technical limitations.  The examples in the solutions directory as i understand is using APIs and we are familiar with APIs. Example solutions (shared) will not address the problem.There needs to be feature request.

4. List any affected packages or components.

• UI - GraphQL
• REST API (currently supported for customers)

NOTE:  Please update this KCS when progress is made on this RFE, as customers will be following the KCS. Alternately, reach out to Aaron Strouse and I will update it.