Skip to Content

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 414.1
edited by Erik Bakker
on 2024/03/11 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 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.
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.
7 7  
8 8  == ** Announcement - TLS versions deprecated** ==
9 9  
... ... @@ -19,15 +19,15 @@
19 19  
20 20  == **Infra flow selection** ==
21 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.
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 24  [[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25 25  
26 -In edit mode, you can select a new version via the right-click option, which you already use for other flows.
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 28  [[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
29 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.
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 32  [[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
33 33  
... ... @@ -35,78 +35,61 @@
35 35  
36 36  {{warning}}The following is only applicable under the following conditions:
37 37   * Windows 2022 server
38 - * At least one port opened (as a consequence of a hosted web service){{/warning}}
38 + * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
39 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.
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 41  
42 42  [[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
43 43  
44 44  == **Feedback Items** ==
45 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.
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.
47 47  
48 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.
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.
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.
52 -
53 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.
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.
55 55  
56 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.
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.
58 58  
59 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.
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.
61 61  
62 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.
61 +This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
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.
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.
67 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.
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.
70 70  
71 71  //__Cron trigger validation__//
72 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 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.
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 -//__Property configuration pop-up resized__//
79 -We have resized the property configuration overviews to make the property value better readable.
76 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
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.
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  
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.
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.
86 86  
87 -//__Improved sorting on catalog overview__//
88 -As of this release, we now sort the topics in the catalog by name.
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.
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"]]
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"]]
110 110  
111 111  == **Key Takeaways** ==
112 112