Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 853.1
edited by Erik Bakker
on 2025/02/10 09:27
Change comment: There is no comment for this version
To version 722.1
edited by Carlijn Kokkeler
on 2024/09/25 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paraside
1 +230 - Petite Peaks
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,29 +3,31 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
6 +**Hi there, eMagiz developers!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
7 7  
8 -== **Updated Base Image** - Flow Testing Only ==
9 -
10 -With this release we introduce the new [[runtime image>>Main.Release Information.Runtime Images||target="blank"]] to our flow testing functionality. This means that as of that moment your flow tests will run against the latest runtime image. We do this to decrease the likelihood of unexpected things happening on your actual environments once we release the image to the community.
8 +{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{\info}}
11 11  
12 -{{info}}
13 -* **Please take into consideration the following**:
14 -* This means that the flow testing results could differ from the results you get once you have deployed your functionality to an environment. If something like that happens please contact us via our [[support department>>mailto:support@emagiz.com]].
15 -{{/info}}
10 +== **Feedback Items** ==
11 +//__Add integration__//
12 +When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
16 16  
17 -== **New eMagiz Mendix Connector**~* ==
18 -
19 -The new eMagiz Mendix Connector is ready and will be first implemented in our own infrastructure to further assess the quality and stability of the new connector. Once this is done we will share more information to the community about the changes related to the new eMagiz Mendix Connector and make it available for a broader audience. In the mean time you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems.
14 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
20 20  
16 +
21 21  == **Bug Fixes** ==
22 -//__Removing integrations from Create__//
23 -When removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems.
18 +//__Queues with illegal characters__//
19 +Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
20 +
21 +//__Blocked deployment step__//
22 +We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
23 +
24 24  == **Fancy Forum Answers** ==
25 25  
26 26  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
27 27  
28 -* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||target="blank"]]
28 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
29 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
30 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
29 29  
30 30  == **Key Takeaways** ==
31 31  
... ... @@ -35,7 +35,7 @@
35 35  * If you have feedback or ideas for us, talk to the Platypus
36 36  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
37 37  * Clear your browser cache (Ctrl + Shift + Del)
38 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]]
40 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
39 39  * Start thinking about how the license tracker can aid your development
40 40  * Start thinking about major, minor, and patch
41 41  * Keep making great integrations