Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 420.1
edited by Erik Bakker
on 2024/03/11 15:20
Change comment: There is no comment for this version
To version 181.1
edited by Erik Bakker
on 2023/10/12 16:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +206 - Situational Deployment
Content
... ... @@ -1,126 +1,116 @@
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 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.
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.
7 7  
8 -== ** Announcement - TLS versions deprecated** ==
7 +== **Release Date Change** ==
8 +As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9 9  
10 -Placeholder for info from Bas
10 +== **Deployment Plan** ==
11 11  
12 -{{info}}Text{{/info}}
12 +//__Improved deployment plan to make the process better and more predictable__//
13 +The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
13 13  
14 -== **Announcement - Spring 6** ==
15 +{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
15 15  
16 -We expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture in the next release. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
17 +//__Editing release properties__//
18 +With this release, it will be possible to change the description of a property by editing the property.
17 17  
18 -{{warning}}
19 -* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
20 -* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
21 -** Simple job launcher (data pipelines)
22 -** Job explorer (data pipelines)
23 -** HTTP components message sender (support object)
24 -** Web service outbound gateway (with a 'message sender' attribute specified)
25 -** SFTP session factory (support object)
26 -** API gateways with OAuth2 as security mechanism.
27 -* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
28 -** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
29 -* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
20 +//__Container memory settings__//
21 +A change in memory settings triggers redeployment of the container now.
30 30  
31 -== **Infra flow selection** ==
23 +//__Properties tab__//
24 +We have removed the deprecated tab Properties in the Deploy phase.
32 32  
33 -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.
26 +//__Cleanup old images__//
27 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
34 34  
35 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
29 +//__Performance improvements for loading releases__//
30 +Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
36 36  
37 -In edit mode, you can select a new version via the right-click option, which you already use for other flows.
32 +== **Store Improvements** ==
38 38  
39 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
34 +//__Message definition elements order__//
35 +We fixed an issue that the order of message definition elements was changed after being imported.
40 40  
41 -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.
37 +//__Importing a store item with synchronous message definitions__//
38 +We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
42 42  
43 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
40 +//__Importing store items containing static copies__//
41 +We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
44 44  
45 -== **Multiple environments selection** ==
43 +//__Importing store content__//
44 +We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
46 46  
47 -{{warning}}The following is only applicable under the following conditions:
48 - * Windows 2022 server
49 - * At least one port opened (as a consequence of a hosted web service){{/warning}}
46 +//__Store disclaimer__//
47 +Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
50 50  
51 -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.
52 -
53 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
54 -
55 55  == **Feedback Items** ==
56 -//__Easier component selection in flow designer__//
57 -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.
58 58  
59 -//__Improved handling of optionality in JSON on lists__//
60 -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.
51 +//__Alerting manual pause__//
52 +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.
61 61  
62 -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.
54 +//__Ordering of graphs in Manage__//
55 +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).
63 63  
64 -//__Loading bar when searching for log entries__//
65 -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.
57 +//__UTC times in Grafana panels__//
58 +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.
66 66  
67 -//__Improved feedback when deleting elements from Capture__//
68 -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.
60 +//__Update flow designer version__//
61 +The framework used in the flow designer has been updated to the latest version.
69 69  
70 -//__Enhanced filter options in Manage__//
71 -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.
63 +//__Carwash track TLS versions in logging__//
64 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
72 72  
73 -//__Copy property names from Create__//
74 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
66 +//__Moving channels in the flow designer__//
67 +Moving already attached channels in the flow designer has been made sligthly easier.
75 75  
76 -//__Improved feedback during migration to the current runtime architecture__//
77 -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.
69 +//__Topic sizes description change__//
70 +In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
78 78  
79 -//__Block user from making changes to their cloud while another upgrade is still in progress__//
80 -We now block users from changing their cloud configuration when another upgrade is ongoing.
72 +//__Password change notification__//
73 +When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
81 81  
82 -//__Cron trigger validation__//
83 -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.
75 +//__Password comparison__//
76 +When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
84 84  
85 -== **Bug Fixes** ==
86 -//__Making Edit (and View) the default action when configuring parameters__//
87 -We have made the Edit (and View) button the default action when configuring parameters in a transformation.
78 +//__Inactive user alerting__//
79 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
88 88  
89 -//__Property configuration pop-up resized__//
90 -We have resized the property configuration overviews to make the property value better readable.
81 +//__Alphabetical sorting on user level in HTTP statistics__//
82 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
91 91  
92 -//__Alphabetically sorted components in the flow designer__//
93 -As of this release, we now sort the components alphabetically in the flow designer.
84 +//__SOAP Web services path__//
85 +Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
94 94  
95 -//__Improved sorting on runtime overview__//
96 -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.
87 +== **Bug Fixes** ==
97 97  
98 -//__Improved sorting on catalog overview__//
99 -As of this release, we now sort the topics in the catalog by name.
89 +//__Flow designer styling__//
90 +The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
100 100  
101 -//__Styling fix on rich text editors__//
102 -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 +//__Partial search for messages__//
93 +It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
103 103  
104 -//__Styling fix on release edit__//
105 -As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
95 +//__Disk usage after cloud template update__//
96 +In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
106 106  
107 -//__Removed false-positive alerts on transformations__//
108 -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 +//__Error handling migration__//
99 +If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
109 109  
110 -//__Event Streaming Graphs - view thirty days back__//
111 -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.
112 -
113 -//__Improved helptext__//
114 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
115 -
116 116  == **Fancy Forum Answers** ==
117 117  
118 118  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:
119 119  
120 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
105 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
106 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
107 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
108 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
109 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
121 121  
122 -== **Key Takeaways** ==
123 123  
112 +== **Key takeaways** ==
113 +
124 124  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:
125 125  
126 126  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -130,6 +130,7 @@
130 130  * Check out the release notes [here]
131 131  * Start thinking about how the license tracker can aid your development
132 132  * Start thinking about major, minor, and patch
123 +* Upgrade to the latest build number
133 133  * Keep making great integrations
134 134  
135 135  Let's stay in touch and till next time!
... ... @@ -137,11 +137,6 @@
137 137  {{info}}
138 138  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
139 139  
140 -{{/info}}
141 -)))
142 -
143 -(((
144 -{{toc/}}
145 -)))
131 +~*~* Indicates a next-generation-architecture only feature.
132 +{{/info}})))((({{toc/}}))){{/container}}
146 146  {{/container}}
147 -{{/container}}