Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 264.1
edited by Carlijn Kokkeler
on 2023/11/22 15:02
Change comment: There is no comment for this version
To version 385.1
edited by Carlijn Kokkeler
on 2024/02/12 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +214 - System Symphony
Content
... ... @@ -3,69 +3,50 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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 +**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
7 7  
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}}
11 -
12 -== **Quicker Deployment Plan Execution** ==
13 -
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!
15 -
16 -== **Next Generation Architecture Default** ==
17 -
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.
19 -
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21 -
22 -== **Cloud Template R11 Docker - Single Lane** ==
23 -
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"]].
25 -
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 -
30 30  == **Feedback Items** ==
31 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:
10 +//__On premise Windows machines__//
11 +We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
34 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.
13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
38 38  
39 -//__Queue explorer milliseconds__//
40 -The queue browser now displays milliseconds in the timestamps.
15 +//__Adding multiple attributes__//
16 +It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. To utilize this, a new runtime image, [[V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.1/||target="blank"]], is needed.
41 41  
42 -//__Unused images__//
43 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
44 44  
45 -//__Carwash logging__//
46 -A new logging feature enabling us to make better choices in encryption standards will be released.
20 +//__Monitoring graphs__//
21 +The monitoring graphs can now show data up to the last thirty days.
47 47  
48 -//__Static alerts queue consumers__//
49 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
50 -
51 51  == **Bug Fixes** ==
24 +//__Image versions__//
25 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
52 52  
53 -//__Flow Designer connection line__//
54 -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.
27 +//__Failover group helptext__//
28 +The helptext of the Group attribute has been improved.
55 55  
56 -//__Portal for migrated models__//
57 -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.
30 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
58 58  
59 -//__Error channel inbounds__//
60 -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.
32 +//__Failover group refresh__//
33 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
61 61  
35 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
36 +
37 +//__Resource paths__//
38 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
39 +
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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:
65 65  
66 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
44 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
45 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
46 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
47 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
67 67  
68 -== **Key takeaways** ==
49 +== **Key Takeaways** ==
69 69  
70 70  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  
... ... @@ -76,7 +76,6 @@
76 76  * Check out the release notes [here]
77 77  * Start thinking about how the license tracker can aid your development
78 78  * Start thinking about major, minor, and patch
79 -* Upgrade to the latest build number
80 80  * Keep making great integrations
81 81  
82 82  Let's stay in touch and till next time!
... ... @@ -84,7 +84,6 @@
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 next-generation-architecture only feature.
88 88  {{/info}}
89 89  )))
90 90