Changes for page 208 - Controlled State
Last modified by CarlijnKokkeler on 2024/04/18 13:10
From version 253.1
edited by dfirdausy
on 2023/11/07 11:54
on 2023/11/07 11:54
Change comment:
There is no comment for this version
To version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
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 - 208 -Controlled State1 +189 - Private Eye - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -2,69 +2,79 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavedonemuchwork toimprove the functionalityof ourstategenerationsolutionsothatyoucanhave a betteroverview ofitsimplementationin yourenvironment.Thisoverview coversa visibility towards thestatisticsforRetrieveLatency,CacheSize, SuccessfulandFailedRetrieves. Nextto themonitoringforthestategenerationimplementationin yourmodel,severalfeedback itemsrevolving arounduser interfacing componentsinour platformthatcanimprovetheuser experiencearealso released.Lastly, someperformanceimprovements and bugfixeshavealsobeenimplemented.5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}} 7 +== **Private Store** == 8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 8 8 9 - == **StateGeneration~*~***==10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 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. 12 +== **3rd generation runtime bolstering** == 14 14 15 - {{info}}Thegraphsareconfiguredwith thesamebehaviourasgraphsin the otherstatisticspages,meaningthatyoucanalsochangethe timerange,zoominzoom outto thetimeframe, etc.{{/info}}14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 16 16 17 -== **Feedback Items** == 16 +//__SOAP and REST web services migration including splitting them__// 17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal. 18 18 19 -//__ ImprovedInformationonRemoving a ReleaseVersion__//20 - Usersare nowinformed witha more comprehensiveinformation of why removingarelease version thatis still active onallenvironments(i.e., Test,Acceptance,andProduction) isfailed. Usersare now informedinwhich environment(s)thatrunsinwhich runtime(s)that the releaseversionunderdeletionis stillrunning.19 +//__Changing SSL settings for 3rd generation runtime models works__// 20 +As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime. 21 21 22 -//__ WiderandExpandableFieldsforXPathExpressions__//23 - Input fieldsforXPathexpressionslocatedinthe Createphaseare nowmade widerandalsocapableofexpandingwhenthe expressionregisteredbytheuseristoolong.22 +//__Improved migration for JMS flows__// 23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 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. 25 +{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 27 27 28 -//__ ConsistentToggleSwitches__//29 - Weare nowimplementingeMagizDesignSystemmodulein ourplatformand,inthis release,we haveupdatedallinstancesofthetoggleswitchto havea moreconsistent performance andlook & feelthroughoutthe platform.27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 +As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 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”). 33 - 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. 36 - 37 -//__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. 39 - 40 -== **Bug Fixes** == 30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 41 41 42 -//__Incorrect Deployed Containers__// 43 -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. 33 +== **Feedback items ** == 44 44 45 -//__Log Messages in Gen3 Models__// 46 -We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in Gen3 models. 35 +We have also solved other feedback items besides the flow designer's critical updates. 47 47 48 -//__ RandomStuckinDeploymentPlanExecution__//49 -We a ddressed anissuewhere theexecutionof deploymentplanwouldoccasionallybecomestuckorhaltedunexpectedly.37 +//__Improved naming convention on Store related pages__// 38 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 50 50 40 +//__Press "Enter" to search on multiple pages__// 41 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 42 + 43 +* Deploy → Deployment Plan 44 +* Deploy → Properties → History 45 +* Deploy → User Management → Roles 46 +* Manage → Error Messages → Error Messages 47 +* Manage → Error Messages → Flows with Error Messages 48 +* Manage → Error Messages → Exceptions of Error Messages 49 +* Manage → Log Entries 50 +* Manage → Alerts 51 +* Manage → Triggers 52 +* Manage → Tags – Cant find (only Gen2) 53 +* Manage → Notifications 54 +* Manage → Notification Settings 55 +* Manage → Data Usage → History 56 +* Manage → Code mappings → All tabs 57 + 58 +== **Bug fixes ** == 59 + 60 +//__Loading problems of Deployment plan execution overview__// 61 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 62 + 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]] 56 -* [[Existing integration sends message to onramp but they dissapear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]] 57 -* [[Keystore not valid in runtime generation 3>>https://my.emagiz.com/p/question/172825635703261540||target="blank"]] 58 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 67 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 68 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 69 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 59 59 60 - 61 61 == **Key takeaways** == 62 62 63 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:73 +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: 64 64 65 65 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 66 66 * If you have feedback or ideas for us, talk to the Platypus 67 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 77 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 68 68 * Clear your browser cache (Ctrl + Shift + Del) 69 69 * Check out the release notes [here] 70 70 * Start thinking about how the license tracker can aid your development ... ... @@ -77,6 +77,6 @@ 77 77 {{info}} 78 78 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 79 79 80 -~*~* Indicates a next-generation-architecture only feature.90 +~*~* Indicates a GEN3-only feature. 81 81 {{/info}})))((({{toc/}}))){{/container}} 82 82 {{/container}}