Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 45.1
edited by Erik Bakker
on 2022/11/21 12:00
on 2022/11/21 12:00
Change comment:
There is no comment for this version
To version 310.1
edited by Carlijn Kokkeler
on 2023/12/21 14:17
on 2023/12/21 14:17
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 -1 88-CloseEncounters1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,73 +1,75 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** Store - Next phase** ==8 +== **TBD** == 8 8 9 -This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible. 10 10 11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 12 12 13 - {{info}}Formoreinformation on theStore pleasecheckoutthis [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagizStore.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}12 +== **Feedback Items** == 14 14 15 -== **New eMagiz Mendix Connector** == 14 +//__Runtime overview__// 15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 16 16 17 - This releasetroducesanew version of theMagiz Mendix Connector. Thisversion(6.0.0) will work with thecurrent runtimearchitecturend thenew runtime architecture making the migration from the existingarchitecture tothe new runtime architecture easier. The latestversion of theeMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 18 18 19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} 19 +//__Missing properties overview__// 20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 20 20 21 - ==**Flow versionstore** ~* ==22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 22 22 23 -On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect. 24 +//__Breaking changes pop-up__// 25 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@ 187-release-blog--flow-version-restore.png]]27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 26 26 27 -{{warning}}Note that the following restrictions apply when restoring to a previous version: 28 - * Changes made on definition and transformation level are **not** restored 29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 29 +//__Broker queue metrics dashboards__// 30 +It is now possible to select the MQTT broker in the queue metrics dashboards. 32 32 33 -== **Feedback items ** == 32 +//__Runtime image version__// 33 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 34 34 35 - Wehave also solved other feedback items besides the flow designer'scritical updates.35 +== **Bug Fixes** == 36 36 37 -//__ Improved help textsKafkacomponent__//38 -The help textson various configurationoptionsandthegeneralhelptextonmultipleKafkacomponentshavebeenupdatedtoclarify howtheywork andhow you oughtto configure themtoachievethe bestpossibleresultwhen sendingandreceivingmessages toand fromtopicswithineMagiz.37 +//__Message throughput__// 38 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases. 39 39 40 -//__ Improved warningmessagewhenMessageredelivery cannotbedequately executed__//41 - Wehaveimprovedthewarningyougetwhenyoucannot retrievethe messageswaitingtobe redelivered. Thishelpsclarify whatisgoingwrongwhen a userseesthis warning.40 +//__Deployment execution error message__// 41 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 42 42 43 -//__ See FlowDesignererrorsonheCreateoverview__//44 - Toimprove our offeringsurroundingthenew Flow Designerfunctionality,wenowshowontheCreateoverviewwhichoftheflows you stillhave alerts due toa misconfiguration of the flow. This will help to identify ongoing workmuchmoremanageable.43 +//__Cloud template upgrade unjust rollback__// 44 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 45 45 46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 46 +//__Missing log entries__// 47 +We improved crash handling so that log messages clearly show when and why a container failed to start. 47 47 48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 49 +//__Runtime logging__// 50 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 49 49 50 - ==**Bug Fixes**==52 +//__External recipients emailaddress__// 51 51 52 -//__Update Swagger File when changing the order of entities in gateway message__// 53 -In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this. 54 54 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 60 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 61 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 62 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 59 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 60 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 61 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 62 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 63 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 63 63 65 + 64 64 == **Key takeaways** == 65 65 66 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:68 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 67 67 68 68 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 * If you have feedback or ideas for us, talk to the Platypus 70 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 71 71 * Clear your browser cache (Ctrl + Shift + Del) 72 72 * Check out the release notes [here] 73 73 * Start thinking about how the license tracker can aid your development ... ... @@ -80,6 +80,12 @@ 80 80 {{info}} 81 81 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 82 82 83 -~*~* Indicates a GEN3-only feature. 84 -{{/info}})))((({{toc/}}))){{/container}} 85 +~*~* Indicates a next-generation-architecture only feature. 86 +{{/info}} 87 +))) 88 + 89 +((( 90 +{{toc/}} 91 +))) 85 85 {{/container}} 93 +{{/container}}