Example Archive Workflow

This workflow uses the Archiver and Archiver_Filter components.

To work as intended, the Operational Monitoring Logging toolbar button must be on when the workflow is running. The OM “eye” should be open:

Pertinent parts of the workflow:

• The OM “eye” is turned on when the workflow runs.

• There should be only one inbound folder so that all files can be tied together by a Job ID.

  This allows all files that originate from a single input file in the EDI-in folder to be considered a set. When an Archive portal user searches for one file in the set, Archive will list the entire set for them.

• The first Instream component validates the input file and inserts a unique ID number called a FSUID into its DTL file. The original EDI file and its DTL file go to all three branches of the workflow.

• The top branch uses the Archiver component to archive the EDI and DTL file. An Archive user can locate these files by using the Search pages.

• The middle branch splits the original EDI file and sends the report to the

  ArchiverNoFilter component. This component archives files that are not an EDIDTL pair of files. The report is archived but it cannot be located with a search on Archive’s Search page.

• The bottom branch runs DataSwapper to modify the EDI, and sends that modified EDI for validation. At this point, the DTL file will be given a new FSUID, so it will no longer be tied by FSUID to the files archived via the top branch.

  The modified EDI and DTL files are then sent to the Archiver component and placed in the archive.

  We now have five files in the archive:

  1. The original EDI file

  2. The DTL file from validating the original EDI file

  3. The Docsplitter report

  4. The EDI file modified by DataSwapper

  5. The DTL file from validating this modified EDI file An Archive portal user can search for 1, 2, 4, or 5.

     Since 1-2 and 4-5 have different FSUIDs, and 3 has no FSUID, what ties them together so that all five are listed in Archive’s Search results? That is handled by the “Job ID.” The workflow assigns a unique job ID to the original input file. It links each file created by the workflow to that same ID and passes along this information to Archive.

     In Archive, searching for the root filename, with no extension, returns all five files:

     

     If you click on a file, you can see the Fileset ID and the Description of the component that archived it: