Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 543.1
edited by Carlijn Kokkeler
on 2024/06/03 13:23
on 2024/06/03 13:23
Change comment:
There is no comment for this version
To version 499.1
edited by Carlijn Kokkeler
on 2024/05/06 13:04
on 2024/05/06 13:04
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 -22 2-FleeFrustration1 +220 - Patch Parade - Content
-
... ... @@ -3,45 +3,51 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 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 read about the details and the rest of our bug fixes!6 +**Hi there, eMagiz developers!** 7 7 8 8 == **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. 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.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 -//__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. 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 16 16 17 -[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.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 -== **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. 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 22 22 23 -//__ Multipleusersdeploying__//24 - Usersareblockedfrom deployingatthesameme on thesame environmenton the [[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@release-22 2-users-deploying.png]]23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 27 27 28 -//__ Invalid memoryconfigurations__//29 - Wehaveimprovedmachine healthcalculationsto preventthecreationof amachinewithinvalidmemoryconfigurations.25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 30 30 31 -//__Property value synchronization__// 32 -Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 33 33 34 -//__ JMSnumber__//35 - The numberon theJMScontainercorrectly displaystheamountofqueuespresentinDesign.30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 36 36 37 -[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 33 +== **Bug Fixes** == 34 +//__Annotation styling__// 35 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 38 38 37 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 38 + 39 +//__Filter rejection warnings__// 40 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 41 + 42 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 43 + 39 39 == **Fancy Forum Answers** == 40 40 41 41 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: 42 42 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"]] 48 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 49 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 50 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 45 45 46 46 == **Key Takeaways** == 47 47 ... ... @@ -51,7 +51,7 @@ 51 51 * If you have feedback or ideas for us, talk to the Platypus 52 52 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 53 53 * Clear your browser cache (Ctrl + Shift + Del) 54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.2 21 -SwiftShift.WebHome||target="blank"]]60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 55 55 * Start thinking about how the license tracker can aid your development 56 56 * Start thinking about major, minor, and patch 57 57 * Keep making great integrations