Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version
To version 247.1
edited by Carlijn Kokkeler
on 2023/11/21 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,64 +2,78 @@
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 couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
5 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **Start/Stop Flows** ~*~* ==
7 +{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}}
8 8  
9 -{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
9 +== **Quicker Deployment Plan** ==
10 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
10 10  
11 -To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12 +== **Next Generation Architecture Default** ==
13 +With this release, the next generation architecture will become the default. New models will use this generation as default.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
15 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
14 14  
15 -After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
17 +== **Cloud Template R11 - Single Lane** ==
18 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
20 +== **Cloud Template R13 - Double Lane** ==
18 18  
19 -{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
20 20  
21 -== **Manage overview Event Streaming** ~*~* ==
23 +== **Feedback Items** ==
22 22  
23 -To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
25 +//__Unused properties overview__//
26 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
27 +* Not used by any runtime that is in the Create phase release.
28 +* Not required by a flow that is in the Create phase release.
29 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
31 +//__Send build requests asynchronously__//
32 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
26 26  
27 -== **Feedback items ** ==
34 +//__Queue explorer milliseconds__//
35 +The queue browser now displays milliseconds in the timestamps.
28 28  
29 -We have also solved other feedback items besides the flow designer's critical updates.
37 +//__Cancel and next buttons order__//
38 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
30 30  
31 -//__Topic configuration calculation__//
32 -With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
40 +//__Unused images__//
41 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
33 33  
34 -//__Make preparation step in deployment plan visible__//
35 -For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
43 +//__Carwash logging__//
44 +A new logging feature enabling us to make better choices in encryption standards will be released.
36 36  
37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
46 +//__Static alerts queue consumers__//
47 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
38 38  
39 -//__3rd generation runtime debugger feedback__//
40 -We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
49 +== **Bug Fixes** ==
41 41  
42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 -As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
51 +//__Flow Designer connection line__//
52 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
44 44  
45 -//__User Management synchronization now happens in one step__//
46 -With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
54 +//__Portal for migrated models__//
55 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
47 47  
57 +//__Error channel inbounds__//
58 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
59 +
48 48  == **Fancy Forum Answers** ==
49 49  
50 50  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:
51 51  
52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
64 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
55 55  
69 +
56 56  == **Key takeaways** ==
57 57  
58 -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:
72 +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:
59 59  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 63  * Clear your browser cache (Ctrl + Shift + Del)
64 64  * Check out the release notes [here]
65 65  * Start thinking about how the license tracker can aid your development
... ... @@ -72,6 +72,6 @@
72 72  {{info}}
73 73  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74 74  
75 -~*~* Indicates a GEN3-only feature.
89 +~*~* Indicates a next-generation-architecture only feature.
76 76  {{/info}})))((({{toc/}}))){{/container}}
77 77  {{/container}}