I would like the user to be able to attach a file with any filename to a receipt, and then have the ECM workflow use DataLinks to retrieve additional fields. The workflow will put the document in the appropriate ECM folder and rename the document based on a standard format. To get the title to show in the E10 tree, it seems I need to attach it to the record again.
The issue is that my original PDF still shows up in the E10 tree. Put another way, the same ECM document shows up twice there. Is there a way to clear the one with the ābadā title out?
Or is there a way to rename the original attachment, so I can skip the additional attach action?
@fredmeissner Couple of ways to approach this, but your understanding is correct. The document title change in the ECM workflow only changes the title in ECM. Weāve been discussing the idea of a better two-way interface with ERP including deleting/archiving/revisioning documents and removing entries in ERP amongst other things. No traction yet, but there are Epicor Ideas for most of them.
You could rearrange the process and have the document come to ECM first then get its title then attached to ERP. You may be able to automate this with a little OCR for the transaction details if thatās possible. For our receiving paperwork, our dock guys scan them into a MFC device that queues them up in ECM workflow queue for them to enter PO /Packslip info at their end of shift. Then my workflow finds the Receipt transaction and attaches the paperwork (after changing the title).
@gpayne is more comfortable with using the Datalinks to create ādata alteringā SQL code. Doing something like this would allow you to manually manage the XfileRef and XFile Attach tables in ERP to remove the previous document. Personally, Iām not a fan of that. Or you could figure out who to simply change the āTitleā in the table in ERP - that might be the best way actually.
You could possibly write a post-process BPM on the Document handling BO that could recognize a āduplicateā attachment and remove the older one. Iād have to think about that one for a minute.
If you figure it out, let us know. Without the 2-way interface, there is a lot to be desired in the current ECM task list when it comes to synchronization.
So we actually do have an existing process where they scan in documents with a ācover sheetā that has barcodes ECM can pick up. This how ECM knows which record in E10 to attach the document to.
We have some documents that are already electronic, so it doesnāt really make sense to print them out and add the cover sheet. I thought attaching them directly would be a simpler process. The BPM idea is interesting, Iāll look into that.
if some are already electronic, then you could drop them in to the ECM āpickupā folder. If they have barcodes or OCR-able data all the better, otherwise they will end up in a workflow queue to have the relevant transaction data entered, then the workflow picks up, changes the title and attaches it to Epicor.
I only updated my fields and now that I have rest from ECM as a possibility I am going to rewrite that one. If I was going to address something like this I would do it from the Epicor side. I have ubaqs based on @jgiese.wciās attachment function that do multiple attachments of the same document from a folder and they could also be made into a fixer of data on the fly.
@utaylor does have a deletion ubaq that is called from rest. Something like that could also be used for this.
Iād use a baq link it to ECM with a REST call to lookup sysrowid of key field.
Then use create attachment with the sysrowid.
Imported file is ocr from idc or directly in ECM with an OCR region.
Key field looks up sysrowid. Workflow uses a search to find duplicates and if no exceptions occur, attachment to the kinetic / Epicor table key field. Example part 123 attachment.