Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/04/18 13:12
From version 70.1
edited by Erik Bakker
on 2023/01/18 11:05
on 2023/01/18 11:05
Change comment:
There is no comment for this version
To version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
on 2023/07/17 15:13
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 - 190 -FastForward1 +201 - Be Informed - Content
-
... ... @@ -2,117 +2,59 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** I t has beena whilesince ourlastdeploymenton the9th of December. Asa resultwe havefinishedupalot ofnewimprovements to our 3rd generationruntime offering and fixed a variety of annoyingbugsas wellassomesmall improvements. This releaseischaracterizedbythe major stepswe tooktorelease several majorfeatures onour3rd generationruntimeamong which arethequeue browser and messageredelivery functionality.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you. 6 6 7 -== **Queue Browser** ~*~* == 7 +== **Announcement - Release Properties** == 8 +As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}} 10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button. 10 10 11 - Toenhancethe observability of your integration landscapewhile runningin the3rd generation runtimearchitecturewe haveadded a new feature toour Manage phase calledthe "Queue browser". You canaccess this functionality via the"Explore" menu option in Manage.With the helpof the queue browser you can, as the name suggests, browse your queue.13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 12 12 13 -To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button. 15 +== ** Breadcrumb navigation in eMagiz ** == 16 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@ 190-release-blog--queue-browser-overview.png]]18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 16 16 17 - Afterselecting the queue andchoosing the option eMagiz will show you the list of messages (oldest first) that arecurrentlyonthequeue (Explore option) or that passed the queue since themoment you activate the option (Wiretap option). For each messageyou have various options at your disposal.20 +== **Feedback Items** == 18 18 19 -* Delete the message from the queue (Explore option) 20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue. 21 -* Clear message from the wiretap queue (Wiretap option) 22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore 23 -* Refresh messages list (both options) 24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first 25 -* Save as test message 26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality. 27 -* Download 28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed. 22 +//__Improved layout of catalog page in Design__// 23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations. 29 29 30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] 25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 31 31 32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]] 28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 33 33 34 -== **Message Redelivery ** ~*~* == 31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 35 35 36 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}} 34 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 37 37 38 - [[image:Main.Images.ReleaseBlog.WebHome@190-release-blog--message-redelivery-overview.png]]37 +== **Bug Fixes** == 39 39 40 -Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred). 39 +//__Avoid clicking on other components while deleting another__// 40 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 41 41 42 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before. 42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved the validation feedback when migrating to the next-generation architecture. 43 43 44 -On top of that we have added some additional functionality. 45 +//__Make sure that user credentials can be viewed with view rights__// 46 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights. 45 45 46 -* Search option 47 - ** Original queue name 48 - ** Original message ID (which can be found as a header called jms_messageid in the error message view) 49 -* Save as test message 50 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. 51 -* Download 52 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed. 48 +//__Refresh behavior within the deployment plan is fixed__// 49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 53 53 54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 55 - 56 -== **3rd generation runtime bolstering** == 57 - 58 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 59 - 60 -//__Define memory settings for on-premise runtimes from Deploy Architecture__// 61 -With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise. 62 - 63 -//__Empty runtime feedback when deploying a release (or setting the release as active)__// 64 -To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture. 65 - 66 -//__Auto-fill namespaces for SOAP hosted webservices__// 67 -Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages. 68 - 69 -//__Updated H2 database setting__// 70 -As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down. 71 - 72 -{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}} 73 - 74 -//__Runtime settings option added to context menu on runtime level Deploy Architecture__// 75 -As a replacement of the current HTTP settings context menu we have added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service) you now also can define whether the control bus needs to work for this runtime. 76 - 77 -//__Deploy Agent option added to context menu on machine level Deploy Architecture__// 78 -With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]] 79 - 80 -//__Performance improvement creating a release__// 81 -With this release, we have improved the performance of creating a release. 82 - 83 -== **Feedback items ** == 84 - 85 -We have also solved other feedback items besides the flow designer's critical updates. 86 - 87 -//__Sensitive information stored in properties is masked __// 88 -We have made how we display sensitive information across the portal in the same manner for various parts of the portal. 89 - 90 -//__Importing "Private" store content to which you do not have access__// 91 -We have improved the user feedback a user will get when trying to import a "Private" store item that is not available to the user. 92 - 93 - 94 -== **Bug fixes ** == 95 - 96 -//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__// 97 -We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality. 98 - 99 -//__Synchronization of Event Streaming topic states__// 100 -We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics. 101 - 102 -//__Copy and paste default support objects__// 103 -With this release you can now copy and paste components without having to worry that additional support objects that already exist in your target flow are copied over and over into the same flow. 104 - 105 -//__Fix editability of properties when importing store items__// 106 -With this release you can once again change property names upon importing a store item. 107 - 108 108 == **Fancy Forum Answers** == 109 109 110 110 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: 111 111 112 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]] 113 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]] 114 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]] 115 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 116 116 117 117 == **Key takeaways** == 118 118