Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version
To version 321.1
edited by Carlijn Kokkeler
on 2023/12/21 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,81 +1,84 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **3rd generation runtime bolstering** ==
8 +== **Logging** ==
9 +//__Missing log entries__//
10 +We improved crash handling so that log messages clearly show when and why a container failed to start.
8 8  
9 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
10 10  
11 -//__Migration of JMS backup configuration improved__//
15 +//__Deployment execution error message__//
16 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
18 +== **Overviews** ==
19 +//__Runtime overview__//
20 +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.
14 14  
15 -//__Autogenerated exits can be deployed at once__//
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
24 +//__Missing properties overview__//
25 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
18 18  
19 -//__Improved the performance of deploying or activating a release__//
27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
29 +//__Runtime restart or redeploy overview__//
30 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
22 22  
23 -== **Exportable Release Audit** ~* ==
32 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
24 24  
25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
35 +== **Feedback Items** ==
28 28  
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34 34  
35 -== **Feedback items ** ==
38 +//__Breaking changes pop-up__//
39 +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'.
36 36  
37 -We have also solved other feedback items besides the flow designer's critical updates.
41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
38 38  
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
43 +//__External recipients emailaddress__//
44 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
41 41  
42 -//__Improved naming convention on Store related pages__//
43 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
46 +//__Broker queue metrics dashboards__//
47 +It is now possible to select the MQTT broker in the queue metrics dashboards.
44 44  
45 -//__Press "Enter" to search on multiple pages__//
46 -In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
49 +//__Runtime image version__//
50 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
47 47  
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
62 62  
53 +== **Bug Fixes** ==
54 +
55 +//__Message throughput__//
56 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
57 +
58 +//__Cloud template upgrade unjust rollback__//
59 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
60 +
61 +//__Next generation block__//
62 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
63 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
68 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
69 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
70 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
71 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
72 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
71 71  
74 +
72 72  == **Key takeaways** ==
73 73  
74 -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:
77 +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:
75 75  
76 76  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  * If you have feedback or ideas for us, talk to the Platypus
78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 79  * Clear your browser cache (Ctrl + Shift + Del)
80 80  * Check out the release notes [here]
81 81  * Start thinking about how the license tracker can aid your development
... ... @@ -88,6 +88,12 @@
88 88  {{info}}
89 89  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90 90  
91 -~*~* Indicates a GEN3-only feature.
92 -{{/info}})))((({{toc/}}))){{/container}}
94 +~*~* Indicates a next-generation-architecture only feature.
95 +{{/info}}
96 +)))
97 +
98 +(((
99 +{{toc/}}
100 +)))
93 93  {{/container}}
102 +{{/container}}