json schema for categories defines type string but folio actually requires UUID

Description

Overview: json schemas for organizations addresses, emails, phone numbers, and urls contact information accept string type for categories but passing a string instead of UUID breaks FOLIO UI functionality for these fields.
Steps to Reproduce:

  1. Log into any FOLIO environment using an API tester or curl command

  2. POST to the /organizations/organizations endpoint some test data, such as:

    1.  

      { "name": "Test", "code": "TEST", "exportToAccounting": false, "status": "Active", "aliases": [], "addresses": [{ "addressLine1": "address line 1", "city": "city", "stateRegion": "CA", "zipCode": "94305", "country": "USA", "isPrimary": true, "categories": [ "Customer Service" ] }], "phoneNumbers": [{ "phoneNumber": "650-123-4567", "categories": [ "Customer Service" ], "type": "Office", "isPrimary": true }], "emails": [{ "value": "claims@vendor.com", "isPrimary": true, "categories": [ "Claims" ] }], "urls": [], "contacts": [], "agreements": [], "erpCode": "testaccountingcode" }
  1. Go to the FOLIO UI and login

  2. Select the organizations app.

  3. Search for "test" organization.

  4. Click on it to and select edit. 

  5. Expand "Contact information" section and review the Categories section for each address, phone number, and email sections.

Expected Results: Expect to see organization categories.
Actual Results: See blank boxes.
Additional Information: Will require a migration script to correct existing values
URL: Looks like the json schemas at https://github.com/folio-org/acq-models/tree/master/mod-orgs/schemas for address, email, url, phone number need to set UUID instead of string for categories, such as at https://github.com/folio-org/acq-models/blob/6c60ecf2e6bbdf71af6a7caabe5ad8b489cbf75b/mod-orgs/schemas/address.json#L38-L45  
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

defines

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges February 3, 2022 at 2:57 PM

This issue is about enforcing the use of UUIDs from the BE and making sure the UI does not fail if incorrect data was added before hand. Expected results need to be updated.

Ann-Marie Breaux January 12, 2022 at 9:43 AM
Edited

Hi I came across this bug reported by Stanford, and not assigned to Thunderjet or the Orgs Epic. Added those and assigned it to you to review and decide next steps.

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Thunderjet

Release

Not Scheduled

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 10, 2022 at 6:15 PM
Updated October 20, 2023 at 11:20 AM
TestRail: Cases
TestRail: Runs

Flag notifications