Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 184.1
edited by Carlijn Kokkeler
on 2023/10/12 16:42
Change comment: There is no comment for this version
To version 464.1
edited by Carlijn Kokkeler
on 2024/04/23 10:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +219 - Creation Carousel
Content
... ... @@ -1,114 +1,48 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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.
6 +**Hi there, eMagiz developers!**
6 6  
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 (4: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 -== **Deployment Plan** ==
11 -
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.
14 -
15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
16 -
17 -//__Editing release properties__//
18 -With this release, it will be possible to change the description of a property by editing the property.
19 -
20 -//__Container memory settings__//
21 -A change in memory settings triggers redeployment of the container now.
22 -
23 -//__Properties tab__//
24 -We have removed the deprecated tab Properties in the Deploy phase.
25 -
26 -//__Cleanup old images__//
27 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
28 -
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.
31 -
32 -== **Store Improvements** ==
33 -
34 -//__Message definition elements order__//
35 -We fixed an issue that the order of message definition elements was changed after being imported.
36 -
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.
39 -
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.
42 -
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.
45 -
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.
48 -
49 49  == **Feedback Items** ==
10 +//__Machine agents__//
11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more here.
50 50  
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.
13 +//__Custom webhook__//
14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more here.
53 53  
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).
16 +//__eMagiz Mendix connector__//
17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4
56 56  
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.
19 +//__Improved OpenAPI import__//
20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
59 59  
60 -//__Update flow designer version__//
61 -The framework used in the flow designer has been updated, improving performance.
62 -
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.
65 -
66 -//__Moving channels in the flow designer__//
67 -Moving already attached channels in the flow designer has been made sligthly easier.
68 -
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.
71 -
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.
74 -
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.
77 -
78 -//__Inactive user alerting__//
79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
80 -
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.
83 -
84 -
85 85  == **Bug Fixes** ==
23 +//__Error handling__//
24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
86 86  
87 -//__Flow designer styling__//
88 -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.
26 +//__Volume mapping passwords__//
27 +Passwords for network volumes are hidden on the machine after deployment.
89 89  
90 -//__Partial search for messages__//
91 -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".
29 +//__Create integration removal__//
30 +When removing an integration from Create, the Create phase is correctly updated as well.
92 92  
93 -//__Disk usage after cloud template update__//
94 -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.
32 +//__Legacy statistics__//
33 +Legacy pages are now correctly hidden when running on the current runtime architecture.
95 95  
96 -//__Error handling migration__//
97 -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.
98 -
99 99  == **Fancy Forum Answers** ==
100 100  
101 101  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:
102 102  
103 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
104 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
105 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
106 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
107 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
108 108  
44 +== **Key Takeaways** ==
109 109  
110 -== **Key takeaways** ==
111 -
112 112  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:
113 113  
114 114  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -115,10 +115,9 @@
115 115  * If you have feedback or ideas for us, talk to the Platypus
116 116  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
117 117  * Clear your browser cache (Ctrl + Shift + Del)
118 -* Check out the release notes [here]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
119 119  * Start thinking about how the license tracker can aid your development
120 120  * Start thinking about major, minor, and patch
121 -* 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,11 @@
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  
129 -~*~* Indicates a next-generation-architecture only feature.
130 -{{/info}})))((({{toc/}}))){{/container}}
62 +{{/info}}
63 +)))
64 +
65 +(((
66 +{{toc/}}
67 +)))
131 131  {{/container}}
69 +{{/container}}