Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 267.1
edited by Carlijn Kokkeler
on 2023/11/23 08:57
Change comment: There is no comment for this version
To version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +213 - Joyful Journeys
Content
... ... @@ -3,62 +3,79 @@
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 ....
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}}
8 +== **Pop-up Improvements** ==
9 +//__Property releases__//
10 +When a new property release is created, this property release can now be viewed and deleted.
11 11  
12 -== **Quicker Deployment Plan Execution** ==
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
13 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!
14 +//__Runtime deletion__//
15 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
15 15  
16 -== **Next Generation Architecture Default** ==
17 +//__Wiretap & debug error messages__//
18 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
17 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.
20 +//__Action messages__//
21 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
23 +== **User Journey** ==
24 +//__Update flows__//
25 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
27 +//__Input fields__//
28 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
23 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"]].
30 +//__UI improvements__//
31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
33 +//__Q&A forum search__//
34 +The option to search by pressing the Enter key has been added to the Q&A forum.
27 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:
38 +//__Memory settings__//
39 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
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.
41 +//__Runtime validation__//
42 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
38 38  
39 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
44 +//__Runtime overview image versions__//
45 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
40 40  
41 -//__Queue explorer milliseconds__//
42 -The queue browser now displays milliseconds in the timestamps.
47 +== **Bug Fixes** ==
43 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.
49 +//__Removal of onramp__//
50 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
46 46  
47 -== **Bug Fixes** ==
52 +//__Component changes reversion__//
53 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
48 48  
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.
55 +//__State generation statistics__//
56 +The state generation graphs will now show the correct number of cache hits and misses.
51 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.
58 +//__Runtime statistics details__//
59 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
54 54  
61 +//__Queue browser timestamps__//
62 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
63 +
64 +//__Deployment prechecks__//
65 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
66 +
67 +//__Addition and deletion of internal recipients__//
68 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
69 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
74 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
75 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
76 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
60 60  
61 -== **Key takeaways** ==
78 +== **Key Takeaways** ==
62 62  
63 63  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:
64 64  
... ... @@ -69,7 +69,6 @@
69 69  * Check out the release notes [here]
70 70  * Start thinking about how the license tracker can aid your development
71 71  * Start thinking about major, minor, and patch
72 -* Upgrade to the latest build number
73 73  * Keep making great integrations
74 74  
75 75  Let's stay in touch and till next time!
... ... @@ -77,7 +77,6 @@
77 77  {{info}}
78 78  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79 79  
80 -~*~* Indicates a next-generation-architecture only feature.
81 81  {{/info}}
82 82  )))
83 83