Etere Ingest is able to trigger T-workflows after the completion of the following ingest operations:
•After an ingest operation (Easy Ingest, Multifunction Ingest, Cart Ingest, Scheduled Ingest)
•After an streaming ingest operation (Easy Ingest, Multifunction Ingest)
Above T-workflows are configured under the "Etere Configuration > Configuration Editor > T-Workflows > Default T-workflows" section, where it's also possible to define the behavior to be taken in case the system founds that a requested T-workflow is already running for a ingested asset:
Operation allowed - The ingest operation will be allowed but the requested T-workflow won't be restarted.
Force workflow reset - The ingest operation will be allowed and the requested T-workflow will be attempted to be reset.
Ask for confirmation - A message will be displayed asking for a confirmation to reset the requested T-workflow.
NB: For automatic modules (Cart Ingest, Scheduled Ingest) the ingest operation won't be allowed and no message will be displayed.
Operation denied - The ingest operation won't be allowed, the requested T-workflow won't be reset and a warning message will be displayed.
NB: It's worth mentioning that all behaviours are recorded in the log file of the ingest operation.
Please Note:
During the Ingest operations, the media file is stored in local storage in the Ingest station before moving to destination folder, the following processes must be in place to optimize the storage space in local ingest station:
•The default T-workflow “After an ingest operation” must be configured to be launched after an ingest, as mentioned in above.
•The Cleanup parameter has been configured in Resource Editor to monitor the used space threshold and perform deletion of file when the threshold is reached.
•The “Operations by Workflow” module must be active to perform the housekeeping tasks.