Yep. Its pretty much Cloud ready, they just need to fix their Paths and viola.
Of course add more Dump Sources checkboxes to like Electronic Interfaces, EDI what not which we can enable in config. I know BPMs and EFX for sure have it. Maybe even EI.
Posting Rules sources are good too to se when developing Custom Rules.
Also that disabled=“false” is used to turn BPMs for debugging off system wide. They should make that Cloud friendly. Sometimes easier to disable all BPMs to test if its your or Epicor
When I used TEMP it wrote it to the Service Accounts Temp folder but again it made a sub-folder Sources.
Once you change the path you must either restart the pool or recycle I can never remember its one of those. Then you must trigger a BPM change like Disable/Enable to see it write.
Would probably be best to have it put in the admin folder of EpicorData. Therefor it would be available in server file download under Admin like the server logs and base EI files.
An interesting thing is that every time you compile a function (demote/promote cycle) - a revisioned compiled copy is saved, i don’t see it exposed to the user anywhere, but you can see it in the backend.
Yeah, something to keep in mind for potential attempts and solutions is each API request can go to a different container/IIS instance. Meaning that any file storage/access location would have to be shared between containers for reliable access. Consistency between containers now sems a lot better but earlier on, let’s just say having different behaviour depending on which container was used to serve each request was the stuff of nighwares for troubleshooting.
Interesting. Not sure I follow. Are you saying, for example, that in File Server Download or via sandbox.io the file list in incomplete or they’re potentially listing files from multiple servers??
Yes, anything company/instance specific/saved would be saved outside the container. Containers for the most part should be considered generic and disposable at anytime. Therefore, unless ‘temporary’ files are configured to be saved and loaded outside the container, such temporary and inconsistent access challenges are likely to occur.
I never bothered playing around with the dump sources thing so idk what files are expected from that but I dug around on the cloud server we have and found these.