Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 161.1
edited by Carlijn Kokkeler
on 2023/10/11 09:30
Change comment: There is no comment for this version
To version 372.1
edited by Carlijn Kokkeler
on 2024/01/31 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +213 - Joyful Journeys
Content
... ... @@ -1,79 +1,83 @@
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!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
6 6  
7 -== **Deployment Plan** ==
8 +== **Pop-up Improvements** ==
8 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.
10 +//__Property releases__//
11 +When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
15 +//__Runtime deletion__//
16 +When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
18 +//__Wiretap & debug error messages__//
19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
20 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.
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
23 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.
24 +== **Formatting & Alignments** ==
26 26  
27 -== **Store Improvements** ==
26 +//__Input fields__//
27 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
28 28  
29 -//__Message definition elements order__//
30 -We fixed an issue that the orders of message definition’s elements were changed after they were imported.
29 +//__UI improvements__//
30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
31 31  
32 -//__Message definition elements order__//
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.
32 +//__Component changes reversion__//
33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
34 34  
35 -== **Feedback Items** ==
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
36 36  
37 -//__Alerting manual pause__//
38 -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.
38 +//__Queue browser timestamps__//
39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
39 39  
40 -//__Ordering of graphs in Manage__//
41 -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).
41 +//__Addition and deletion of internal recipients__//
42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
42 42  
43 -//__UTC times in Grafana panels__//
44 -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.
44 +== **Feedback Items** ==
45 45  
46 -//__Update flow designer version__//
47 -The framework used in the flow designer has been updated to the latest version.
46 +//__Update flows__//
47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors.
48 48  
49 -//__Carwash track TLS versions in logging__//
50 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
49 +//__Q&A forum search__//
50 +The option to search by pressing the Enter key has been added to the Q&A forum.
51 51  
52 -//__Moving channels in the flow designer__//
53 -Moving already attached channels in the flow designer has been made sligthly easier.
52 +//__Memory settings__//
53 +It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
54 54  
55 -//__Topic sizes description change__//
56 -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.
55 +//__Runtime validation__//
56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
57 57  
58 -//__Password change notification__//
59 -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.
58 +//__Runtime overview image versions__//
59 +Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
60 60  
61 -//__Password comparison__//
62 -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.
61 +== **Bug Fixes** ==
63 63  
63 +//__Removal of onramp__//
64 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
64 64  
65 -== **Bug Fixes** ==
66 +//__Runtime statistics details__//
67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
66 66  
67 -//__Flow designer styling__//
68 -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.
69 +//__Deployment prechecks__//
70 +During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
69 69  
70 70  == **Fancy Forum Answers** ==
71 71  
72 72  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:
73 73  
74 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
76 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
77 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
78 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
75 75  
76 -== **Key takeaways** ==
80 +== **Key Takeaways** ==
77 77  
78 78  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:
79 79  
... ... @@ -84,7 +84,6 @@
84 84  * Check out the release notes [here]
85 85  * Start thinking about how the license tracker can aid your development
86 86  * Start thinking about major, minor, and patch
87 -* Upgrade to the latest build number
88 88  * Keep making great integrations
89 89  
90 90  Let's stay in touch and till next time!
... ... @@ -92,6 +92,11 @@
92 92  {{info}}
93 93  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94 94  
95 -~*~* Indicates a next-generation-architecture only feature.
96 -{{/info}})))((({{toc/}}))){{/container}}
98 +{{/info}}
99 +)))
100 +
101 +(((
102 +{{toc/}}
103 +)))
97 97  {{/container}}
105 +{{/container}}