Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04

From version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
Change comment: There is no comment for this version
To version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,114 +2,61 @@
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, 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.
7 7  
8 -== ** Announcement - TLS versions deprecated** ==
6 +**Hi there, eMagiz developers!**
9 9  
10 -Placeholder for info from Bas
8 +== **TBD** ==
11 11  
12 -{{info}}Text{{/info}}
13 13  
14 -== **Announcement - Spring 6** ==
15 15  
16 -Placeholder for info from Jelle
17 -
18 -{{warning}}Text{{/warning}}
19 -
20 -== **Infra flow selection** ==
21 -
22 -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.
23 -
24 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25 -
26 -In edit mode, you can select a new version via the right-click option, which you already use for other flows.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
29 -
30 -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.
31 -
32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
33 -
34 -== **Multiple environments selection** ==
35 -
36 -{{warning}}The following is only applicable under the following conditions:
37 - * Windows 2022 server
38 - * At least 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 the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
43 -
44 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 displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
47 47  
48 -//__Improved handling of optionality in JSON on lists__//
49 -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.
14 +//__Missing properties overview__//
15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
50 50  
51 -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.
17 +ADD FIGURE
52 52  
53 -//__Loading bar when searching for log entries__//
54 -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.
19 +//__Container version overview__//
20 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
55 55  
56 -//__Improved feedback when deleting elements from Capture__//
57 -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.
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
58 58  
59 -//__Enhanced filter options in Manage__//
60 -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.
24 +//__Improved deployment process__//
25 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
61 61  
62 -//__Copy property names from Create__//
63 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
27 +//__Rebuilding of images__//
28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
64 64  
65 -//__Improved feedback during migration to the current runtime architecture__//
66 -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.
67 -
68 -//__Block user from making changes to their cloud while another upgrade is still in progress__//
69 -We now block users from changing their cloud configuration when another upgrade is ongoing.
70 -
71 -//__Cron trigger validation__//
72 -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.
73 -
74 74  == **Bug Fixes** ==
75 -//__Making Edit (and View) the default action when configuring parameters__//
76 -We have made the Edit (and View) button the default action when configuring parameters in a transformation.
77 77  
78 -//__Property configuration pop-up resized__//
79 -We have resized the property configuration overviews to make the property value better readable.
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
80 80  
81 -//__Alphabetically sorted components in the flow designer__//
82 -As of this release, we now sort the components alphabetically in the flow designer.
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
83 83  
84 -//__Improved sorting on runtime overview__//
85 -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.
38 +//__View all store items__//
39 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
86 86  
87 -//__Improved sorting on catalog overview__//
88 -As of this release, we now sort the topics in the catalog by name.
41 +//__Out of memory behavior__//
42 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
89 89  
90 -//__Styling fix on rich text editors__//
91 -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.
44 +//__Max fetch size__//
45 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
92 92  
93 -//__Styling fix on release edit__//
94 -As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
95 -
96 -//__Removed false-positive alerts on transformations__//
97 -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.
98 -
99 -//__Event Streaming Graphs - view thirty days back__//
100 -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.
101 -
102 -//__Improved helptext__//
103 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
104 -
105 105  == **Fancy Forum Answers** ==
106 106  
107 107  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:
108 108  
109 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
51 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
52 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
53 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
54 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
55 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
110 110  
111 -== **Key Takeaways** ==
112 112  
58 +== **Key takeaways** ==
59 +
113 113  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:
114 114  
115 115  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -119,6 +119,7 @@
119 119  * Check out the release notes [here]
120 120  * Start thinking about how the license tracker can aid your development
121 121  * Start thinking about major, minor, and patch
69 +* Upgrade to the latest build number
122 122  * Keep making great integrations
123 123  
124 124  Let's stay in touch and till next time!
... ... @@ -126,6 +126,7 @@
126 126  {{info}}
127 127  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
128 128  
77 +~*~* Indicates a next-generation-architecture only feature.
129 129  {{/info}}
130 130  )))
131 131