Replies: 1 comment 3 replies
-
|
if you’re calling the mirth rest API, and it looks like the response changed, and the release notes do not indicate that the response changed, that is likely worth posting an issue in the issue section with complete details. But I would certainly post it here first and make sure the second set of eyes looks at it before you post it as an issue |
Beta Was this translation helpful? Give feedback.
-
|
Good idea. I'm not even sure where to get the release notes for the commercial extensions... |
Beta Was this translation helpful? Give feedback.
-
|
Can you post an example of the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure on release notes either, I looked on client portal and I see the manual, but not release notes. I was under the impression that this extension had not changed in years. |
Beta Was this translation helpful? Give feedback.
-
Hi All!
I was working to use the openapi to communicate with Mirth.
The code was calling "/extensions/ssl/all" passing in the correct format and worked great in 4.4.0. However, apparently there was a breaking change in 4.4.1 that changed the accepted format of the message.
Should I create a Issue in the connect repo or is there another more appropriate repo that I can post the issue?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions