Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 168.1
edited by CarlijnKokkeler
on 2023/10/11 13:32
Change comment: There is no comment for this version
To version 544.1
edited by CarlijnKokkeler
on 2024/06/03 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +222 - Flee Frustration
Content
... ... @@ -1,103 +1,49 @@
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!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
6 6  
7 -== **Deployment Plan** ==
8 -
9 -//__Improved deployment plan to make the process better and more predictable__//
10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
11 -
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
14 -
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
17 -
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
23 -
24 -//__Performance improvements for loading releases__//
25 -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.
26 -
27 -== **Store Improvements** ==
28 -
29 -//__Message definition elements order__//
30 -We fixed an issue that the order of message definition elements was changed after being imported.
31 -
32 -//__Improting a store item with synchronous message definitions__//
33 -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.
34 -
35 -//__Importing store items containing static copies__//
36 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
37 -
38 -//__Importing Store content__//
39 -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.
40 -
41 41  == **Feedback Items** ==
9 +//__Cron triggers__//
10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
42 42  
43 -//__Alerting manual pause__//
44 -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.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
45 45  
46 -//__Ordering of graphs in Manage__//
47 -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).
14 +//__Design changes__//
15 +If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
48 48  
49 -//__UTC times in Grafana panels__//
50 -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.
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
51 51  
52 -//__Update flow designer version__//
53 -The framework used in the flow designer has been updated to the latest version.
54 -
55 -//__Carwash track TLS versions in logging__//
56 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
57 -
58 -//__Moving channels in the flow designer__//
59 -Moving already attached channels in the flow designer has been made sligthly easier.
60 -
61 -//__Topic sizes description change__//
62 -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.
63 -
64 -//__Password change notification__//
65 -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.
66 -
67 -//__Password comparison__//
68 -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.
69 -
70 -//__Inactive user alerting__//
71 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
72 -
73 -//__Alphabetical sorting on user level in HTTP statistics__//
74 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
75 -
76 -//__SOAP Web services path__//
77 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
78 -
79 79  == **Bug Fixes** ==
20 +//__Trigger activation__//
21 +Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
80 80  
81 -//__Flow designer styling__//
82 -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.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
83 83  
84 -//__Partial search for messages__//
85 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
86 86  
87 -//__Disk usage after cloud template update__//
88 -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.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
89 89  
90 -//__Error handling migration__//
91 -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.
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
92 92  
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
93 93  
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
38 +
94 94  == **Fancy Forum Answers** ==
95 95  
96 96  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:
97 97  
98 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
99 99  
100 -== **Key takeaways** ==
46 +== **Key Takeaways** ==
101 101  
102 102  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:
103 103  
... ... @@ -105,10 +105,9 @@
105 105  * If you have feedback or ideas for us, talk to the Platypus
106 106  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
107 107  * Clear your browser cache (Ctrl + Shift + Del)
108 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
109 109  * Start thinking about how the license tracker can aid your development
110 110  * Start thinking about major, minor, and patch
111 -* Upgrade to the latest build number
112 112  * Keep making great integrations
113 113  
114 114  Let's stay in touch and till next time!
... ... @@ -116,6 +116,11 @@
116 116  {{info}}
117 117  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
118 118  
119 -~*~* Indicates a next-generation-architecture only feature.
120 -{{/info}})))((({{toc/}}))){{/container}}
64 +{{/info}}
65 +)))
66 +
67 +(((
68 +{{toc/}}
69 +)))
121 121  {{/container}}
71 +{{/container}}