Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 133.1
edited by Erik Bakker
on 2023/08/01 14:11
on 2023/08/01 14:11
Change comment:
There is no comment for this version
To version 508.1
edited by CarlijnKokkeler
on 2024/05/06 13:44
on 2024/05/06 13:44
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 02 -NewEquilibrium1 +220 - Patch Parade - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,84 +1,93 @@ 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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Release Properties** == 8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are: 8 +== **Feedback Items** == 9 9 10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 -* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in. 12 -* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers. 13 -* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment. 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 - {{info}}Formoreinformation pleasecheckout thefollowingmicrolearnings:13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 16 16 17 -* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 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. 20 20 21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 -{{/info}} 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 23 23 24 - == ** Manage- Next generation graphsimprovements** ==25 - As of this release, we will create acondensedviewof your metricswhen zoomingoutin theManagephase graphs. This will significantly improve theperformance ofthemanage graphsas weretrieveandshowlessfine-grainedinformation when zooming out.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@ 202-release-blog--manage-graphs-zoomed-out.png]]23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 28 28 29 -== **Feedback Items** == 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 -//__Improved editability when testing in eMagiz wihout Edit rights in Create__// 32 -Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 33 33 34 -//__ Improvedauditability on Deploy Architecture__//35 - To improve the audtiabilityonDeployArchitecturewe nowalsolog when someonewithAdminrightschangesspecific functionsonthislevel(i.e.Fixed IP).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 -//__ Testyour ownexported work__//38 -W ehave nowmadeitpossible totestyourownexported workto theStorebeforeitgets approved.This willincreasethequality ofstoreitemswehave,andourpartners,haveon offerwithin thestore.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. 39 39 40 - {{info}}In case the concept of the store is new for you please check out this[[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 41 41 42 -//__ ImprovedAudit Trail on severalplaces__//43 - In several placesinthe portal,wehaveimprovedthe audittrailto specifybetterwhochangedwhat atwhichpointin time.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. 44 44 45 -//__Removed the erroneous alert on message mapping when having a passthrough API__// 46 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 47 - 48 48 == **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. 49 49 50 -//__Avoid clicking on other components while deleting another__// 51 -To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 52 52 53 -//__ Improved validation feedback in migratingto thenext-generation architecture__//54 - Wehave improvedthevalidationfeedbackwhenmigratingtothenext-generation architecture.47 +//__Filter rejection warnings__// 48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 55 55 56 -//__Make sure that user credentials can be viewed with view rights__// 57 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights. 50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 58 58 59 -//__ Refresh behavior withinthedeployment plan is fixed__//60 - Thisreleasechangestherefreshbehavior within thedeploymentplanto show, oncemore,the "to beinstalled" flowsbeforetheuserpressesExecute.52 +//__Manage Explore__// 53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 61 61 55 +//__Page refreshing__// 56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 57 + 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. 60 + 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 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 67 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 68 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||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"]] 69 69 70 -== **Key takeaways** ==80 +== **Key Takeaways** == 71 71 72 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:82 +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: 73 73 74 74 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 * If you have feedback or ideas for us, talk to the Platypus 76 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 86 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 77 77 * Clear your browser cache (Ctrl + Shift + Del) 78 -* Check out the release notes [here] 88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 79 79 * Start thinking about how the license tracker can aid your development 80 80 * Start thinking about major, minor, and patch 81 -* Upgrade to the latest build number 82 82 * Keep making great integrations 83 83 84 84 Let's stay in touch and till next time! ... ... @@ -86,6 +86,11 @@ 86 86 {{info}} 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 -~*~* Indicates a GEN3-only feature. 90 -{{/info}})))((({{toc/}}))){{/container}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 91 91 {{/container}} 105 +{{/container}}