Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

'Widget definition' dropdown does not contain any options to select

Description

Overview: 'Widget definition' dropdown does not contain any options to select

Steps to reproduce:
1. Log in to evrk2 environment as an admin user
2. Navigate to 'Dashboard' app
3. Select "New widget" from the dashboard actions menu
4. Enter a name for the widget
5. Select "ERM Agreements" from the 'Widget definition' dropdown

Expected result: 'Widget definition' dropdown contains options to select, for example, 'ERM Agreements'

Actual result: 'Widget definition' dropdown does not contain any options (empty).

In DevTools, GET /servint/widgets/definitions/global call fails with 500 status and the following response body:

Additional info:

  • Also reproducible on FSE Dry run 1

  • NOT reproducible on Snapshot

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Attachments

8
  • 27 Feb 2025, 08:47 AM
  • 27 Feb 2025, 08:47 AM
  • 16 Jan 2025, 02:31 PM
  • 11 Dec 2024, 01:41 PM
  • 13 Sep 2024, 03:46 PM
  • 13 Sep 2024, 10:45 AM
  • 13 Sep 2024, 09:43 AM
  • 13 Jun 2024, 11:55 AM

Checklist

hide

Activity

Show:

Craig McNally March 14, 2025 at 4:00 PM

No need to apologize, I’m not going to claim to never have missed a Jira comment before slightly smiling face. LMK if you need anything else from me.

Owen Stephens March 14, 2025 at 9:24 AM
Edited

sorry - I see that now. Apologies. Back to the drawing board

Just for completeness, the response body from https://kong-eureka-bugfest-ramsons.int.aws.folio.org/_/proxy/tenants/fs09000000/modules?provide=dashboard is

[ { "id": "mod-agreements-7.1.5" }, { "id": "mod-licenses-6.1.3" }, { "id": "mod-service-interaction-4.1.2" } ]

Craig McNally March 13, 2025 at 6:52 PM
Edited

/

So perhaps the first thing to check is whether

https://kong-eureka-bugfest-ramsons.int.aws.folio.org/_/proxy/tenants/fs09000000/modules?provide=dashboard

works OK?

It does, see my earlier comments - I provide an example curl request showing it works

Owen Stephens March 13, 2025 at 3:22 PM

have managed to have a quick chat with about this.

mod-service-interaction makes requests to Okapi to find all modules that implement the dashboard interface (^1.0), and then for each of those modules it requests any widget definitions available from the module which is how it retrieves any widget definitions from the implementing modules - if that attempt is failing in some way then we’d get no widget definitions.

Testing on https://eureka-bugfest-ramsons.int.aws.folio.org/ I can see a request like:

GET https://kong-eureka-bugfest-ramsons.int.aws.folio.org/dashboard/definitions HEADER X-Okapi-Module-Id = mod-agreements-7.1.5

does get a valid response. So perhaps the first thing to check is whether

https://kong-eureka-bugfest-ramsons.int.aws.folio.org/_/proxy/tenants/fs09000000/modules?provide=dashboard

works OK?

Craig McNally March 7, 2025 at 7:09 PM

I just tried this on eureka ramsons bugfest and unfortunately it did not help. The API call returned:

{ "status": "OK" }

Details

Assignee

Reporter

Labels

Development Team

Bienenvolk

Release

Sunflower (R1 2025) Bug Fix

RCA Group

TBD

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 13, 2024 at 11:56 AM
Updated last week
TestRail: Cases
TestRail: Runs

Flag notifications