Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
on 2024/03/11 15:13
Change comment:
There is no comment for this version
To version 315.1
edited by Carlijn Kokkeler
on 2023/12/21 14:40
on 2023/12/21 14:40
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 -21 6-HackHeaven1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,114 +2,80 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 - 6 -**Hi there, eMagiz developers!** As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes. 7 7 8 - ==**Announcement- TLS versionsdeprecated**==6 +**Hi there, eMagiz developers!** 9 9 10 - Placeholderfor info fromBas8 +== **TBD** == 11 11 12 -{{info}}Text{{/info}} 13 13 14 -== **Announcement - Spring 6** == 15 15 16 - Placeholderfor info fromJelle12 +== **Feedback Items** == 17 17 18 -{{warning}}Text{{/warning}} 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. 19 19 20 - == **Infraflow selection** ==17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 21 21 22 -This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually. 19 +//__Missing properties overview__// 20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 23 23 24 -[[image:Main.Images.Release Blog.WebHome@release-21 6-hack-heaven--infra-flow-comparison.png]]22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 25 25 26 -In edit mode, you can select a new version via the right-click option, which you already use for other flows. 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'. 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-21 6-hack-heaven--infra-flow-selection.png]]27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 29 29 30 -We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release. 29 +//__External recipients emailaddress__// 30 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 31 31 32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 32 +//__Broker queue metrics dashboards__// 33 +It is now possible to select the MQTT broker in the queue metrics dashboards. 33 33 34 -== **Multiple environments selection** == 35 +//__Runtime image version__// 36 +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. 35 35 36 -{{warning}}The following is only applicable under the following conditions: 37 - * Windows 2022 server 38 - * At least one port opened (as a consequence of a hosted web service){{/warning}} 38 +//__Runtime restart or redeploy overview__// 39 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 39 39 40 - When configuringyour Deploy Agent, you now havean additionalption that theusercan activate. Thischeckbox unlocks thepossibility of stability whenrunning multipleagents on one machine.41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 41 41 42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 43 - 44 -== **Feedback Items** == 45 -//__Easier component selection in flow designer__// 46 -The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier. 47 - 48 -//__Improved handling of optionality in JSON on lists__// 49 -Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties. 50 - 51 -With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired. 52 - 53 -//__Loading bar when searching for log entries__// 54 -To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search. 55 - 56 -//__Improved feedback when deleting elements from Capture__// 57 -To better specify to the user which integration or system the user intends to delete, we have improved the text in the confirmation pop-up. This way, we can provide more information to the user to avoid mistakes. 58 - 59 -//__Enhanced filter options in Manage__// 60 -With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places. 61 - 62 -//__Copy property names from Create__// 63 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying. 64 - 65 -//__Improved feedback during migration to the current runtime architecture__// 66 -Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order. 67 - 68 -//__Block user from making changes to their cloud while another upgrade is still in progress__// 69 -We now block users from changing their cloud configuration when another upgrade is ongoing. 70 - 71 -//__Cron trigger validation__// 72 -We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression. 73 - 74 74 == **Bug Fixes** == 75 -//__Making Edit (and View) the default action when configuring parameters__// 76 -We have made the Edit (and View) button the default action when configuring parameters in a transformation. 77 77 78 -//__ Property configuration pop-upresized__//79 - Wehaveresizedthe propertyconfigurationoverviewstomakethepropertyvaluebetter readable.45 +//__Message throughput__// 46 +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. 80 80 81 -//__ Alphabetically sorted componentsintheflowdesigner__//82 - As ofthis release,we nowsort the componentsalphabeticallyin the flowdesigner.48 +//__Deployment execution error message__// 49 +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. 83 83 84 -//__ Improvedsortingonruntimeoverview__//85 -A sof thisrelease,we nowsorttheruntimes inthe runtimeoverviewcorrectlybytime. Thismeansthat theruntime with a changedstatus, closestto thecurrentdateandtime, is shownatthe topofthe list. This should reducethe chance of overlookinga critical mistake.51 +//__Cloud template upgrade unjust rollback__// 52 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 86 86 87 -//__ Improvedsortingon catalogoverview__//88 - Asofthisrelease,wenowsort thetopics inthecatalogby name.54 +//__Missing log entries__// 55 +We improved crash handling so that log messages clearly show when and why a container failed to start. 89 89 90 -//__ Styling fix on richtexteditors__//91 - Rich texteditorsareusedinvariousparts of theportal.This releasefixesa brokenstylingconfigurationthat madeitdifficulttofillin informationintheseeditors.57 +//__Runtime logging__// 58 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 92 92 93 -//__ Stylingfixonrelease edit__//94 -A s of this release,the correcticon(green)will beshownwhenwanting toadd a secondAPI operation undertheme"header."60 +//__Next generation block__// 61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 95 95 96 -//__Removed false-positive alerts on transformations__// 97 -When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation. 63 +//__Feedback deployment plan__// 98 98 99 -//__Event Streaming Graphs - view thirty days back__// 100 -Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further. 101 101 102 -//__Improved helptext__// 103 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 104 - 105 105 == **Fancy Forum Answers** == 106 106 107 107 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: 108 108 109 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 70 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 71 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 72 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 73 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 74 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 110 110 111 -== **Key Takeaways** == 112 112 77 +== **Key takeaways** == 78 + 113 113 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: 114 114 115 115 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -119,6 +119,7 @@ 119 119 * Check out the release notes [here] 120 120 * Start thinking about how the license tracker can aid your development 121 121 * Start thinking about major, minor, and patch 88 +* Upgrade to the latest build number 122 122 * Keep making great integrations 123 123 124 124 Let's stay in touch and till next time! ... ... @@ -126,6 +126,7 @@ 126 126 {{info}} 127 127 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 128 128 96 +~*~* Indicates a next-generation-architecture only feature. 129 129 {{/info}} 130 130 ))) 131 131