Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 156.1
edited by CarlijnKokkeler
on 2023/10/10 13:56
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 -206 - Situational Deployment
1 +216 - Hack Heaven
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,54 +1,89 @@
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 few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6 6  
7 -== **Deployment Plan** ==
10 +Placeholder for info from Bas
8 8  
9 -//__Improved deployment plan to make the process better and more predictable__//
10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
12 +{{info}}Text{{/info}}
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
14 +== **Announcement - Spring 6** ==
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
16 +Placeholder for info from Jelle
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -
23 -== **Store Improvements** ==
24 -
18 +{{warning}}Text{{/warning}}
25 25  
20 +== ** Updated release functionality - Infra flow selection** ==
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.
23 +
24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
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.
27 +
28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
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 +
26 26  == **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.
27 27  
28 -//__Alerting manual pause__//
29 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
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.
30 30  
31 -//__Ordering of graphs in Manage__//
32 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
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.
33 33  
34 -//__UTC times in Grafana panels__//
35 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
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.
36 36  
37 -//__Update flow designer version__//
38 -The framework used in the flow designer has been updated to the latest version.
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.
39 39  
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.
40 40  
41 -
63 +
42 42  == **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.
43 43  
68 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
44 44  
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.
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.
75 +
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||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"]]
50 50  
51 -== **Key takeaways** ==
86 +== **Key Takeaways** ==
52 52  
53 53  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:
54 54  
... ... @@ -59,7 +59,6 @@
59 59  * Check out the release notes [here]
60 60  * Start thinking about how the license tracker can aid your development
61 61  * Start thinking about major, minor, and patch
62 -* Upgrade to the latest build number
63 63  * Keep making great integrations
64 64  
65 65  Let's stay in touch and till next time!
... ... @@ -67,6 +67,11 @@
67 67  {{info}}
68 68  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69 69  
70 -~*~* Indicates a next-generation-architecture only feature.
71 -{{/info}})))((({{toc/}}))){{/container}}
104 +{{/info}}
105 +)))
106 +
107 +(((
108 +{{toc/}}
109 +)))
72 72  {{/container}}
111 +{{/container}}