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

From version 7.1
edited by eMagiz
on 2022/10/12 11:20
Change comment: There is no comment for this version
To version 105.1
edited by Erik Bakker
on 2023/04/25 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +196 - The Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,51 +2,70 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of 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.
6 6  
7 -==**Store additions**==
8 -We have released several Store items that can be used in the Design Store and which include complete data models and transformations. See the list below of the components that have these.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 3.png]]
7 +== **"Live" mode on flow testing** ==
11 11  
12 -==**Audit trail User Management**==
13 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
14 -
15 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
9 +With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
16 16  
17 -==**Next Generation Monitoring & Alerting engine**==
18 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
19 -
20 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
21 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
22 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
23 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
24 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
25 -
26 -
27 -=== **Improvements** ===
28 -
29 -* Performance Deployment plan
30 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
31 -
32 -* Flow Designer updates
33 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
34 -
35 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
36 -
37 -* Store
38 -We have fixed several smaller Store import issues to improve the user experience.
39 -
11 +By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
12 +
13 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
14 +
15 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
18 +
19 +== **3rd generation improvements** ==
20 +
21 +//__Event Streaming statistics completion__//
22 +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.
23 +
24 +//__Deployments on next generation architecture__//
25 +This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
26 +
27 +//__Clean queues option__//
28 +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.
29 +
30 +== **Feedback items ** ==
31 +
32 +//__On-premise containers are started upon slot wakeup__//
33 +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.
34 +
35 +//__See Fixed IP in Deploy Architecture__//
36 +To improve our cloud offerings' we now display the configured fixed IP on your cloud connectors. This will unlock you as the user to easily communicate this value to external parties without involvement on our end.
37 +
38 +//__Resource path is shown to the user__//
39 +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.
40 +
41 +//__Flow designer improvements__//
42 +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.
43 +
44 +//__Improved capabilities of a company contact__//
45 +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.
46 +
47 +== **Bug fixes ** ==
48 +
49 +//__Optional API parameters are handled correctly__//
50 +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.
51 +
52 +//__Without CDM rights nothing related to any data model can be edited anymore__//
53 +With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
54 +
55 +//__Improved sorting of Design and Deploy archticture__//
56 +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.
57 +
40 40  == **Fancy Forum Answers** ==
41 41  
42 -As always, a gentle reminder to all 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:
60 +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:
43 43  
44 -* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
45 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
62 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
63 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
64 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
46 46  
47 47  == **Key takeaways** ==
48 48  
49 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
68 +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:
50 50  
51 51  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
52 52  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -57,12 +57,11 @@
57 57  * Start thinking about major, minor, and patch
58 58  * Upgrade to the latest build number
59 59  * Keep making great integrations
60 -* Check out the new documentation portal.
61 61  
62 62  Let's stay in touch and till next time!
63 63  
64 64  {{info}}
65 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  
67 67  ~*~* Indicates a GEN3-only feature.
68 68  {{/info}})))((({{toc/}}))){{/container}}