Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
on 2022/10/12 10:29
Change comment:
There is no comment for this version
To version 135.1
edited by Erik Bakker
on 2023/08/01 14:12
on 2023/08/01 14:12
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 - 185-To determine1 +202 - New Equilibrium - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -2,60 +2,74 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavebeenhardat workbolsteringourofferingconcerningtheupcomingrolloutofour new architecturestack.Nexttothatbig development,wehavefinished our workon the Flow Designerwhichsthemajorpartof thisrelease.Pleasetakea momenttoreadthebelowcarefullyandworkwiththenewflowdesigner assoonaspossibleto familiarizeyourselfwiththisone.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 6 7 -==**Flow Designer V3**== 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 8 9 -The new Flow Designerused inCreateis released!This isasignificantimprovementin our iPaaS Portalthatimplements feedback of ourusersand helpstoimprove theoverall experience. Afterseveraliterationsof internalvalidations andtestingsessionswith end-users,wearereleasingthis featuretoall users.Below areomekeynotesthat areimportanttoknowand to consider.10 - 11 - ===**Improvements**===12 - ThenewFlowDesignerimplementsanapproach wherebycomponents can bedragged intothecanvas withoutanyconfigurationsettingchanged.The right handpanelcontainsa new sectioncalled Alerts that helpsusersto remove allalerts from theflowcreated. Suchasmissingconfigurations,channelsorismatches. Allofthesealertsneedtobe resolvedsothat a valid flow canbepushed toDeploy.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. 13 13 14 - [[image:Main.Images.ReleaseBlog.WebHome@184- FlowDesignerreleaseblog 1.png]]15 +{{info}}For more information please check out the following microlearnings: 15 15 16 -Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow. 17 - 18 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]] 19 - 20 -* **Alerts** 21 -In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location. 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"]] 22 22 23 -* **Resources** 24 -In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these. 25 - 26 -* **Support objects** 27 -The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used. 21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 +{{/info}} 28 28 29 -* **Properties** 30 -The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry. 31 - 32 -=== **User interaction changes** === 33 -There are some small changes to consider compared to the old flow designer. Please take a moment to read these: 34 - 35 -* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select 36 -* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier 24 +== ** Manage - Next generation 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 manage graphs as we retrieve and show less fine-grained information when zooming out. 37 37 38 - 39 -== **Feedback items ** == 27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 40 40 41 - Wehavealso solvedother feedbackitemsbesides the key updates around functionality.29 +== **Feedback Items** == 42 42 43 -//__ Setruntimefieldasfirstselectedfieldonproperty level__//44 -With hischange,the runtimeisthefirstfieldselectedwhen copyingaproperty.Thiswayit iseasier toselectanotherruntime andpropagate thatpropertytothatruntime aswell.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. 45 45 46 - [[image:Main.Images.ReleaseBlog.WebHome@184- FlowDesignerreleaseblog 3.png]]47 - 34 +//__Improved auditability on Deploy Architecture__// 35 +To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP). 48 48 37 +//__Test your own exported work__// 38 +We have now made it possible to test your own 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. 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}} 41 + 42 +//__Improved Audit Trail on several places__// 43 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 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 +== **Bug Fixes** == 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. 52 + 53 +//__Improved validation feedback in migrating to the next-generation architecture__// 54 +We have improved the validation feedback when migrating to the next-generation architecture. 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. 58 + 59 +//__Refresh behavior within the deployment plan is fixed__// 60 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 61 + 49 49 == **Fancy Forum Answers** == 50 50 51 -As always, a gentle reminder to a ll 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: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: 52 52 53 -* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]] 54 -* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]] 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"]] 55 55 56 56 == **Key takeaways** == 57 57 58 -Thanks to all that help build ,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:72 +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: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus ... ... @@ -66,12 +66,11 @@ 66 66 * Start thinking about major, minor, and patch 67 67 * Upgrade to the latest build number 68 68 * Keep making great integrations 69 -* Check out the new documentation portal. 70 70 71 71 Let's stay in touch and till next time! 72 72 73 73 {{info}} 74 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 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]] 75 75 76 76 ~*~* Indicates a GEN3-only feature. 77 77 {{/info}})))((({{toc/}}))){{/container}}