Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 305.1
edited by Carlijn Kokkeler
on 2023/12/21 13:54
Change comment: There is no comment for this version
To version 357.1
edited by Carlijn Kokkeler
on 2024/01/29 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +213 - Joyful Journeys
Content
... ... @@ -3,59 +3,54 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** This release ....
7 7  
8 -== **TBD** ==
9 9  
10 -
11 -
12 12  == **Feedback Items** ==
13 13  
14 -//__Runtime overview__//
15 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
11 +//__Property releases__//
12 +When a new property release is created, this property release can now be viewed and deleted.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
18 18  
19 -//__Missing properties overview__//
20 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
16 +//__Runtime deletion__//
17 +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.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
19 +//__Update flows__//
20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
23 23  
24 -//__Breaking changes pop-up__//
25 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
22 +//__Input fields__//
23 +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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
25 +//__Memory settings__//
26 +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.
28 28  
29 -//__Broker queue metrics dashboards__//
30 -It is now possible to select the MQTT broker in the queue metrics dashboards.
28 +//__Runtime validation__//
29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
31 31  
32 -== **Bug Fixes** ==
31 +//__UI improvements__//
32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
33 33  
34 -//__Deployment execution error message__//
35 -In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
34 +//__Q&A forum search__//
35 +The option to search by pressing the Enter key has been added to the Q&A forum.
36 36  
37 -//__Cloud template upgrade unjust rollback__//
38 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
37 +//__Action messages__//
38 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
39 39  
40 -//__Missing log entries__//
41 -We improved crash handling so that log messages clearly show when and why a container failed to start.
40 +== **Bug Fixes** ==
42 42  
43 -//__Runtime logging__//
44 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
45 45  
43 +
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
51 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
52 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
53 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
54 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
48 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
49 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
50 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
55 55  
52 +== **Key Takeaways** ==
56 56  
57 -== **Key takeaways** ==
58 -
59 59  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:
60 60  
61 61  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -65,7 +65,6 @@
65 65  * Check out the release notes [here]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 -* Upgrade to the latest build number
69 69  * Keep making great integrations
70 70  
71 71  Let's stay in touch and till next time!
... ... @@ -73,7 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -~*~* Indicates a next-generation-architecture only feature.
77 77  {{/info}}
78 78  )))
79 79