PRDE - Story default text according to the team DoR (Definition of Ready)

01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

• Provide an endpoint that allow FE to query tasks using SQL instead of ES.

04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:

• Filter hide internal tasks: true/false
• Open filter by taskID and user (it uses LIKE operator)
• Tenand ID should be provided within the query to be perfomed by (/admin/query/sqlfilter).

Additional filters:

• Endpoint on FE side allowing to filter Tasks (/admin/query/sqlfilter).
• TaskID: it receives a list of taskID separated by comma.
• taskType: it receives a list of task types.
• taskStatus: it receives a list of status of tasks.
• LogType: it receives a list of task log entry type.
• Date Created / Date Updated: it receives a start/end date.
• Hide bypassed tasks: it has two behaviors, for both we expect to send true/false.
  • Carol App bypassed tasks
  • SQL Processing bypassed tasks
• Scheduled: true/false
• AI Process Name: it receives the carol app process name, it filters it using the LIKE operator.
• Data Model: it receives one or more data model and allow to filter tasks related to this data model. It work for all tasks related to data models.
• Pipeline Name: it allow to filter SQL Processing tasks by pipeline name, using the operator LIKE.
• Processed Records: it allow to filter tasks using an integer value to filter SQL Processing tasks with processed records. It allow equals, not equals, is less than or equals, is greater than or equals, is empty, is not empty.