Changes for page 208 - Controlled State

Last modified by CarlijnKokkeler on 2024/04/18 13:10

From 56.1 to 55.1 From 269.1 to 268.1

From version 268.1

edited by CarlijnKokkeler
on 2023/11/20 16:21

Change comment: There is no comment for this version

To version 56.1

edited by Erik Bakker
on 2022/12/06 14:58

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--208 - Controlled State
++189 - Private Eye

Author

@@ -1,1 +1,1 @@
--XWiki.CarlijnKokkeler
++XWiki.ebakker

Content

@@ -2,68 +2,79 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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. 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.
++**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.
--{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
++== **Private Store** ==
++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).
--== **State Generation - Manage overview~*~*** ==
++{{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}}
--The following page has been added:
--* State generation statistics: Contains the statistics for state generation implementation in your model. The navigation to this page can be found under Manage->Monitoring page. This page provides you with graphs that explain the retrieve latency, cache size, and successful and failed retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that have the add-on license for state generation.
++== **3rd generation runtime bolstering** ==
--[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.jpg]]
++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.
--== **Feedback Items** ==
++//__SOAP and REST web services migration including splitting them__//
++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.
--//__Improved information on removing a release version__//
--Users are now informed with more comprehensive information about why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) fails. Users are now informed in which environment(s) and in which runtime(s) that the release version under deletion is still running.
++//__Changing SSL settings for 3rd generation runtime models works__//
++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.
--//__Wider and expandable fields for XPath expressions__//
--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.
++//__Improved migration for JMS flows__//
++This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
--//__Old images cleanup mechanism__//
--We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz from taking resources from the customer’s machine due to the unattended old images.
++{{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}}
--//__Consistent toggle switches__//
--In this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
++//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
++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.
--//__Consistent triggers naming__//
--We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, on the Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so that we have a consistent naming.
--
--//__Search phrase__//~*~*
--We are now enabling users to search for log entries and error messages in the next-generation architecture models based on phrases containing two or more words, instead of only one word or the full sentence. This also means that the user can search for entries with distances of 2 or incomplete search phrases (e.g., “startin engine” to look for “starting servlet engine”).
--
--//__Improved image building performance__//
--We have implemented an improvement on the preparation step of the release at the beginning of the deployment, which leads to a faster deployment process.
--
--//__Default "errorChannel" on next-generation architecture migration__//~*~*
--During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
--
--== **Bug Fixes** ==
++//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
++We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
--//__Incorrect deployed containers__//
--A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones were deployed. This problem was caused by auto-healing that was triggered during a new deployment.
++== **Feedback items ** ==
--//__Log messages in next-generation architecture models__//~*~*
--We have implemented an improvement in our infra components that is intended to reduce the occurrence of log messages failing to be sent in the next-generation architecture models.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Random stuck in deployment plan execution__//
--We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
++//__Improved naming convention on Store related pages__//
++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.
++//__Press "Enter" to search on multiple pages__//
++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.
++
++* Deploy → Deployment Plan
++* Deploy → Properties → History
++* Deploy → User Management → Roles
++* Manage → Error Messages → Error Messages
++* Manage → Error Messages → Flows with Error Messages
++* Manage → Error Messages → Exceptions of Error Messages
++* Manage → Log Entries
++* Manage → Alerts
++* Manage → Triggers
++* Manage → Tags – Cant find (only Gen2)
++* Manage → Notifications
++* Manage → Notification Settings
++* Manage → Data Usage → History
++* Manage → Code mappings → All tabs
++
++== **Bug fixes ** ==
++
++//__Loading problems of Deployment plan execution overview__//
++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.
++
  == **Fancy Forum Answers** ==
  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:
--* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
--* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
++* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
++* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
++* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
  == **Key takeaways** ==
--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:
++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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
--* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
++* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
@@ -74,6 +74,8 @@
  Let's stay in touch and till next time!
  {{info}}
--~*~* Indicates a next-generation-architecture only feature.
++~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
++
++~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 208 - Controlled State

Summary

Details

Navigation