I’m curious to get others opinion on what approach to take when dealing with internal flat file manipulations and conversions; regularly outputted exports from one system that need some string finessing for import into another system.
I personally inherited a few processes that were built into our old retired eGate system that I replaced effectively with PowerShell scripts, and wondering if there is any real advantage to having these types of processes handled in Iguana.
We were using Mirth’s file import, and it worked well.
I was hoping to use the built in Iguana file import, but it ‘move’ afterwards forces the file into a date/time folder. That breaks downstream processes, so I have to manually parse and move the files. Staying in Iguana so far though
Macro Helix / McKesson
Software Developer / Integration Lead / Scrum Master
You must be logged in to reply to this topic.