odoo/industry#2311
Created by fw-bot
Blocked
- Merge method
- Review
-
CI
- ci/industry: (runtime 67s)
- label
- odoo-dev:saas-19.1-19.0-standardize-pos-config-trcaz-492033-fw
- head
- 4f9f07df07e1ca8d2cc1f7e3c03a976b0a0ffa67
| odoo/industry | |
|---|---|
| 19.0 | #1578 |
| saas-19.1 | #2311 missing statuses missing r+ |
| saas-19.2 | |
| saas-19.3 | |
| master |
[IMP] *: standardize POS config creation
Following task-5364749, we noticed there were some industries like art_craft that are creating their POS configs and journals manually, which is probably error prone and will create unwanted behaviors like duplicate account journals. Instead, we should call a function to load a scenario and modify the existing data.
Furthermore, thanks to this commit odoo/odoo#244246, we can, from the data that is being imported, infer whether or not the module is loaded with demo. Therefore, we can call, from the data, the load_onboarding_scenario functions with the additional parameter with_demo_data as True or False to load the scenario's default demo data in one go.
NB: at the moment, the retail scenario has no demo data that come with the function call, but the parameter still exists. The kiosk scenario however has no demo data parameter.
Forward-Port-Of: #1578