Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 254.1
edited by Carlijn Kokkeler
on 2023/11/21 12:04
Change comment: Renamed back-links.
To version 410.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 -209 - Max Verstappen
1 +216 - Hack Heaven
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,76 +2,88 @@
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.
5 5  
6 -**Hi there, eMagiz developers!** We have done .....
8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
7 7  
8 -{{warning}}
9 -Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 -{{/warning}}
10 +Placeholder for info from Bas
11 11  
12 -== **Quicker Deployment Plan** ==
12 +{{info}}{{/info}}
13 13  
14 -We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
14 +== **Announcement - Spring 6** ==
15 15  
16 -== **Next Generation Architecture Default** ==
16 +Placeholder for info from Jelle
17 17  
18 -With this release, the next generation architecture will become the default. New models will use this generation as default.
18 +{{warning}}{{/warning}}
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
20 +== ** Updated release functionality - Infra flow selection** ==
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
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.
23 23  
24 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
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.
27 27  
28 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
29 29  
30 -== **Feedback Items** ==
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 31  
32 -//__Unused properties overview__//
33 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
34 34  
35 -* Not used by any runtime that is in the Create phase release.
36 -* Not required by a flow that is in the Create phase release.
37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
34 +== ** Updated deploy functionality on-premise - Multiple environments selection** ==
38 38  
39 -//__Send build requests asynchronously__//
40 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
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 -//__Queue explorer milliseconds__//
43 -The queue browser now displays milliseconds in the timestamps.
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.
44 44  
45 -//__Cancel and next buttons order__//
46 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
47 47  
48 -//__Unused images__//
49 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
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.
50 50  
51 -//__Carwash logging__//
52 -A new logging feature enabling us to make better choices in encryption standards will be released.
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.
53 53  
54 -//__Static alerts queue consumers__//
55 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
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.
56 56  
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.
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.
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.
62 +
63 +
57 57  == **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.
58 58  
59 -//__Flow Designer connection line__//
60 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
68 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
61 61  
62 -//__Portal for migrated models__//
63 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
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.
64 64  
65 -//__Error channel inbounds__//
66 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
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.
67 67  
68 68  == **Fancy Forum Answers** ==
69 69  
70 70  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:
71 71  
72 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
73 73  
74 -== **Key takeaways** ==
86 +== **Key Takeaways** ==
75 75  
76 76  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:
77 77  
... ... @@ -82,7 +82,6 @@
82 82  * Check out the release notes [here]
83 83  * Start thinking about how the license tracker can aid your development
84 84  * Start thinking about major, minor, and patch
85 -* Upgrade to the latest build number
86 86  * Keep making great integrations
87 87  
88 88  Let's stay in touch and till next time!
... ... @@ -90,7 +90,6 @@
90 90  {{info}}
91 91  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92 92  
93 -~*~* Indicates a next-generation-architecture only feature.
94 94  {{/info}}
95 95  )))
96 96