Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
on 2023/06/20 13:14
Change comment:
There is no comment for this version
To version 242.1
edited by Danniar Firdausy
on 2023/11/06 13:23
on 2023/11/06 13:23
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 -20 0-UnchartedTerritories1 +208 - Controlled State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.dfirdausy - Content
-
... ... @@ -2,60 +2,56 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortunately not quite ready to be released.As a result the output of this release is limited.Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.5 +**Hi there, eMagiz developers!** ... . 6 6 7 - == **Next generation improvements andbugfixes** ==7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}} 8 8 9 -//__Enhanced right-hand view within Deployment Plan context__// 10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 9 +== **State Generation~*~*** == 11 11 12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 11 +//__New Page__// 12 +The following page has been added: 13 +* Aggregator: reverse of the splitter, used to combine multiple messages into a single one. 13 13 14 -//__Improved timeout settings when deploying__// 15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur. 15 +Added support for ... . 16 16 17 -{{info}} Note that this fix is part of a newruntime image for the current-generation runtimes.The release notes of this can be found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}17 +{{info}}The components are ... .{{/info}} 18 18 19 - //__Detailed HTTP Statisticsnow show userinfo in specificadditionalcases__//20 - To solvea bug for a specific client we changed thelogicto show the user info (i.e.first part of the api key) in a specific implementation just as we already do in our standard implementations.19 +== **Metrics Storage Duration** == 20 +We will ... . 21 21 22 - {{info}}Notethat this fix is part of a new runtimeimage for the next-generation runtimes. The release notes of thiscanbe found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}22 +== **Feedback Items** == 23 23 24 -//__Imp rovedloadingspeedof Manage Dashboard__//25 -Th is releaseimprovestheloadingspeedwithwhich allthedashboardsinManagereshowntotheuser.Thiswillenhance theuserxperiencewithintheManagephase.24 +//__Import from store__// 25 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened. 26 26 27 -== **Store Improvements** == 28 - 29 -//__Importing in Design is improved__// 30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 31 - 27 +//__Import from store__// 28 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened. 29 + 32 32 == **Bug Fixes** == 33 33 34 -//__ Deprecatedreminder pop-upmoved__//35 - We haveremovedareminder pop-up on a pending cloud templateas itwas deprecatedandcouldcauseissueswhenusingitincommunicationwithothersystems.32 +//__Topic and event-processor names__// 33 +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. 36 36 37 -//__ Improvedselectionarea in Flow Designer__//38 - Whenworking onalargeflow youcan nowselectspecificareaseasilywhileyouare scrolleddownfurtherdowntheflow.35 +//__Topic and event-processor names__// 36 +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. 39 39 40 -//__Improved Kafka settings__// 41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 42 - 43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 44 - 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 42 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 43 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 44 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 45 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 51 51 47 + 52 52 == **Key takeaways** == 53 53 54 -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:50 +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: 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. 54 +* 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 ... ... @@ -68,6 +68,6 @@ 68 68 {{info}} 69 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]] 70 70 71 -~*~* Indicates a GEN3-only feature.67 +~*~* Indicates a next-generation-architecture only feature. 72 72 {{/info}})))((({{toc/}}))){{/container}} 73 73 {{/container}}