"<https://api.laddition.com/ShiftDocuments>""<https://api.laddition.com/SalesDocumentLines>""<https://api.laddition.com/dimproduct>"The idea for this first flow is to just record the light data, which imo are sufficient to know if we succedded in finding a service at one date.
If we look at the service model, almost all the data can be read from CA_response.
Then, multiple solutions can be implemented on how to grab the remaining datas:
Launch a background task for each day requesting the data and populating data for specific products
In the service menu, propose another functionality to fetch the sales lines, and get detailed information for the service.
Diagram
graph TD
A((User)) --> B[/ list of dates /]
B --> C{for each dates}
C --> E[[Fetch sowprog + CA response]]
E --> F{Is there a service ?}
F -- Yes --> J{Is it already in DB ?}
F -- No --> C
J -- No --> G[[create a service in DB flag it pending]]
G --> C
C -- Finally --> A
G -.potential implementation.-> I[[Launch background task to fill the product side]]