Skip to main content

Files: how arrival and transfer work today

What this page is

Unlike the other pages in this section, this one is not a concept mapping. It describes the file-handling job types available in OpCon Continuum as they work today, so you can see what you have to build with. It does not compare them to anything, and it is not a statement about coverage either way — check what you rely on against what is here, and raise anything missing with your Continuous contact.

What this solves

Most nightly automation at a financial institution turns on a file: an ACH return, a core export, a statement extract. The work cannot start until the file is there and finished, and a file that is still being written is the classic way a night goes wrong — the job reads a half-complete file and posts something wrong. OpCon Continuum has several job types for this. The built-in one that waits, Wait for File, has a default that will stop you before you start: it only watches a short list of allowed directories.

What you get. Which job types handle files, how Wait for File and SMAFT File Transfer work, the allowed-path rule, and how to wait for a file in a way that cannot read it half-written.