This module uses the pattern_import_export and attachment_synchronize modules to automate imports and exports. Different functionalities that are not self-explanatory are used, so you can check the depending modules for more context about this module's usage and configuration.
Table of contents
Here is the full workflow for imports and exports in this module. In italics are the modules relevant to that particular functionality.
- Create a filter and a pattern.config for the model to export (pattern_import_export)
- Create an attachment.synchronize.task of type "export" and configure it (attachment_synchronize)
- Create and configure a pattern.export.task using elements of steps 1. and 2.
- Call pattern.export.task.run_pattern_export_scheduler()
- Observe the following:
- A pattern.file is created from the filter and pattern configuration from step 1.
- The result of that export is in the storage that you configured in step 2.
This is to be used with a cron to call run_pattern_export_scheduler() for automation.
- Create a pattern.config (pattern_import_export)
- Create an attachment.synchronize.task of type "Import using pattern" and configure it (attachment_synchronize)
- Call pattern.synchronize.task.run_import_scheduler()
- Observe the following:
- Files that match the configuration of attachment_synchronize_task are run through the import procedure
- For every file, once imported, the patterned import is executed
This is to be used with a cron to call run_import_scheduler() for automation.
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Akretion
Akretion :
- Kevin Khao <[email protected]>
- Sebastien Beau <[email protected]>
Current maintainers:
This module is part of the shopinvader/pattern-import-export project on GitHub.
You are welcome to contribute.