Changes for page 208 - Controlled State
Last modified by CarlijnKokkeler on 2024/04/18 13:10
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 208 -ControlledState1 +185 - To determine - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -2,60 +2,64 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have donemuch worktoimprovethefunctionalityof ourstategenerationsolutionsothatyoucanhave a betteroverviewof itsimplementationin yourenvironment.This overviewcoversavisibilitytowardsthe statisticsfor RetrieveLatency,CacheSize,Successful and FailedRetrieves.Nextto themonitoringforthestategenerationimplementationinyourmodel, several feedback itemsrevolvingaround userinterfacingcomponentsin our platformthatcanimprovetheuserexperienceare alsoreleased.Lastly,some performanceimprovementsandbugfixes havealsobeenimplemented.5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one. 6 6 7 - {{warning}}State generation functionality isonlyaccessible for models with an add-on stategenerationlicense.{{/warning}}7 +==**Flow Designer V3**== 8 8 9 -== **State Generation~*~*** == 9 +The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider. 10 + 11 +=== **Improvements** === 12 +The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy. 10 10 11 -//__New Page__// 12 -The following page has been added: 13 -* State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. This page provides you with graphs that explains the Retrieve Latency, Cache Size, Successful and Failed Retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that has the add-on license for state generation. 14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 14 14 15 -{{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}} 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. 16 16 17 -== **Feedback Items** == 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. 18 18 19 -//__Improved Information on Removing a Release Version__// 20 -Users are now informed with a more comprehensive information of why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) is failed. Users are now informed in which environment(s) that runs in which runtime(s) that the release version under deletion is still running. 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 21 21 22 - //__WiderandExpandable Fields for XPath Expressions__//23 - Inputfields for XPath expressions locatedintheCreate phase are nowmade wider and alsocapableof expanding when the expression registered by the user is too long.38 + 39 +== **Feedback items ** == 24 24 25 -//__Old Images Cleanup Mechanism__// 26 -We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz to take resources of the customer’s machine due to the unattended old images. 41 +We have also solved other feedback items besides the key updates around functionality. 27 27 28 -//__ ConsistentToggleSwitches__//29 -W earenow implementingeMagizDesignSystem module inourplatformand,inthisrelease,we updatedall instancesofthe toggleswitchtohave amoreconsistentperformance andlook & feel.43 +//__Set runtime field as first selected field on property level__// 44 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 30 30 31 -//__Search Phrase__// 32 -We are now enabling users to search for log entries and error messages based on phrases containing two or more words, instead of only one word or the full sentence. This also means that user can search for entries with distances of 2 or incomplete search phrase (e.g., “startin engine” to look for “starting servlet engine”). 46 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 33 33 34 -== **Bug Fixes** == 35 35 36 -//__Topic and event-processor names__// 37 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable. 38 - 39 -//__Topic and event-processor names__// 40 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable. 41 - 42 42 == **Fancy Forum Answers** == 43 43 44 -As always, this isa 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:51 +As always, a gentle reminder to all 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: 45 45 46 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 47 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 48 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 49 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 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"]] 50 50 51 - 52 52 == **Key takeaways** == 53 53 54 -Thanks to all whohelpedbuildandthose who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 60 * Check out the release notes [here] 61 61 * Start thinking about how the license tracker can aid your development ... ... @@ -62,12 +62,13 @@ 62 62 * Start thinking about major, minor, and patch 63 63 * Upgrade to the latest build number 64 64 * Keep making great integrations 69 +* Check out the new documentation portal. 65 65 66 66 Let's stay in touch and till next time! 67 67 68 68 {{info}} 69 -~* Indicates a Beta feature. If you would like to get access to this beta feature ,please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]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]] 70 70 71 -~*~* Indicates a next-generation-architecture only feature.76 +~*~* Indicates a GEN3-only feature. 72 72 {{/info}})))((({{toc/}}))){{/container}} 73 73 {{/container}}