Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From 96.1 to 97.1 From 262.1 to 263.1

From version 97.1

edited by Erik Bakker
on 2023/04/13 08:44

Change comment: There is no comment for this version

To version 262.1

edited by Danniar Firdausy
on 2023/11/08 13:37

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 @@
--195 - Easter Party
++208 - Controlled State

Author

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

Content

@@ -2,91 +2,68 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
++**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.
--== **Release properties** ==**
++{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
--== **API improvements** ==
++== **State Generation - Manage overview** ==
--//__Improved auto-generated error handling__//
--When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
++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.
--//__Switch default message format__//
--We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
++[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
--//__Re-using elements in gateway message__//
--This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
++== **Feedback Items** ==
--//__Improved naming of API operations when adding integrations to Create__//
--Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
++//__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.
--== **3rd generation improvements** ==
++//__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.
--//__Update of the static alerting engine__//
--In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
++//__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.
--//__Add "Data pipeline" functionality__//
--This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
++//__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.
--//__Fix related to the debugger__//
--This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
++//__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 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** ==
--{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
++//__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.
--//__Improved migration process__//
--This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
++//__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.
--//__Deployment plan change__//
--In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
++//__Random stuck in deployment plan execution__//
++We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
--{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
--
--== **Feedback items ** ==
--
--//__License Tracker improvements__//
--With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
--
--//__Ability to view the message definition for a topic__//
--Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
--
--//__Restricted access for uploading custom certificates to endpoints__//
--To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
--
--== **Bug fixes ** ==
--
--//__Improved deletion behavior for enumerations__//
--To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
--
--//__Prevent "async" api operations__//
--With this release, we have removed the ability to select the "async" option when the default message format is API Management.
--
--//__Importing a response definition broke the request definition__//
--Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
--
--//__Removing a flow does not update the API "all-entry" anymore__//
--When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
--
--//__Stop deployment plan when a property is missing__//
--Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
--
--//__Cap stack trace of error messages and log entries__//
--To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
--
  == **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:
--* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
--* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
--* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
++* [[(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"]]
  == **Key takeaways** ==
--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:
++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:
  * 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
@@ -99,6 +99,6 @@
  {{info}}
  ~* 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.
++~*~* Indicates a next-generation-architecture only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 208 - Controlled State

Summary

Details

Navigation