Yes - but they are a little special in that they are designed to be universal. A single workflow can apply to documents that come from Epicor, from IDC (PDF + XML) or from the ECM Client Batch input. The first action block has a check for a sysrowid guid and if so, then I have a datalink that uses that sysrowguid to go back into epicor and find the transaction metadata. If there is no guid, then either OCR/XML or something has to get me the key transaction data and then a datalink uses the go back to Epicor for the metadata.
So, really have two datalinks and a single universal workflow. Ok, technically three as one is for looking into the test database… I keep ALL my datalinks in both the Prod and Dev ECM envirnments.
