Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 113.1
edited by Erik Bakker
on 2023/05/09 12:59
Change comment: There is no comment for this version
To version 417.1
edited by Erik Bakker
on 2024/03/11 15:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +216 - Hack Heaven
Content
... ... @@ -1,69 +1,136 @@
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!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
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.
6 6  
7 -== **Event streaming alerting** ==
8 +== ** Announcement - TLS versions deprecated** ==
8 8  
9 -With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
10 +Placeholder for info from Bas
10 10  
11 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
12 +{{info}}Text{{/info}}
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
14 +== **Announcement - Spring 6** ==
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16 +In the next release, we expect to release a major version of our current runtime base image. This image moves the eMagiz stack from Java 8 to Java 17, and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 +{{warning}}
19 +* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changes. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
20 +* To help you identify which flow versions are especially important here, you can consider all flows that contain any of the following components:
21 +** Simple job launcher (data pipelines)
22 +** Job explorer (data pipelines)
23 +** HTTP components message sender (support object)
24 +** Web service outbound gateway (with a 'message sender' attribute specified)
25 +** SFTP session factory (support object)
26 +** API gateways with OAuth2 as security mechanism.
27 +* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java version changes and the Spring version changes, this may affect the availability of the libraries on the classpath, and therefore the validity of import statements. You can already test the Groovy script using the flow testing functionality as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
28 +** In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes
29 +* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production.{{/warning}}
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
32 +== **Infra flow selection** ==
22 22  
23 -For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
34 +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.
24 24  
25 -== **3rd generation improvements** ==
36 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
26 26  
27 -//__Increased grace period for shutdown__//
28 -In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
38 +In edit mode, you can select a new version via the right-click option, which you already use for other flows.
29 29  
30 -//__Update at once or not__//
31 -This release fixes re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double lane Docker setup.
40 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
32 32  
33 -//__Improved user feedback while executing a deployment plan__//
34 -This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information of why this cannot be executed is shown to the user. This way they can take this information and act upon it instead of assuming everything went well.
42 +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.
35 35  
36 -//__Improved auto-healing when running in a hybrid situation__//
37 -In situations where you run in a hybrid situation (i.e. partly next-gen and partly the current generation) we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next generation architecture.
44 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
38 38  
39 -== **Feedback items ** ==
46 +== **Multiple environments selection** ==
40 40  
41 -//__Make sure the message format can be viewed without "Start editing"__//
42 -With this release, we have ensured that when you navigate to Design -> System message you can see the message format (i.e. XML, JSON or EDI) without entering the "Start Editing" mode.
48 +{{warning}}The following is only applicable under the following conditions:
49 + * Windows 2022 server
50 + * At least one port opened (as a consequence of a hosted web service){{/warning}}
43 43  
44 -//__Various styling improvements in the flow testing functionality__//
45 -Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
52 +When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
46 46  
54 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
55 +
56 +== **Feedback Items** ==
57 +//__Easier component selection in flow designer__//
58 +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.
59 +
60 +//__Improved handling of optionality in JSON on lists__//
61 +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.
62 +
63 +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.
64 +
65 +//__Loading bar when searching for log entries__//
66 +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.
67 +
68 +//__Improved feedback when deleting elements from Capture__//
69 +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.
70 +
71 +//__Enhanced filter options in Manage__//
72 +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.
73 +
74 +//__Copy property names from Create__//
75 +This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
76 +
77 +//__Improved feedback during migration to the current runtime architecture__//
78 +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.
79 +
80 +//__Block user from making changes to their cloud while another upgrade is still in progress__//
81 +We now block users from changing their cloud configuration when another upgrade is ongoing.
82 +
83 +//__Cron trigger validation__//
84 +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.
85 +
86 +== **Bug Fixes** ==
87 +//__Making Edit (and View) the default action when configuring parameters__//
88 +We have made the Edit (and View) button the default action when configuring parameters in a transformation.
89 +
90 +//__Property configuration pop-up resized__//
91 +We have resized the property configuration overviews to make the property value better readable.
92 +
93 +//__Alphabetically sorted components in the flow designer__//
94 +As of this release, we now sort the components alphabetically in the flow designer.
95 +
96 +//__Improved sorting on runtime overview__//
97 +As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
98 +
99 +//__Improved sorting on catalog overview__//
100 +As of this release, we now sort the topics in the catalog by name.
101 +
102 +//__Styling fix on rich text editors__//
103 +Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
104 +
105 +//__Styling fix on release edit__//
106 +As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
107 +
108 +//__Removed false-positive alerts on transformations__//
109 +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.
110 +
111 +//__Event Streaming Graphs - view thirty days back__//
112 +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.
113 +
114 +//__Improved helptext__//
115 +We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
116 +
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
121 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
54 54  
55 -== **Key takeaways** ==
123 +== **Key Takeaways** ==
56 56  
57 -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:
125 +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:
58 58  
59 59  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
129 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 63  * Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
65 65  * Start thinking about major, minor, and patch
66 -* Upgrade to the latest build number
67 67  * Keep making great integrations
68 68  
69 69  Let's stay in touch and till next time!
... ... @@ -71,6 +71,11 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 -~*~* Indicates a GEN3-only feature.
75 -{{/info}})))((({{toc/}}))){{/container}}
141 +{{/info}}
142 +)))
143 +
144 +(((
145 +{{toc/}}
146 +)))
76 76  {{/container}}
148 +{{/container}}