Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 414.1
edited by Erik Bakker
on 2024/03/11 14:49
Change comment: There is no comment for this version
To version 97.1
edited by Erik Bakker
on 2023/04/13 08:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +195 - Easter Party
Content
... ... @@ -1,107 +1,97 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
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.
7 7  
8 -== ** Announcement - TLS versions deprecated** ==
5 +**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
9 9  
10 -Placeholder for info from Bas
7 +== **Release properties** ==**
11 11  
12 -{{info}}Text{{/info}}
9 +== **API improvements** ==
13 13  
14 -== **Announcement - Spring 6** ==
11 +//__Improved auto-generated error handling__//
12 +When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
15 15  
16 -Placeholder for info from Jelle
14 +//__Switch default message format__//
15 +We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
17 17  
18 -{{warning}}Text{{/warning}}
17 +//__Re-using elements in gateway message__//
18 +This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
19 19  
20 -== **Infra flow selection** ==
20 +//__Improved naming of API operations when adding integrations to Create__//
21 +Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
21 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 +== **3rd generation improvements** ==
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25 +//__Update of the static alerting engine__//
26 +In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
25 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.
28 +//__Add "Data pipeline" functionality__//
29 +This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
31 +//__Fix related to the debugger__//
32 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
29 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.
34 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
36 +//__Improved migration process__//
37 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
33 33  
34 -== **Multiple environments selection** ==
39 +//__Deployment plan change__//
40 +In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
35 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}}
42 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
39 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.
44 +== **Feedback items ** ==
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
46 +//__License Tracker improvements__//
47 +With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
43 43  
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.
49 +//__Ability to view the message definition for a topic__//
50 +Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
47 47  
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.
52 +//__Restricted access for uploading custom certificates to endpoints__//
53 +To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
50 50  
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.
55 +== **Bug fixes ** ==
53 53  
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.
57 +//__Improved deletion behavior for enumerations__//
58 +To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
56 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.
60 +//__Prevent "async" api operations__//
61 +With this release, we have removed the ability to select the "async" option when the default message format is API Management.
59 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.
63 +//__Importing a response definition broke the request definition__//
64 +Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
62 62  
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.
66 +//__Removing a flow does not update the API "all-entry" anymore__//
67 +When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
65 65  
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.
69 +//__Stop deployment plan when a property is missing__//
70 +Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
68 68  
69 -//__Cron trigger validation__//
70 -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.
72 +//__Cap stack trace of error messages and log entries__//
73 +To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
71 71  
72 -== **Bug Fixes** ==
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.
75 -
76 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
77 -
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.
80 -
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.
83 -
84 84  == **Fancy Forum Answers** ==
85 85  
86 86  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:
87 87  
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"]]
79 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
80 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
81 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
93 93  
94 -== **Key Takeaways** ==
83 +== **Key takeaways** ==
95 95  
96 -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:
85 +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:
97 97  
98 98  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
99 99  * If you have feedback or ideas for us, talk to the Platypus
100 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
89 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
101 101  * Clear your browser cache (Ctrl + Shift + Del)
102 102  * Check out the release notes [here]
103 103  * Start thinking about how the license tracker can aid your development
104 104  * Start thinking about major, minor, and patch
94 +* Upgrade to the latest build number
105 105  * Keep making great integrations
106 106  
107 107  Let's stay in touch and till next time!
... ... @@ -109,11 +109,6 @@
109 109  {{info}}
110 110  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111 111  
112 -{{/info}}
113 -)))
114 -
115 -(((
116 -{{toc/}}
117 -)))
102 +~*~* Indicates a GEN3-only feature.
103 +{{/info}})))((({{toc/}}))){{/container}}
118 118  {{/container}}
119 -{{/container}}