Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 111.1
edited by Erik Bakker
on 2023/05/09 12:45
Change comment: There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +189 - Private Eye
Content
... ... @@ -2,69 +2,73 @@
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 work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
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 -== **Event streaming alerting** ==
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 -With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
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 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
12 +== **3rd generation runtime bolstering** ==
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
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. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
19 +//__Changing SSL settings for 3rd generation runtime models works__//
20 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
25 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
22 22  
23 -For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
24 24  
25 -== **3rd generation improvements** ==
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.
26 26  
27 -//__Event Streaming statistics completion__//
28 -In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
33 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
29 29  
30 -//__Deployments on next generation architecture__//
31 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
36 +//__Added "Reset" functionality__//
37 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
32 32  
33 -//__Clean queues option__//
34 -This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
35 -
36 36  == **Feedback items ** ==
37 37  
38 -//__On-premise containers are started upon slot wakeup__//
39 -With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
41 +We have also solved other feedback items besides the flow designer's critical updates.
40 40  
41 -//__Resource path is shown to the user__//
42 -You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
43 +//__Improved naming convention on Store related pages__//
44 +We have improved various display names using the merge functionality within our store offering.
43 43  
44 -//__Flow designer improvements__//
45 -With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
46 +//__Update security protocols for our internal architecture__//
47 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
46 46  
47 -//__Improved capabilities of a company contact__//
48 -With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
49 +//__Improved read-only description for "if exists" constructions in Transformations__//
50 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
49 49  
52 +
50 50  == **Bug fixes ** ==
51 51  
52 -//__Optional API parameters are handled correctly__//
53 -Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
55 +//__Decent validation feedback when not filling in the property value__//
56 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
54 54  
55 -//__Without CDM rights nothing related to any data model can be edited anymore__//
56 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
58 +//__Incorrect resource locations__//
59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
57 57  
58 -//__Improved sorting of Design and Deploy archticture__//
59 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
61 +//__Apply to environment in User Management performance improvement__//
62 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
60 60  
61 61  == **Fancy Forum Answers** ==
62 62  
63 63  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:
64 64  
65 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
67 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
68 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
68 68  
69 69  == **Key takeaways** ==
70 70