We use ECM/DocStar for our storage of attachments.
We have a request to override the current user experience to make it simpler.
Problem I am seeing is that is looks like it’s deep enough in the implementation, such that it’s not possible.
When looking at each of the places where attachments can be added (e.g. Order, Job, Labor Detail) in Application Studio and tracing with web developer tools, the only hints I can find are in the network tab.
There is nothing in the Application Map or Layout, no console trace that identifies the slideout or what events/methods are being called.
It appears to come down to Ice.BO.AttachmentSvs, method DocStarUploadFile followed by Erp.BO.SalesOrderSvc, method GetNewOrderHedAttach.
DocStarUploadFile requires as one of the parameters, the contents of the file being attached.
I think that’s related to the reason for it being buried, security issue, I can’t locally read the contents of a file and pass it to the web side…
Jose Gomez posted code to do attachments via REST and his example specifically uses the DocStar endpoint - though the entire process is the same with the regular UploadFile function as well.
This is not classic (I wish)…the issue I think I’ll have with that approach is that the user will need to pick the file locally, then it can be uploaded to server using file transfer widget, but then they would need to pick it again to get it to DocStar
Yes, this does seem to be the limitation. Unless what you’re doing can be system generated, the user must input at some point. May be a way to ‘play’ around with the communication to the edge client but I haven’t gotten that far.
If it is system generated content - like a report - it can be automatically printed and attached. If your users receive these as email attachments originally and you use a modern email service (I hope!) you can have either an Epicor function or a separate program listen to said mailbox for attachments - but you’d have to know the context for which you are attaching.