1.3 KiB
1.3 KiB
API Boundaries
- Authentication is already implemented and is outside the current API-development scope.
- Provide screen-oriented endpoints for Progress Report, Final Report, Notice, Q&A Question/Answer, menu exposure, and Popup management.
- Keep controllers thin and enforce role and Center access again in the service layer.
- Store registration, modification, deletion, answer-view, notice-view, and popup-view timestamps as KST
LocalDateTimevalues according to the existing project convention.
System Event Logs
- Controllers write a system event log after each successful create, update, delete, or upload operation.
- Event codes use the hundreds digit for the major category, tens digit for the minor category, and ones digit for the action.
- Action digits are
1 = insert,2 = update,3 = delete, and4 = upload. - Major categories are
2xx = Report,3xx = Notice,4xx = Q&A,5xx = Popup, and6xx = Menu. - Q&A minor categories are
41x = Questionand42x = Answer. - Log resource identifiers and aggregate counts; do not log HTML bodies or uploaded file contents.
Do Not Assume
Ask before implementing undefined:
- future differences between Admin
1001/2001 - report filters beyond
centerCd - progress-report scoring formulas and external survey SQL
- behavior that is not present in the approved API and screen contracts