Details
-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
None
-
R5 - 11/29: Comp Meta Provider, Release 5 - 12/13 Beg Del Adm:, Rel 5 - 1/10 - 1/24 - DA Cont., Rel 5 - 1/24 - 1/31 - DA Cont.
Description
Tested on version 1.0.1-SNAPSHOT-4804797
Description
When a user selects a Minimum Refresh Delay greater than a Maximum Refresh Delay, an error is caused in the system, but the user is not made aware of this. The metadata provider will not save
Steps
- Log into UI
- Click 'Add New' button and select 'Metadata Provider’
- Entering valid data, move through the application to the Reloading Attributes page
- Enter 'PT24H' for Min Refresh Delay and 'PT0S' for Max Refresh Delay
- Continue to the final page using valid data
- Click the 'Save' button
What is occurring
The save button shows it's loading and does not stop.
What is expected
Recommended: When saving 'Reloading Attributes' page, display a Client-side error to let the user know the min/max fields need to be resolved before continuing.
Screenshot min_max delay
Error Code
Failed to load resource: the server responded with a status of 400 ()
