Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 843.1
edited by Erik Bakker
on 2025/01/13 10:00
on 2025/01/13 10:00
Change comment:
There is no comment for this version
To version 854.1
edited by Erik Bakker
on 2025/02/10 09:30
on 2025/02/10 09:30
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -23 6-AnotherAgent1 +238 - Preparation Paraside - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -WebHome 1 +Main.Release Information.Release Blogs.WebHome - Content
-
... ... @@ -3,46 +3,30 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, our new en vironment template willbeavailable!Please findoutmoreabout it[[here>>Main.ReleaseInformation.CloudTemplates||target="blank"]].Moreover,wehave addressed severalkeyfeedbackpointswithinourplatform.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. 7 7 8 -== ** NewEnvironmentTemplates** ==8 +== **Updated Base Image** - Flow Testing Only == 9 9 10 - As announcedonour[[statuspage>>https://status.emagiz.com/incidents/nc5jxhxtkvfg||target="blank"]]wewillreleasea new environmenttemplate to ourcommunity. Thisenvironmenttemplatecontainstwo significantchangeson yourenvironmentofwhichthe eMagizagentis key.Thisagentisresponsibleforcommunicating betweenthe variousmachineswithin yourmodel(bothon-premises andourcloud).11 - 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 your flow tests will run against the latest runtime image as of that moment. We do this to decrease the likelihood of unexpected things happening in your actual environments once we release the image to the community. 11 + 12 12 {{info}} 13 -* **Please take into consideration the following migration actions**: 14 -* You can use the [[(automatic) upgrade procedure>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained||target="blank"]] as provided within the platform to update your environments to this new environment template. 15 -* Please ensure to update the environment template before the **February, 13th 2025**. We impose this deadline to avoid delays for subsequent updates to our infrastructure. 16 -* Should you encounter any problems please your partner manager! 13 +* **Please take into consideration the following**: 14 +* This means the flow testing results could differ from those 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]]. 17 17 {{/info}} 16 + 17 +== **New eMagiz Mendix Connector**~* == 18 18 19 -== **Minor changes** == 20 -//__Help text improvements__// 21 -We have added updated the help texts on our (S)FTP components to better explain the local filter options. This to avoid confusion on the intention of those settings. 22 - 23 -//__Migration functionality removed__// 24 -We have removed Spring 6 related migration functionality from our portal given that all our customers are already migrated to the latest runtime image. As a result, this functionality became obsolete. 25 - 26 -//__Manage Alerting feedback__// 27 -We have slightly altered the user experience when configuring an alert in eMagiz with regards to the "Notification" part of the trigger. In here we now provide an explanation of what is going wrong when trying to activate the notifications **without** selecting **any** recipient. On top of that we now filter out **all** inactive users to ensure they cannot be selected as a recipient on a trigger. 19 +The new eMagiz Mendix Connector is ready and will be first implemented in our infrastructure further to assess the quality and stability of the new connector. Once this is done, we will share more information with the community about the new eMagiz Mendix Connector changes and make it available to a broader audience. In the meantime, you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems. 28 28 29 -[[image:Main.Images.Release Blog.WebHome@release-236-ux-improvement-notifications-alerting.png]] 30 - 31 31 == **Bug Fixes** == 32 -//__ Import fromStore- Design__//33 - Thepossibility of importing anythingfromthestoreinDesignis nowblockedwhenthesystemhasnotechnicalnameyet. Thisis toavoidbrokentransformationswithintheCreatephaseofeMagiz.22 +//__Removing integrations from Create__// 23 +Removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems. 34 34 35 -//__Changing number of runtimes__// 36 -As a regular user, you can now increase and decrease the number of runtimes for existing Systems. This allows you to transfer them from Design Architecture to Deploy Architecture to be utilized in future deployments. 37 - 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[Encoding mode and REST template>>https://my.emagiz.com/p/question/172825635704029463||target="blank"]] 43 -* [[Empty header causes error in JDBC Outbound Gateway>>https://my.emagiz.com/p/question/172825635704029580||target="blank"]] 44 -* [[Handle special characters in Web service outbound gateway payload>>https://my.emagiz.com/p/question/172825635704029803||target="blank"]] 45 -* [[Invalid packet length>>https://my.emagiz.com/p/question/172825635704042225||target="blank"]] 29 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]] 46 46 47 47 == **Key Takeaways** == 48 48 ... ... @@ -52,7 +52,7 @@ 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 53 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 54 * Clear your browser cache (Ctrl + Shift + Del) 55 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.23 6-AnotherAgent.WebHome||target="blank"]]39 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 58 58 * Keep making great integrations