Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 315.1
edited by Carlijn Kokkeler
on 2023/12/21 14:40
Change comment: There is no comment for this version
To version 55.1
edited by Erik Bakker
on 2022/11/24 11:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,86 +1,85 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
7 7  
8 -== **TBD** ==
7 +== **3rd generation runtime bolstering** ==
9 9  
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
10 10  
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
11 11  
12 -== **Feedback Items** ==
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
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.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
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.
23 +//__Failing runtimes won't be restarted indefinitely anymore__//
24 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
26 +== **Exportable Release Audit** ~* ==
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'.
28 +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@release-blog-211-breaking-changes.jpg]]
30 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
28 28  
29 -//__External recipients emailaddress__//
30 -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.
32 +{{warning}}Note that the following restrictions apply when exporting an audit document:
33 + * Works **only** for releases that are promoted and made active on **Production**
34 + * You will **only** see changes made during the **current** calendar year
35 + * On the first of April all objects of the **last** calendar year will be **removed**.
36 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
31 31  
32 -//__Broker queue metrics dashboards__//
33 -It is now possible to select the MQTT broker in the queue metrics dashboards.
38 +== **Feedback items ** ==
34 34  
35 -//__Runtime image version__//
36 -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.
40 +We have also solved other feedback items besides the flow designer's critical updates.
37 37  
38 -//__Runtime restart or redeploy overview__//
39 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
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.
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
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. This release has added this functionality to many more pages across the portal. The complete list is as follows.
42 42  
43 -== **Bug Fixes** ==
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
44 44  
45 -//__Message throughput__//
46 -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.
63 +== **Bug fixes ** ==
47 47  
48 -//__Deployment execution error message__//
49 -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.
65 +//__Loading problems of Deployment plan execution overview__//
66 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
50 50  
51 -//__Cloud template upgrade unjust rollback__//
52 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
53 -
54 -//__Missing log entries__//
55 -We improved crash handling so that log messages clearly show when and why a container failed to start.
56 -
57 -//__Runtime logging__//
58 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
59 -
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 -
63 -//__Feedback deployment plan__//
64 -
65 -
66 66  == **Fancy Forum Answers** ==
67 67  
68 68  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:
69 69  
70 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
71 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
72 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
73 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
74 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
72 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
75 75  
76 -
77 77  == **Key takeaways** ==
78 78  
79 -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:
78 +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:
80 80  
81 81  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82 82  * If you have feedback or ideas for us, talk to the Platypus
83 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
82 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84 84  * Clear your browser cache (Ctrl + Shift + Del)
85 85  * Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
... ... @@ -93,12 +93,6 @@
93 93  {{info}}
94 94  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95 95  
96 -~*~* Indicates a next-generation-architecture only feature.
97 -{{/info}}
98 -)))
99 -
100 -(((
101 -{{toc/}}
102 -)))
95 +~*~* Indicates a GEN3-only feature.
96 +{{/info}})))((({{toc/}}))){{/container}}
103 103  {{/container}}
104 -{{/container}}