Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 419.1
edited by Carlijn Kokkeler
on 2024/03/25 11:46
Change comment: There is no comment for this version
To version 267.1
edited by Carlijn Kokkeler
on 2023/11/23 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +209 - Max Verstappen
Content
... ... @@ -3,50 +3,62 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
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.
7 7  
8 -== **Cloud Template R12 Docker - Single Lane** ==
9 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
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}}
10 10  
11 -== **Cloud Template R14 Docker - Double Lane** ==
12 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
12 +== **Quicker Deployment Plan Execution** ==
13 13  
14 -== **Feedback Items** ==
15 -//__Custom trigger__//
16 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
14 +We sped up the process of preparing runtime images in executing 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 of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
16 +== **Next Generation Architecture Default** ==
19 19  
20 -//__Copy to clipboard buttons__//
21 -Copy to clipboard buttons have been added to various pages:
18 +With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
22 22  
23 - * Deploy agent pop-up
24 - * Create - Flow designer: Properties
25 - * Deploy - Property releases: Property details
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
22 +== **Cloud Template R11 Docker - Single Lane** ==
28 28  
29 -//__Reset H2 database__//
30 -For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
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"]].
31 31  
32 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
34 -* For on-premise runtimes, only a reset of the runtime is needed.
26 +== **Cloud Template R13 Docker - Double Lane** ==
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
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"]].
37 37  
30 +== **Feedback Items** ==
31 +
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:
34 +
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.
38 +
39 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
40 +
41 +//__Queue explorer milliseconds__//
42 +The queue browser now displays milliseconds in the timestamps.
43 +
44 +//__Static alerts queue consumers__//
45 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
46 +
38 38  == **Bug Fixes** ==
39 -//__Runtime overview improvements__//
40 -The runtime overview has been improved regarding checks on the runtime version.
41 41  
49 +//__Flow Designer connection line__//
50 +In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
51 +
52 +//__Portal for migrated models__//
53 +We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
54 +
42 42  == **Fancy Forum Answers** ==
43 43  
44 44  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:
45 45  
46 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
47 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
59 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
48 48  
49 -== **Key Takeaways** ==
61 +== **Key takeaways** ==
50 50  
51 51  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:
52 52  
... ... @@ -57,6 +57,7 @@
57 57  * Check out the release notes [here]
58 58  * Start thinking about how the license tracker can aid your development
59 59  * Start thinking about major, minor, and patch
72 +* Upgrade to the latest build number
60 60  * Keep making great integrations
61 61  
62 62  Let's stay in touch and till next time!
... ... @@ -64,6 +64,7 @@
64 64  {{info}}
65 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]]
66 66  
80 +~*~* Indicates a next-generation-architecture only feature.
67 67  {{/info}}
68 68  )))
69 69