Skip to:

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

Create settings API for hrId

Description

HRID Sequencers (Instance, Holdings, Item) in Inventory need to be responsive to the new tenant-level settings for Starting number and Prefix.

Steps

  • Create db table for storing hrID settings

  • Add default values

  • Make start number required

  • Add Service for generation new hrID using settings instead of db trigger

  • Only a single endpoint needed

  • Only Get and Put needed

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Matt Reno November 18, 2019 at 3:07 PM

the settings API will allow the user to set the start number to any valid number, 1-99,999,999. The settings API does not check whether or not the value has been used.

Ann-Marie Breaux November 18, 2019 at 2:52 PM

Hi Does the API cover the fact that 1) we won't duplicate numbers and 2) what happens if the user resets the setting in such a way that the numbers could possibly overlap. Does the backend prevent from resetting to a lower number than was previously used? Thank you!

Matt Reno November 18, 2019 at 1:30 PM

The settings API can be tested manually, see: https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/hrid-settings-storage.html

HRID generation cannot be tested manually at this point.

Cate Boerema November 18, 2019 at 12:52 PM

is there any way for this to be manually tested?

Ann-Marie Breaux November 13, 2019 at 2:39 AM

Hi I am open to whatever is quickest, so long as 1) we don't duplicate numbers and 2) the backend returns some sort of useable message for the UI. If we understand what the backend is going to do, we can adjust the UI text or warning messages to make it more clear. Thank you!

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Parent

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 30, 2019 at 8:07 AM
Updated December 2, 2019 at 9:58 AM
Resolved November 29, 2019 at 4:31 PM
TestRail: Cases
TestRail: Runs