The question is specific to the API notation shown in the screen under the heading Table Name with the comment Joins Multiple Tables. I am using Spring Boot with JPA (Database: RDBMS)
I have defined API notations for multiple requirements that UI ReactJS based Portal application consumes the APIs. Are these notations follow the best practices of API notation [Refer screenshot], especially when multiple tables data is required to be combined?
We have a process hierarchy with supported levels from 0,1,2,3,4. We follow terminologies across application Level-0
process as PROCESSES
and Level-1 to 4
processes as SUBPROCESSES
.
- Processes [Level-0] -->
PROCESS_DETAILS
(has header info),PROCESS_ATTR_MAPPING
(dynamic attributes of a process) - Subprocesses [Level-1 to 4] -->
NODE_DETAILS
(has header info),NODE_ATTR_MAPPING
(dynamic attributes of a process),NODE_META_DATA
(Other metadata information) - Other tables are calendars or planning information, we can ignore them for the sake of simplicity of my question.