Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 58.1
edited by Erik Bakker
on 2023/01/18 08:57
Change comment: There is no comment for this version
To version 412.1
edited by Erik Bakker
on 2024/03/11 14:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +216 - Hack Heaven
Content
... ... @@ -1,107 +1,107 @@
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!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6 6  
7 -== **Queue Browser** ==
10 +Placeholder for info from Bas
8 8  
9 -{{warning}}Note that this functionality only works 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 the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
14 +== **Announcement - Spring 6** ==
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 of your actual message that pass through the queue from the moment you pressed the Wiretap button.
16 +Placeholder for info from Jelle
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
18 +{{warning}}Text{{/warning}}
16 16  
17 -After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
20 +== ** Updated release functionality - Infra flow selection** ==
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 +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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
31 31  
32 -== **3rd generation runtime bolstering** ==
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.
33 33  
34 -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.
28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
35 35  
36 -//__SOAP and REST web services migration, including splitting them__//
37 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
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.
38 38  
39 -//__Changing SSL settings for 3rd generation runtime models works__//
40 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
41 41  
42 -//__Improved migration for JMS flows__//
43 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
34 +== ** Updated deploy functionality on-premise - Multiple environments selection** ==
44 44  
45 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
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}}
46 46  
47 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
48 -As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
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.
49 49  
50 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
51 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
52 52  
53 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
54 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
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.
55 55  
56 -//__Added "Reset" functionality__//
57 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
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.
58 58  
59 -== **Feedback items ** ==
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.
60 60  
61 -We have also solved other feedback items besides the flow designer's critical updates.
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.
62 62  
63 -//__Improved naming convention on Store related pages__//
64 -We have improved various display names using the merge functionality within our store offering.
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.
65 65  
66 -//__Update security protocols for our internal architecture__//
67 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
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.
68 68  
69 -//__Improved read-only description for "if exists" constructions in Transformations__//
70 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
63 +//__Improved feedback during migration to the current-runtime architecture__//
64 +We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
71 71  
66 +//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
67 +We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
72 72  
73 -== **Bug fixes ** ==
69 +//__Cron trigger validation__//
70 +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.
74 74  
75 -//__Decent validation feedback when not filling in the property value__//
76 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
72 +== **Bug Fixes** ==
73 +//__Queue name validation__//
74 +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.
77 77  
78 -//__Incorrect resource locations__//
79 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
76 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
80 80  
81 -//__Apply to environment in User Management performance improvement__//
82 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
78 +//__Removal of onramp__//
79 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
83 83  
81 +//__eMagiz login__//
82 +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.
83 +
84 84  == **Fancy Forum Answers** ==
85 85  
86 86  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:
87 87  
88 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
89 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
90 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
91 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
88 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
89 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
90 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
91 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
92 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
92 92  
93 -== **Key takeaways** ==
94 +== **Key Takeaways** ==
94 94  
95 -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:
96 +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:
96 96  
97 97  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98 98  * If you have feedback or ideas for us, talk to the Platypus
99 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
100 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
100 100  * Clear your browser cache (Ctrl + Shift + Del)
101 101  * Check out the release notes [here]
102 102  * Start thinking about how the license tracker can aid your development
103 103  * Start thinking about major, minor, and patch
104 -* Upgrade to the latest build number
105 105  * Keep making great integrations
106 106  
107 107  Let's stay in touch and till next time!
... ... @@ -109,6 +109,11 @@
109 109  {{info}}
110 110  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111 111  
112 -~*~* Indicates a GEN3-only feature.
113 -{{/info}})))((({{toc/}}))){{/container}}
112 +{{/info}}
113 +)))
114 +
115 +(((
116 +{{toc/}}
117 +)))
114 114  {{/container}}
119 +{{/container}}