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
on 2025/02/10 09:27
Change comment:
There is no comment for this version
To version 873.1
edited by Erik Bakker
on 2025/03/10 09:53
on 2025/03/10 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 38-PreparationParaside1 +240 - Spring Cleaning - Content
-
... ... @@ -3,29 +3,33 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, finishingthefirst iteration of ournew eMagiz Mendix Connectorand thefirstiterationofurnew base image. We will firstutilizethenew eMagizMendix Connectortogetan even betterfeeling of itsperformance, butyou will noticeUI change straightaway.Once we have passedthathurdle, wewill sharemore informationabout it and releaseittoa broader range ofcustomers. Regarding the base image, we will now introducethis to ourflowtesting offering toseeif anythingunexpected happens.This is an additionalsafetymeasurewe haveput in placetoreduce the chance of something breakingin yourmodel oncehenewbase imageis released.On top ofthat, we have some minor updatestoimprovethe qualityof the platform.6 +**Hi there, eMagiz developers!** In this release, we focused on tidying up our house to make it ready for various cool things to come later this year. As a result, we have a set of infastrucutural improvements as well as several UI/UX related improvements and bug fixes for you to enjoy. 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 +== **Minor Changes** == 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 +//__Alerts/Notifications improved UI/UX__// 11 +Alerts/Notifications now have an icon before the text to put further emphasis on the meaning. One example of such a change is shown below. 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. 13 +[[image:Main.Images.Release Blog.WebHome@release-240-improved-icon-alerts.png]] 20 20 15 +//__Badge, Switch, and progess bar have an improved UI/UX__// 16 +We have updated our badge, switch and progress bar components. This to improve the overall quality and consistency of what we show to the user. One example of such a change is shown below. 17 + 18 +[[image:Main.Images.Release Blog.WebHome@release-240-improved-badge-alerts.png]] 19 + 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. 21 +//__Auto-creation API Operation entry gate__// 22 +We have changed the auto-creation behavior for entry gates. This means that we now avoid creating functionality in these entry gates that is only relevant for flows running inside a Mendix app. 23 + 24 +//__Infra flow reset Mendix Connector__// 25 +Infra flows for systems labeled as a "Mendix Connector" can no be reset once more under all circumstances, also when your model utilize the code mapping functionality. 26 + 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"]] 31 +* [[sum function in xpath concatenates instead of sums>>https://my.emagiz.com/p/question/172825635704067995||target="blank"]] 32 +* [["Failed to list files" error log>>https://my.emagiz.com/p/question/172825635704067900||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.2 38-PreparationParadise.WebHome||target="blank"]]42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.240 - Spring Cleaning.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