lol, reading is fundamental. Thank you for pointing out what should have been obvious.
I missed the "User" in your example as a custom implementation. I just reviewed these provided adapters, very nice! What continues to puzzle me is why the product does not provide a Business Operation off them (and others). I know, support issues, right?
I just completed a custom "adaptation" using their provided Util.Pipe adapter, because the code was a bit crusty. It did serve as nice reference source, just not as nice as these SQL adapters.
... because we're running 2018 and that SQL operation does not exist to use in our operations:
Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2018.1.4 (Build 505_1U) Thu May 28 2020 10:11:16 EDT [HealthShare Modules:Core:15.032.9035 + Linkage Engine:15.032.9035]
Can you expand upon your question a little more? I just posted an article for sending message data to an external SQL database -- but by invoking a Stored Procedure (not SQL inserts or transactions), which I find eminently better to keep that business logic out of the messaging bus.
To leave a comment or answer to post please log in
Please log in
To leave a post please log in