While checking OLMIS-6172, I noticed that we can add unnamed periods.
Send PUT api/processingPeriods/id or POST api/processingPeriods with body:
I received the status 201, and the unnamed period is visible on the UI.
Also, Start Date and End Date are different on the UI than those given in the body.
It should not be possible to create processing periods without names;
It should not be possible to update an existing processing period in such a way that its name is null;
The processing period's start date and end date on the back-end should match the dates visible on the UI.
I will take this ticket again and test it on UAT after 3.6Release. Then I will be able to check if it already works.
Now the endpoint is working correctly, I cannot create an unnamed period, or update an existing one in this way.
However, I think that the message that appears should be different. Instead of "Name is null", it can be "The processing period's name is required" or "The processing period's name cannot be null".
I agree with you. In the response, there are two fields with 'name' key so it might be confusing.
I have changed the response message, so ticket can be tested again.
Everything is displayed correctly.