Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 318.1
edited by Carlijn Kokkeler
on 2023/12/21 14:49
on 2023/12/21 14:49
Change comment:
There is no comment for this version
To version 510.1
edited by Carlijn Kokkeler
on 2024/05/06 14:05
on 2024/05/06 14:05
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 11-LogLuminary1 +220 - Patch Parade - Content
-
... ... @@ -3,75 +3,82 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 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 -== **Overviews and logging** == 9 -//__Runtime overview__// 10 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 8 +== **Feedback Items** == 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 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. 13 13 14 -//__Missing properties overview__// 15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 16 16 17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 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. 18 18 19 -//__Runtime restart or redeploy overview__// 20 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 23 23 24 -//__Missing log entries__// 25 -We improved crash handling so that log messages clearly show when and why a container failed to start. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 26 26 27 -//__ Runtimelogging__//28 - Wefixedabugwhereno newlogmessages werehowingup,evenhoughtheywereproducedbythecontainer.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 - == **FeedbackItems** ==28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 31 31 30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 32 32 33 -//__ Breakingchangespop-up__//34 - Pending changesthathave a high risklevel arenow shownboldinthepopup thatappearsafter clicking'Apply toenvironment'.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. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release- blog-211-breaking-changes.jpg]]36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 37 38 -//__ External recipientsemailaddress__//39 - The overview ofexternalrecipientshas beenupdated. Externalrecipients arecreatedon a modellevel, insteadof comma separated list.Thismeansthat youcan addthemto yourenvironmentdirectly, likeinternal users.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. 40 40 41 -//__ Brokerqueuemetricsdashboards__//42 - Itis nowpossibletoselecttheMQTT brokerinthequeuemetricsdashboards.41 +//__Filter rejection warnings__// 42 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 43 43 44 -//__Runtime image version__// 45 -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. 44 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 46 46 47 - 48 48 == **Bug Fixes** == 47 +//__Annotation styling__// 48 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 49 49 50 -//__Message throughput__// 51 -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. 50 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 52 52 53 -//__ Cloud templateupgradeunjust rollback__//54 -An issue has been fixed where a cloudtemplateupgrade wouldbe rolledback unjustlydue tofailed runtimechecks.52 +//__Manage Explore__// 53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 55 55 56 -//__ Nextgenerationblock__//57 - Applytoenvironmentwillnowbe blockedwhen tryingtodeployGen3runtimesonaGen2model.55 +//__Page refreshing__// 56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 58 58 59 -//__ Deploymentexecutionerror message__//60 - In some caseswhenamachine typestepin thedeploymentplan executionerrors, theportalmay give an error when tryingto display theerrormessage. Thishasbeenfixed by nowshowingageneric error inthedeploymentplan and loggingthefullerrorinheDeployhistory. TheDeploy history will showasummaryof theerrorand show the full error messagein a new pop-up.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. 61 61 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. 63 + 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 + 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: 65 65 66 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 67 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 68 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 69 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 70 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||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"]] 71 71 80 +== **Key Takeaways** == 72 72 73 -== **Key takeaways** == 74 - 75 75 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: 76 76 77 77 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -78,10 +78,9 @@ 78 78 * If you have feedback or ideas for us, talk to the Platypus 79 79 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 80 * Clear your browser cache (Ctrl + Shift + Del) 81 -* Check out the release notes [here] 88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 82 82 * Start thinking about how the license tracker can aid your development 83 83 * Start thinking about major, minor, and patch 84 -* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! ... ... @@ -89,7 +89,6 @@ 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -~*~* Indicates a next-generation-architecture only feature. 93 93 {{/info}} 94 94 ))) 95 95