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

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):
03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

The endpoint “processQuery“ currently isn’t asking the caller to send the Carol App Name, and it blocks us to determine where is this pipeline coming from (considering that the pipelineName is unique by Carol App Name).

04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

Add a an optional parameter on “processQuery“ asking the Carol App Name.

05 - WHO CAN USE THIS FEATURE (USER ROLES):

• Tenant Admin, Carol Admin.

06 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
07 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):
08 - ALTERNATIVE STEPS:
09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
10 - ACCEPTANCE CRITERIA:

• When calling the endpoint “processQuery“ I should be able to send the carolAppName, and this information should be available on the task (following the same fieldname we store today when the SQL Processing task is created from a scheduled task).
• When calling the endpoint “processQuery“ I should be able to do not send a value for Carol App Name, and it should still create the SQL Processing task.
  • The side effect is that this task wont be optimized by the SQL Processing efficiency engine (OKR-01).