For the response call, it is imperative to include createdByand change invalidTermsto invalidCriteria.
Currently, there is a gap in the system where validation for the 'structuredQuery' objects and their properties is missing. This includes validating each property within the 'structuredQuery' object against predefined criteria to guarantee that only valid and correctly formatted data is accepted
When multiple instances of the same criterion are present, distinguishing between them becomes problematic. To address this issue effectively, there is a proposal to introduce a unique identifier within the 'savedQueries' object schema. This identifier will enable clear differentiation between individual criteria instances, enhancing the clarity and usability of the system.
For the response call, it is imperative to include
createdBy
and changeinvalidTerms
toinvalidCriteria
.Currently, there is a gap in the system where validation for the 'structuredQuery' objects and their properties is missing. This includes validating each property within the 'structuredQuery' object against predefined criteria to guarantee that only valid and correctly formatted data is accepted
When multiple instances of the same criterion are present, distinguishing between them becomes problematic. To address this issue effectively, there is a proposal to introduce a unique identifier within the 'savedQueries' object schema. This identifier will enable clear differentiation between individual criteria instances, enhancing the clarity and usability of the system.