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

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Geny Isam Hamud Herrera
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):

Today about 70% of our SQL Processing tasks are not processing data, the reason is because the staging area did not receive records to be processed. Study available here.

We can optimize the processing by allowing senders (like Smart Link) to notify Carol that a batch of data has been completely sent to Carol and Carol can start processing the data.

03 - STORY CONTEXT (WHAT'S THE CURRENT PROBLEM, SITUATION, SCENARIO, PAIN TO BE RESOLVED?

Comportamentos para definir “timeout” para um summary (aberto pelo smart link ou aberto automaticamente):

• Casos de summary abertos automaticamente o timeout deve considerar 30 min sem recebimento de requests. Sugerido um status do Summary nessas condições para AUTO_OPEN ao invés de OPEN.
• Demais summaries (recebidos via API pelo smart link, por exemplo) obedecem o período de 30 min (regra já existente, alterado para 30 min ao invés de 3 horas).

• Quando o summary nao tiver dados enviados terá o status de NO_PIPELINE_EXECUTE por não ter dados.

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

N/A
05 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):

N/A
06 - ALTERNATIVE STEPS:

N/A
07 - FLOWS NOT COVERED:

N/A
08 - ASSETS/DIAGRAMS (ADD ANY RELEVANT DOCUMENTATION, DIAGRAM, LINKS):

N/A
09 - ACCEPTANCE CRITERIA (LIST ALL THE ITENS THAT MUST BE DONE IN ORDER TO CONSIDER THIS STORY AS DONE):

• Implement the result of the card
  CAPL-4328: [Smartlink Notification] Optimize execution based on external app notificatio...Done
• As result we must reduce the number of SQL Processing to be executed and this should cover Scheduled Tasks and Orchestrator