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 - 185-Todetermine1 +208 - Controlled State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.dfirdausy - Content
-
... ... @@ -2,64 +2,68 @@ 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 been hardatworkbolsteringourofferingconcerningtheupcomingrollout ofour newarchitecture stack.Next to thatbigdevelopment,wehave finishedourworkontheFlow Designerwhichisthemajorpartofthisrelease. Pleasetake amomenttoreadthebelowcarefully andworkwiththenewflow designer assoonaspossibletofamiliarizeyourselfwiththis one.5 +**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can have a better overview of its implementation in your environment. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented. 6 6 7 - ==**FlowDesignerV3**==7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}} 8 8 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. 9 +== **State Generation~*~*** == 13 13 14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 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. 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. 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}} 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. 17 +== **Feedback Items** == 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. 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. 21 + 22 +//__Wider and Expandable Fields for XPath Expressions__// 23 +Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long. 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. 27 + 28 +//__Consistent Toggle Switches__// 29 +We are now implementing eMagiz Design System module in our platform and, in this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform. 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”). 31 31 32 - ===**Userinteraction changes** ===33 - Therearesomesmallchangestoconsidercomparedto theoldflowdesigner.Pleasetakeamomenttoread these:34 +//__Improved Image Building Performance__// 35 +We have implemented an improvement on the preparing step of the release at the begining of the deployment, which leads to a faster deployment process. 34 34 35 - * Multipleselect. Thisoption is still available, but youhaveto clickthe shift buttonwhiledrawingtherectanglethat holds the objects to select36 - * Live preview. When movingcomponentsaround,alivepreviewofthe flowis displayedsothat alignmentbecomes easier37 +//__Default "errorChannel" on Gen3 Migration__// 38 +During a migration of a model to Gen3, we have introduced a check now for flows that did not have custom error handling to be set their error channel to "errorChannel" after the migration if the custom error handling is set to false. 37 37 40 +There are cases where flows do not have a custom error handling. In this release, we During Gen3 Migration of a model. 38 38 39 -== ** Feedbackitems** ==42 +== **Bug Fixes** == 40 40 41 -We have also solved other feedback items besides the key updates around functionality. 44 +//__Wrong Deployed Containers__// 45 +A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones instead are deployed. This problem was caused by auto-healing that triggered during a new deployment. 42 42 43 -//__ Set runtimefieldas first selectedfield onpropertylevel__//44 - With this change,theruntimeisthefirstfieldselectedwhencopying a property.Thisway it is easiertoselectanotherruntimeandpropagatethatproperty tothatruntimeaswell.47 +//__Topic and event-processor names__// 48 +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. 45 45 46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 47 - 48 - 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:52 +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"]] 54 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 55 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 56 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 57 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 55 55 59 + 56 56 == **Key takeaways** == 57 57 58 -Thanks to all thathelp build,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:62 +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: 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 62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 64 * Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development ... ... @@ -66,13 +66,12 @@ 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]] 77 +~* 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 -~*~* Indicates a GEN3-only feature.79 +~*~* Indicates a next-generation-architecture only feature. 77 77 {{/info}})))((({{toc/}}))){{/container}} 78 78 {{/container}}