Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 142.1
edited by Erik Bakker
on 2023/08/07 09:55
on 2023/08/07 09:55
Change comment:
There is no comment for this version
To version 411.1
edited by Erik Bakker
on 2024/03/11 14:39
on 2024/03/11 14:39
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 02-NewEquilibrium1 +216 - Hack Heaven - Content
-
... ... @@ -1,79 +1,99 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 + 6 +**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes. 4 4 5 - **Hithere, eMagiz developers!**Inthe last few weeks, we have crossed our t's and dotted our i's ontherelease properties functionalitythat will impact the day-to-daylifeof every user working within the platform.The focus of the release blog will consequentlyalso be on this subject.On top of that, wehave several smaller feedback items from our hackathonefforts that are now releasedto you.8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** == 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, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are: 10 +Placeholder for info from Bas 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. As a result, you don't have to type them twice when working on an integration. 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 an entirely new release in Test and promote it to the Production environment. 12 +{{info}}Text{{/info}} 14 14 15 - {{info}}Formore information, pleasecheck out thefollowingmicrolearnings:14 +== **Announcement - Spring 6** == 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"]] 16 +Placeholder for info from Jelle 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 +{{warning}}Text{{/warning}} 23 23 24 -== ** Manage - Graphs improvements ~*~* ** == 25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out. 20 +== ** Updated release functionality - Infra flow selection** == 26 26 27 - [[image:Main.Images.ReleaseBlog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]22 +This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level. 28 28 24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 25 + 26 +When you are in edit mode you can select a new version via the right-click option as you were used to for other flows. 27 + 28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 29 + 30 +On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release. 31 + 32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 33 + 34 +== ** Updated deploy functionality on-premise - Multiple environments selection** == 35 + 36 +{{warning}}The following is only applicable under the following conditions: 37 + * Windows 2022 server 38 + * Atleast one port opened (as a consequence of a hosted web service){{/warning}} 39 + 40 +When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine. 41 + 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 43 + 29 29 == **Feedback Items** == 45 +//__Easier component selection in flow designer__// 46 +The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier. 30 30 31 -//__Improved editability when testing in eMagiz withoutEditrightsinCreate__//32 - WithouteditingrightsintheCreatephase,you couldalreadydoa lotonthelevelofflowtestsineMagiz.However,thereweresomeoversights weshould havenoticedduringtheimplementation.Thesehave beenfixed,allowingthosewithout editrightstochange the testcase'sname anddescription.48 +//__Improved handling of optionality in JSON on lists__// 49 +Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired. 33 33 34 -//__ ImprovedauditabilityonDeploy Architecture__//35 -To i mprove theaudibilityof DeployArchitecture,we now also logwhensomeonewithAdmin rights changesspecific functionson thislevel (i.e., Fixed IP).51 +//__Loading bar when searching for log entries__// 52 +To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search. 36 36 37 -//__ Testyourown exported storecontent__//38 - We have nowallowedtesting ofyour exportedworktothe storebeforeitgetsapproved.Thiswillincreasethequalityofstoreitems we have,andourpartners have on offerwithin the store.54 +//__Improved feedback when deleting elements from Capture__// 55 +To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes. 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}} 57 +//__Enhanced filter options in Manage__// 58 +With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places. 41 41 42 -//__ Improvedcomparisonofflowsin thereleases overview__//43 - Wehave nowmadeitpossibletoseethedifferencesintheflow versionsbetweenthetwo releasesfor allthreepatterns.60 +//__Copy property names from Create__// 61 +This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying. 44 44 63 + 45 45 == **Bug Fixes** == 65 +//__Queue name validation__// 66 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer. 46 46 47 -//__Improved validation on XPath header enricher__// 48 -To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component. 68 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 49 49 50 -//__ Cancelbehavioronflow testing property overview fixed__//51 - We haveensuredthatwhenyou pressCancelwheneditinga property neededinaflow test,thepropertyplaceholderwillnolongerdisappear fromthelist.70 +//__Removal of onramp__// 71 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase. 52 52 53 -//__ Cancel behavioron flow fragment level when exporting store content__//54 - Wehaveensuredthat whenyoupressCancel whenexportinga flow fragment,theflow fragmentwillnolongerdisappearfromthelist.73 +//__eMagiz login__// 74 +In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field. 55 55 56 -//__Adding numbers on containers in Deploy Architecture__// 57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release. 58 - 59 59 == **Fancy Forum Answers** == 60 60 61 61 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: 62 62 63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 80 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 81 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 82 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 83 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 84 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 64 64 65 -== **Key takeaways** ==86 +== **Key Takeaways** == 66 66 67 -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:88 +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: 68 68 69 69 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 * If you have feedback or ideas for us, talk to the Platypus 71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 92 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 72 * Clear your browser cache (Ctrl + Shift + Del) 73 73 * Check out the release notes [here] 74 74 * Start thinking about how the license tracker can aid your development 75 75 * Start thinking about major, minor, and patch 76 -* Upgrade to the latest build number 77 77 * Keep making great integrations 78 78 79 79 Let's stay in touch and till next time! ... ... @@ -81,6 +81,11 @@ 81 81 {{info}} 82 82 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 83 83 84 -~*~* Indicates a next-generation-architecture only feature. 85 -{{/info}})))((({{toc/}}))){{/container}} 104 +{{/info}} 105 +))) 106 + 107 +((( 108 +{{toc/}} 109 +))) 86 86 {{/container}} 111 +{{/container}}