CAMPAIGN MANAGER

Approach: This approach is based on the management of FDD Document based on the campaign upload requirement.
FDD CREATION: (Campaign Upload)

When a campaign is uploaded we will create one FDD for each slot with “scheduled_start_time” for each individual record uploaded in the campaign for the present day.

These FDD will be queued for execution according to the slot start time. Additionally, we will add a new variable to the FDDs to denote the slot.

For each subsequent day the capaign is scheduled to run, we will create FDDs for each record in a similar manner at 00 hours. (FDDs will be created for a single day at a time to prevent overwhelming the database or complicating the overall process)

NOTE:

• If no slot is selected at the time of uploading the file then FDD will create without slot and work the same as current flow.

• Time Slot Functionality will be working only for those campaigns uploaded from our system.

• We are provisionally proposing limiting the maximum number of time slots in one day to 2 and the campaign will be scheduled only for at the most 30 days.
  Slot time must be under working time (Flow working time).
  If the csv file contains the schedule time field and campaign created in slot then schedule time will be slot start time that means ignore schedule time fields.

• If the number of records processed within a given slot is below the system's capacity, the slot will be marked as FAILED. Therefore, the number of records in each slot should align with the system’s capacity

All file upload process and scheduler for slot will be processed on KFP.

Upload Negative Number base:

• Negative numbers uploaded will be stored in Mysql corresponding to request_id

• When the negative numbers are uploaded the corresponding entries will be updated in the respective FDDs and will also check if the numbers are already queued in KP awaiting execution.

• When the scheduler runs to create FDD for subsequent days (at 00:00 hours) we will check the negative number repository for corresponding requst_id and will not create FDD.

• Need to maintain negative file upload for reporting.

Flow Execution:

During execution on KP, we will perform all essential checks as currently practiced, including verifying the slot time. If the execution time falls outside the designated slot time, the task will be marked as a failure (out of slot time). We will not reschedule the task, even if reattempts and rescheduling within the next business hours are defined in the flow.

Reports:

There will be no changes required in the approach for EOD and raw reports. Currently, EOD reports are generated based on the FlowExecutionAttemptDetailDocument start time. Raw reports are generated based on start time, phonon_uuid, request_id, and other relevant numbers.

Dashboard Report Count:
On page load data will be the current date.
Uploaded Record : Total record in file.
Attempted Records : Total FDD other then IN PROGRESS status.Attempted Records will be more then total record if multiple slots.
Negative Upload Records : All Negative Records uploaded for campaign.
Pending Records : All FDD count IN PROGRESS status.