I am trying to set up a BPM to launch the Attachment form from Inspection Processing (Erp.InspProcessing.InspectReceipt), with the necessary parameters to link the document to the receipt.
I believe Attachment is the correct BO to invoke, but I am not sure on which method…and the more research I do, the more I wonder whether a customization to launch the form (Lib.Attachments.AttachmentDetailForm) makes sense.
@fredmeissner - is it paper being scanned then attached - or is it a digital file already (like from email)?
(I’ve not done programmatic doc attachments yet - but I’ve good with working around this issue when it’s paper 
)
Hi @fredmeissner,
You could achieve it by doing UI customisation on the form to leverage a form to upload documents then utilise the adapter method to attach where you require for example we do something similar for Job inspection & Non Conformance.
This would be paper being scanned and then attached.
Ok - Paper - I assume it’s an inspection form - maybe you print that for each inspection… Does the paper already have, or can it be printed with, the VendorID and Pack Slip# data? And better yet - in barcode format (if you have the barcode option in ECM)?
We run all of our RCV paperwork through a MFC (Ricoh Copier/Scanner) in the Ship/Recv/Inspection office. It has a button that puts the scanned pages into a folder monitored by the ECM Client batch input service. Then, using the barcodes and the Content Type associated with that scanner/imported file, a workflow does all the work and attaches it back to the Epicor Receipt transaction.
If you don’t have the barcode module, than you can scan and import into a workflow queue and add the vendor/packslip# data manually and then the workflow can do the rest.
These are material certifications and other documents that we get from the vendor. They should have that information on them, utilizing IDC and the workflows would be pretty slick.
So same for us. Except the paper they send us is confusing at best and we figure there is little hope that IDC will work for our stuff. For now we’re dumping into a workflow queue and manually adding Vendor and Packslip to it so the workflow can finish up.
@fredmeissner Not to not answer your question, but another possible solution. We did not want receiving or receiving inspection scanning documents, so I adapted @MikeGross’s ECM workflow to a following day process. The receiving report is the header. I don’t have the barcode module, but even without I get 90% with no human indexing.
Our HP scanner software has an auto separate on a separator page so they stack them and do one mass scan into hundreds of PDFs then drop them into a folder where ECM reads the header page, names the document and attaches to RcvHed. Later in the day they do cleanup in the ECM workflow.
