Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 410.1
edited by Erik Bakker
on 2024/03/11 14:39
Change comment: There is no comment for this version
To version 321.1
edited by Carlijn Kokkeler
on 2023/12/21 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,89 +2,78 @@
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, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
7 7  
8 -== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6 +**Hi there, eMagiz developers!**
9 9  
10 -Placeholder for info from Bas
8 +== **Logging** ==
9 +//__Missing log entries__//
10 +We improved crash handling so that log messages clearly show when and why a container failed to start.
11 11  
12 -{{info}}{{/info}}
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
13 13  
14 -== **Announcement - Spring 6** ==
15 +//__Deployment execution error message__//
16 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
15 15  
16 -Placeholder for info from Jelle
18 +== **Overviews** ==
19 +//__Runtime overview__//
20 +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.
17 17  
18 -{{warning}}{{/warning}}
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
19 19  
20 -== ** Updated release functionality - Infra flow selection** ==
24 +//__Missing properties overview__//
25 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
21 21  
22 -This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
29 +//__Runtime restart or redeploy overview__//
30 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
25 25  
26 -When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
32 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
29 29  
30 -On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
31 -
32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
33 -
34 -== ** Updated deploy functionality on-premise - Multiple environments selection** ==
35 -
36 -{{warning}}The following is only applicable under the following conditions:
37 - * Windows 2022 server
38 - * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
39 -
40 -When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
43 -
44 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 they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
47 47  
48 -//__Improved handling of optionality in JSON on lists__//
49 -Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
50 50  
51 -//__Loading bar when searching for log entries__//
52 -To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
38 +//__Breaking changes pop-up__//
39 +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'.
53 53  
54 -//__Improved feedback when deleting elements from Capture__//
55 -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.
41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
56 56  
57 -//__Enhanced filter options in Manage__//
58 -With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
43 +//__External recipients emailaddress__//
44 +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.
59 59  
60 -//__Copy property names from Create__//
61 -This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
46 +//__Broker queue metrics dashboards__//
47 +It is now possible to select the MQTT broker in the queue metrics dashboards.
62 62  
49 +//__Runtime image version__//
50 +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.
63 63  
52 +
64 64  == **Bug Fixes** ==
65 -//__Queue name validation__//
66 -The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
67 67  
68 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
55 +//__Message throughput__//
56 +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.
69 69  
70 -//__Removal of onramp__//
71 -An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
58 +//__Cloud template upgrade unjust rollback__//
59 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
72 72  
73 -//__eMagiz login__//
74 -In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
61 +//__Next generation block__//
62 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
75 75  
76 76  == **Fancy Forum Answers** ==
77 77  
78 78  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:
79 79  
80 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
81 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
82 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
83 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
84 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
68 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
69 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
70 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
71 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
72 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
85 85  
86 -== **Key Takeaways** ==
87 87  
75 +== **Key takeaways** ==
76 +
88 88  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:
89 89  
90 90  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -94,6 +94,7 @@
94 94  * Check out the release notes [here]
95 95  * Start thinking about how the license tracker can aid your development
96 96  * Start thinking about major, minor, and patch
86 +* Upgrade to the latest build number
97 97  * Keep making great integrations
98 98  
99 99  Let's stay in touch and till next time!
... ... @@ -101,6 +101,7 @@
101 101  {{info}}
102 102  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
103 103  
94 +~*~* Indicates a next-generation-architecture only feature.
104 104  {{/info}}
105 105  )))
106 106