Connect Paige to OnBase

How it works

1. 1

   Paige exports each finished document to an SFTP folder: a PDF, then .json, .xml, and .csv files with the same base name.

2. 2

   A Power Automate flow triggers on the .json, reads the values, copies the PDF to the DIP import share, and appends one record to the day's index file on that share.

3. 3

   OnBase runs the DIP process on a schedule (or an operator runs it from the Client), imports every document in the index file, and sets the keywords.

Step 1 — Point Paige at your SFTP server

1. 1

   In Paige, open Settings (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose Export.

2. 2

   Click the FTP card. Enter the FTP Address, Port 22, Username, Password, and in FTP Folder Path a folder for this scan job, such as /paige/invoices.

3. 3

   Click Test Connection. What you should see: FTP connection successful! Connect — Connected to FTP Server! and a green Connected label.

4. 4

   Turn on Enable Auto Export. Under Auto Export Settings, switch on Only documents having a document type, set Auto Field Entry Complete to Yes, and set Human Reviewed to Reviewed — DIP imports are hard to undo, so let people check in Paige first. Click Save.

Step 2 — Agree the index file layout with your OnBase administrator

Step 3 — Build the flow

1. 1

   Trigger — SFTP - SSH: When a file is added or modified. Connection: Host server address, User name, Password, Port number 22. Folder: the scan job's folder. Include file content on.

2. 2

   Condition: File name ends with .json. Steps 3–6 go in If yes.

3. 3

   Parse JSON on the trigger's File content, schema generated from a real .json.

4. 4

   SFTP - SSH: Get file content using path. Path: the folder plus the parsed pdf_file.

5. 5

   File System: Create file. Folder path: the files subfolder of the import share. File name: a name built from Paige fields, ending in .pdf — @{body('Parse_JSON')?['fields']?['Invoice Number']}.pdf — and File content from step 4. Strip \ / : * ? " < > | from the name with replace() calls; a duplicate name would overwrite, so append the export timestamp if that can happen.

6. 6

   File System: Append file (or Create file if it doesn't exist yet, guarded with a Get file metadata using path and a condition). File path: the share root plus paige-invoices-@{formatDateTime(utcNow(),'yyyy-MM-dd')}.txt. Content: one record in the agreed order, ending with a newline:

   @{body('Parse_JSON')?['metadata']?['document_type']}|\\fileserver\OnBaseImport\Paige\Invoices\files\@{body('Parse_JSON')?['fields']?['Invoice Number']}.pdf|@{body('Parse_JSON')?['fields']?['Vendor Name']}|@{body('Parse_JSON')?['fields']?['Invoice Number']}|@{body('Parse_JSON')?['fields']?['Invoice Date']}|@{replace(body('Parse_JSON')?['fields']?['Total'], ',', '')}
   

   Use the same field names as the Paige document type, in the order the OnBase administrator configured. Keyword types that are dates or currency want values in the format OnBase expects — convert with formatDateTime() and replace() as in the amount example.

7. 7

   Save. What you should see: the flow checker reports no errors.

Step 4 — Run DIP

Step 5 — Test it

1. 1

   Process one document through the scan job in Paige, review it, and wait for the export.

2. 2

   Check the flow's run history: one successful run. On the share: the PDF in files, and the day's index file with one record.

3. 3

   Run the DIP process (or wait for its schedule). What you should see: in the OnBase Client, the document under its document type with the keywords filled. The DIP verification report shows one document imported and no rejections.

When it doesn't work