Automate the nightly core export
What this solves
Every business night your core banking system writes an export file, and the day's postings depend on it. If a workflow starts while that file is still being written, or runs on a day the core is closed, it can process a half-complete file or the wrong day's data, and no one notices until the numbers are wrong the next morning.
What you get. A workflow that waits for the export to land and finish writing, processes it only on business days and, if anything fails, recovers automatically and alerts an operator. The nightly run becomes hands-off and safe to trust.
Related topics
- Create a workflow (Builder)
- Define a frequency (Builder)
- Wait for File (Builder)
- Order jobs with dependencies (Builder)
- Run events on outcomes (Builder)
- Manage connections (Administrator)
- Respond to a failed job (Operator)