Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 80.1
edited by Erik Bakker
on 2023/02/09 08:53
Change comment: There is no comment for this version
To version 411.1
edited by Erik Bakker
on 2024/03/11 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +216 - Hack Heaven
Content
... ... @@ -1,150 +1,99 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[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.
4 4  
5 -**Hi there, eMagiz developers!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6 6  
7 -== **Dynamic Alerts** ~*~* ==
10 +Placeholder for info from Bas
8 8  
9 -{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
12 +{{info}}Text{{/info}}
10 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
14 +== **Announcement - Spring 6** ==
12 12  
13 -We offer alerting on five types.
16 +Placeholder for info from Jelle
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
18 +{{warning}}Text{{/warning}}
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
20 +== ** Updated release functionality - Infra flow selection** ==
22 22  
23 -These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
26 26  
27 -Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
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.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
30 30  
31 -== **Debugger ** ~*~* ~* ==
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.
32 32  
33 -{{warning}}Note that this functionality only works when the following criteria are met.
34 -* Your JMS server is running on the 3rd generation runtime
35 -* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 -* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
37 37  
38 -As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
34 +== ** Updated deploy functionality on-premise - Multiple environments selection** ==
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
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}}
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
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.
43 43  
44 -Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
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 -{{info}}Note the following limitations when working with the debugger.
49 - * Your entire model needs to be migrated to the 3rd generation runtime
50 - * Only **one** flow **per** runtime can be debugged **per** environment
51 - * There is only **one** overview in which **all** debugged messages are shown
52 - * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
53 - * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
54 - ** After five minutes the debug functionality will be shutdown automatically under water.
55 - ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
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.
56 56  
57 -== **Volume mapping - Network Share** ==
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.
58 58  
59 -This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
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.
60 60  
61 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
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.
62 62  
63 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
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.
64 64  
65 -== **Feedback items ** ==
66 66  
67 -We have also solved other feedback items besides the flow designer's critical updates.
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.
68 68  
69 -//__Show status on machine level under Deploy Architecture__//
70 -With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
68 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
71 71  
72 -//__Improved validation feedback on non-supported WSS4J interceptor __//
73 -We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
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.
74 74  
75 -//__Improve help text in flow testing on Java classes__//
76 -We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
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.
77 77  
78 -//__Improved readibility of notification when trying to delete a runtime__//
79 -When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
80 -
81 -//__Improved sorting of missing properties overview__//
82 -We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
83 -
84 -//__Improved notification when error message cannot be found__//
85 -We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
86 -
87 -//__Additional lifecycle management overview__//
88 -We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
89 -
90 -//__Improved feedback when memory settings are negative__//
91 -We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
92 -
93 -//__Auto upgrade for a cloud template default to "ON"__//
94 -For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
95 -
96 -//__Removed an irrelevant refresh button on a flow designer component__//
97 -We have removed an irrelevant refresh button on the standard filter component.
98 -
99 -//__Notification list shows all notifications on default__//
100 -When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
101 -
102 -== **Bug fixes ** ==
103 -
104 -//__Keep selection when copying properties__//
105 -We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
106 -
107 -//__Check on security header improved for API Gateway__//
108 -We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
109 -
110 -//__Don't show systems with only "external" flows in Design__//
111 -We fixed a bug that caused systems to appear in Design in cases where there should be none.
112 -
113 -//__Fix styling of mendix login in some occurences__//
114 -When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
115 -
116 -//__Change timing of wake-up of cloud slots on Friday__//
117 -To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
118 -
119 -//__Fixed a typo in the Topic statistics overview__//
120 -We fixed a typo in the topic statistics overview.
121 -
122 -//__Fixed a typo in the HTTP statistics overview__//
123 -We fixed a typo in the HTTP statistics overview.
124 -
125 -//__Activatation of release history when executing a deployment__//
126 -We ensured that the release history is activated when executing a deployment.
127 -
128 128  == **Fancy Forum Answers** ==
129 129  
130 130  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:
131 131  
132 -* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
133 -* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
134 -* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
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"]]
135 135  
136 -== **Key takeaways** ==
86 +== **Key Takeaways** ==
137 137  
138 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
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:
139 139  
140 140  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
141 141  * If you have feedback or ideas for us, talk to the Platypus
142 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
92 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
143 143  * Clear your browser cache (Ctrl + Shift + Del)
144 144  * Check out the release notes [here]
145 145  * Start thinking about how the license tracker can aid your development
146 146  * Start thinking about major, minor, and patch
147 -* Upgrade to the latest build number
148 148  * Keep making great integrations
149 149  
150 150  Let's stay in touch and till next time!
... ... @@ -152,6 +152,11 @@
152 152  {{info}}
153 153  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
154 154  
155 -~*~* Indicates a GEN3-only feature.
156 -{{/info}})))((({{toc/}}))){{/container}}
104 +{{/info}}
105 +)))
106 +
107 +(((
108 +{{toc/}}
109 +)))
157 157  {{/container}}
111 +{{/container}}