Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 332.1
edited by Carlijn Kokkeler
on 2024/01/03 10:01
Change comment: There is no comment for this version
To version 511.1
edited by Carlijn Kokkeler
on 2024/05/06 14:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +220 - Patch Parade
Content
... ... @@ -3,70 +3,81 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 +**Hi there, eMagiz developers!** In the last few weeks, we worked hard on solving several feedback items and bug fixes. On top of that, we have release a new runtime image LINK that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Without further ado, let us look at our improvements and bug fixes below.
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
8 +== **Feedback Items** ==
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container.
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
14 14  
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
17 17  
18 -== **Overviews** ==
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
19 19  
20 -//__Runtime overview__//
21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
24 24  
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
29 29  
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
34 34  
35 -== **Feedback Items** ==
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
36 36  
37 -//__Breaking changes pop-up__//
38 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
38 +//__JMS header handling__//
39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released.
41 41  
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
41 +== **Bug Fixes** ==
42 +//__Annotation styling__//
43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
44 44  
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
47 47  
48 -//__Runtime image version__//
49 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
47 +//__Filter rejection warnings__//
48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
50 50  
50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
51 51  
52 -== **Bug Fixes** ==
52 +//__Manage Explore__//
53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
53 53  
54 -//__Message throughput__//
55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
55 +//__Page refreshing__//
56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
56 56  
57 -//__Cloud template upgrade incorrect rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
58 +//__Message redelivery__//
59 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
59 59  
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
61 +//__Deployment plan__//
62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
62 62  
64 +//__Overview pages__//
65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
66 +
67 +//__Memory check__//
68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
69 +
70 +//__Copy password__//
71 +The copy to clipboard button now copies the actual value of passwords instead of the masked value of them.
72 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
77 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
78 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
68 68  
69 -== **Key takeaways** ==
80 +== **Key Takeaways** ==
70 70  
71 71  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:
72 72  
... ... @@ -74,7 +74,7 @@
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 75  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 -* Check out the release notes [here]
88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 80  * Keep making great integrations