Changes for page 202 - New Equilibrium
Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 44.1
edited by Erik Bakker
on 2022/11/08 10:05
on 2022/11/08 10:05
Change comment:
There is no comment for this version
To version 146.1
edited by Carlijn Kokkeler
on 2024/04/18 13:13
on 2024/04/18 13:13
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 - 187-IntegrationSponsor1 +202 - New Equilibrium - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,67 +1,74 @@ 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!** Thisreleasewillreleaseseveralimpactful features and enablerstoourcommunity.Amongothers,thenext phase of theeMagiz Store will becomepublicly available. Thismeansthatyou can now import datamodelsandtransformationon top ofsystem messagesinDesignand acceleratorsin Create.Furthermore, we willlaunchanewBetafunctionalitythroughsomeofourclients,enablingyouto restoreyourflowto apreviousversion.6 +**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 smaller feedback items from our hackathon efforts that are now released to you. 6 6 7 -== ** Store- Next phase** ==8 +== **Release Properties** == 8 8 9 - This release will introducethenextphaseoftheStoreto ourwhole community.With this newfunctionality,youcanmportdatamodel messages(i.e.,CDM,APIGatewayDatamodel,orEventStreamingdatamodel)and transformations.Connectingto standardizedsystemssuchas ExactOnline, MicrosoftGraph,Salesforce,and otherswillbecome even moreaccessible.10 +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 10 11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 12 +* 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 13 +* 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. 14 +* 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. 15 +* 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 12 13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}} 17 +{{info}} 18 +For more information, please check out the following microlearnings: 14 14 15 -== **New eMagiz Mendix Connector** == 20 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 21 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 22 +* [[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 16 17 -This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal. 24 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 25 +{{/info}} 18 18 19 - {{info}}Migratingtheruntimefrom the eMagizportal works thesameas for any other runtime. The migrationpath can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}27 +== ** Manage - Graphs improvements ~*~* ** == 20 20 21 - ==**Flow version restore**~*==29 +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. 22 22 23 - On top of that, wewillalso launchanew Beta featuretothecommunity that allows you to restoreyour flow to a previousversion. This way, you can quickly undochangesmade that were incorrect.31 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 24 24 25 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--flow-version-restore.png]]33 +== **Feedback Items** == 26 26 27 -{{warning}}Note that the following restrictions apply when restoring to a previous version: 28 - * Changes made on definition and transformation level are **not** restored 29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 35 +//__Improved editability when testing in eMagiz without Edit rights in Create__// 36 +Without editing 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 should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description. 32 32 33 -== **Feedback items ** == 38 +//__Improved auditability on Deploy Architecture__// 39 +To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP). 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 41 +//__Test your own exported store content__// 42 +We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store. 36 36 37 -//__Improved help texts Kafka component__// 38 -The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz. 44 +{{info}} 45 +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"]] 46 +{{/info}} 39 39 40 -//__Improved warningmessagewhenMessageredelivery cannot beadequately executed__//41 -We have improvedthewarningyou getwhenyoucannotretrieve themessages waiting toberedelivered. Thishelpsclarify what is going wrongwhenauserseesthis warning.48 +//__Improved comparison of flows in the releases overview__// 49 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns. 42 42 43 -//__See Flow Designer errors on the Create overview__// 44 -To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable. 51 +== **Bug Fixes** == 45 45 46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 53 +//__Improved validation on XPath header enricher__// 54 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component. 47 47 48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 56 +//__Cancel behavior on flow testing property overview fixed__// 57 +We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list. 49 49 50 -== **Bug Fixes** == 59 +//__Cancel behavior on flow fragment level when exporting store content__// 60 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list. 51 51 52 -//__ Update Swagger File whenchangingtheorderofentities ingatewaymessage__//53 - Inour previous release, weimprovedhowtheSwaggerfile isgeneratedwhenchangingtheorder of attributesofyourgatewaymessage. To makethis functionalitywork for entities,we havemadeseveral additionalchanges to theplatformsupporting this.62 +//__Adding numbers on containers in Deploy Architecture__// 63 +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. 54 54 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 60 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 61 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 62 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 69 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 63 63 64 -== **Key takeaways** ==71 +== **Key Takeaways** == 65 65 66 66 Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 67 67 ... ... @@ -69,7 +69,7 @@ 69 69 * If you have feedback or ideas for us, talk to the Platypus 70 70 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 71 71 * Clear your browser cache (Ctrl + Shift + Del) 72 -* Check out the release notes [here] 79 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]] 73 73 * Start thinking about how the license tracker can aid your development 74 74 * Start thinking about major, minor, and patch 75 75 * Upgrade to the latest build number ... ... @@ -80,6 +80,12 @@ 80 80 {{info}} 81 81 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 82 82 83 -~*~* Indicates a GEN3-only feature. 84 -{{/info}})))((({{toc/}}))){{/container}} 90 +~*~* Indicates a next-generation-architecture only feature. 91 +{{/info}} 92 +))) 93 + 94 +((( 95 +{{toc/}} 96 +))) 85 85 {{/container}} 98 +{{/container}}