While writing a custom ETL module, it is up to the developer to periodically update the load_event table. The status column in that table is used to drive frontend display for up-to-date feedback on each task's progress:
It would be helpful to developers to have a documented list of strings that are used to key the different messages that are displayed on the frontend by default.
In Arches 7.6, this information would come from the plugins/etl-manager.htm template. Some statuses trigger buttons on the frontend as well.
| status |
display (i18n string) |
button |
| running |
validating |
stopEtl |
| validated |
running |
- |
| completed |
indexing |
undoImport |
| unindexed |
loadedButUnindexed |
undoImport |
| indexed |
completed |
undoImport |
| failed |
failed |
removeFromHistory |
| reversing |
unloading |
- |
| unloaded |
unloaded |
removeFromHistory |
| cancelled |
cancelled |
removeFromHistory |
While writing a custom ETL module, it is up to the developer to periodically update the
load_eventtable. Thestatuscolumn in that table is used to drive frontend display for up-to-date feedback on each task's progress:It would be helpful to developers to have a documented list of strings that are used to key the different messages that are displayed on the frontend by default.
In Arches 7.6, this information would come from the
plugins/etl-manager.htmtemplate. Some statuses trigger buttons on the frontend as well.