Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 132.1
edited by Erik Bakker
on 2023/08/01 13:50
Change comment: There is no comment for this version
To version 258.1
edited by Carlijn Kokkeler
on 2023/11/21 12:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,77 +1,80 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6 +**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
8 +{{warning}}
9 +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.
10 +{{/warning}}
9 9  
10 -{{info}}For more information please check out the following microlearnings:
12 +== **Quicker Deployment Plan** ==
11 11  
12 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
13 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 +We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, 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 deployment plan will be finished much quicker now!
15 15  
16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 -{{/info}}
16 +== **Next Generation Architecture Default** ==
18 18  
19 -== ** Deploy Architecture - Apply To Environment improvements ** ==
20 -As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
18 +With this release, the next generation architecture will become the default. New models will use this generation as default.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
23 23  
24 -== ** Breadcrumb navigation in eMagiz ** ==
25 -This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
22 +== **Cloud Template R11 Docker - Single Lane** ==
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
24 +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>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
28 28  
26 +== **Cloud Template R13 Docker - Double Lane** ==
27 +
28 +This release introduces a new cloud template for all our customers running in a double-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>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
29 +
29 29  == **Feedback Items** ==
30 30  
31 -//__Improved layout of catalog page in Design__//
32 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
32 +//__Unused properties overview__//
33 +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:
33 33  
34 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35 -Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
35 +* Not used by any runtime that is in the Create phase release.
36 +* Not required by a flow that is in the Create phase release.
37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
36 36  
37 -//__Additional help texts on Design Architecture__//
38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
39 +//__Queue explorer milliseconds__//
40 +The queue browser now displays milliseconds in the timestamps.
39 39  
40 -//__Improved Audit Trail on several places__//
41 -In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
42 +//__Cancel and next buttons order__//
43 +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.
42 42  
43 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
44 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
45 +//__Unused images__//
46 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
45 45  
46 -== **Bug Fixes** ==
48 +//__Carwash logging__//
49 +A new logging feature enabling us to make better choices in encryption standards will be released.
47 47  
48 -//__Avoid clicking on other components while deleting another__//
49 -To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
51 +//__Static alerts queue consumers__//
52 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
50 50  
51 -//__Improved validation feedback in migrating to the next-generation architecture__//
52 -We have improved the validation feedback when migrating to the next-generation architecture.
54 +== **Bug Fixes** ==
53 53  
54 -//__Make sure that user credentials can be viewed with view rights__//
55 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
56 +//__Flow Designer connection line__//
57 +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.
56 56  
57 -//__Refresh behavior within the deployment plan is fixed__//
58 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
59 +//__Portal for migrated models__//
60 +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.
59 59  
62 +//__Error channel inbounds__//
63 +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.
64 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
69 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
67 67  
68 68  == **Key takeaways** ==
69 69  
70 -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:
73 +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:
71 71  
72 72  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  * If you have feedback or ideas for us, talk to the Platypus
74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 75  * Clear your browser cache (Ctrl + Shift + Del)
76 76  * Check out the release notes [here]
77 77  * Start thinking about how the license tracker can aid your development
... ... @@ -84,6 +84,12 @@
84 84  {{info}}
85 85  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  
87 -~*~* Indicates a GEN3-only feature.
88 -{{/info}})))((({{toc/}}))){{/container}}
90 +~*~* Indicates a next-generation-architecture only feature.
91 +{{/info}}
92 +)))
93 +
94 +(((
95 +{{toc/}}
96 +)))
89 89  {{/container}}
98 +{{/container}}