Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 855.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
To version 748.1
edited by Carlijn Kokkeler
on 2024/10/21 11:51
on 2024/10/21 11:51
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 8-Preparation Paraside1 +232 - TBD - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,30 +3,53 @@ 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!** 7 7 8 -== **Updated Base Image** - Flow Testing Only == 8 +== **Feedback Items** == 9 + 9 9 10 - With this release, we introduce the new[[runtime image>>Main.ReleaseInformation.Runtime Images||target="blank"]] to our flow testing functionality.This means that your flow tests will runagainst the latest runtime image asof that moment.dothis to decreasethelikelihood of unexpected things happening in your actualenvironments once wereleasethe imagetothe community.11 +[[image:Main.Images.Release Blog.WebHome@release-232-explore-button.png]] 11 11 12 -{{info}} 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]]. 15 -{{/info}} 13 +//__Property name__// 14 +When creating a new property name for a new property value, it wil automatically be selected for the new property value. 16 16 17 - == **New eMagiz MendixConnector**~* ==16 +[[image:Main.Images.Release Blog.WebHome@release-232-propery-name.png]] 18 18 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. 20 - 21 21 == **Bug Fixes** == 22 -//__ Removing integrationsfrom Create__//23 - Removinganexit/entryconnectorlinkedto a systemandusingthesamemessagetypecannowberemovedfromMagizwithoutproblems.19 +//__Hidden Explore__// 20 +The 'Explore' button will no longer be hidden if there are no results when searching on a queue name in the queue browser. 24 24 22 +//__Property name__// 23 +The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. 24 + 25 +[[image:Main.Images.Release Blog.WebHome@release-232-delete-container.png]] 26 + 27 +//__Technical names__// 28 +It is no longer possible anymore to create machines with the same technical name. 29 + 30 +//__Failover systems__// 31 +When enabling or disabling our failover feature for a system, its connector container will no longer be moved to another machine if not required. 32 + 33 +//__Deploy architecture changes__// 34 +The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed. 35 + 36 +//__Code mappings search__// 37 +When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated. This has been fixed. 38 + 39 +[[image:Main.Images.Release Blog.WebHome@release-232-code-mappings.png]] 40 + 41 +//__Source filters__// 42 +Source filters will now display the attribute filter statement correctly. 43 + 44 +[[image:Main.Images.Release Blog.WebHome@release-232-source-filters.png]] 45 + 25 25 == **Fancy Forum Answers** == 26 26 27 27 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: 28 28 29 -* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]] 50 +* [[SOAP Webservice error when using namespaces>>https://my.emagiz.com/p/question/172825635703978319||target="blank"]] 51 +* [[Unable to retrieve topics in Kafka Mendix module>>https://my.emagiz.com/p/question/172825635703978127||target="blank"]] 52 +* [[application/x-www-form-urlencoded token>>https://my.emagiz.com/p/question/172825635703965691||target="blank"]] 30 30 31 31 == **Key Takeaways** == 32 32 ... ... @@ -36,7 +36,7 @@ 36 36 * If you have feedback or ideas for us, talk to the Platypus 37 37 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 38 38 * Clear your browser cache (Ctrl + Shift + Del) 39 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.23 8-PreparationParadise||target="blank"]]62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.231 - Microscopic Madness.WebHome||target="blank"]] 40 40 * Start thinking about how the license tracker can aid your development 41 41 * Start thinking about major, minor, and patch 42 42 * Keep making great integrations