create an endpoint for CRUDing fixed due date schedules
Description
Based on my understanding of the scenarios listed in UIS-14, these are the CRUD operations to be supported. I'm unclear on where the display logic for date localization (per scenario 6) belongs, but I'm thinking for now that that is a front-end issue.
CREATE Creating a new fixed date schedule entry should be a boiler plate record with the title "Untitled" and two empty blocks for schedules (scenarios 3, 9) Details to be populated through update steps
RETRIEVE
Retrieve all records (no order specified) (scenario 1)
Oh, and please mark this done when it's ready to go so I know I can unblock UICIRC-20.
Cate Boerema October 18, 2017 at 2:29 PM
Comment: You rock! I need to assign you more stories
shale99 October 18, 2017 at 12:52 PM
whats in the branch
create fixed due dates update fixed due dates delete fixed due dates get fixed due date by id get fixed due dates via cql (sorting support supplied) metadata info attached to records and auto populated validation on date, on correct ids, fixed due date names unique validation, name is mandatory current open issue is just the dates - can i expect yyy-MM-dd , and backend will save as timezoned ? will attach updated raml and schemas shortly
comments welcomed...
Cate Boerema October 17, 2017 at 10:34 AM
Got it. Yeah, I think the "metadata functionality" is the most important and would be great to capture for all records going forward. I think we will want the auditing at some point but we can hold off on that for now. Thanks!
Based on my understanding of the scenarios listed in UIS-14, these are the CRUD operations to be supported. I'm unclear on where the display logic for date localization (per scenario 6) belongs, but I'm thinking for now that that is a front-end issue.
CREATE
Creating a new fixed date schedule entry should be a boiler plate record with the title "Untitled" and two empty blocks for schedules (scenarios 3, 9) Details to be populated through update steps
RETRIEVE
Retrieve all records (no order specified) (scenario 1)
Retrieve all records in name order (scenario 2)
Retrieve one record by id (scenarios 2, 3)
UPDATE
title, description, change schedules, (scenario 5)
add schedules (scenario 7-8)
delete schedules (scenario 10-11)
DELETE
Not described in UIS-14, but from a back-end standpoint self-explanatory