Wiki source code of 188 - Close Encounters

Last modified by Carlijn Kokkeler on 2024/04/18 13:21
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4
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.
6
7 == **3rd generation runtime bolstering** ==
8
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
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.
13
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.
16
17 //__Autogenerated exits can be deployed at once__//
18 This release has fixed a bug that prevented you from deploying an exit flow correctly.
19
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.
22
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.
25
26 == **Exportable Release Audit** ~* ==
27
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.
29
30 [[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
31
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}}
37
38 == **Feedback items ** ==
39
40 We have also solved other feedback items besides the flow designer's critical updates.
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.
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. This release has added this functionality to many more pages across the portal. The complete list is as follows.
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
63 == **Bug fixes ** ==
64
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.
67
68 == **Fancy Forum Answers** ==
69
70 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:
71
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
76 == **Key takeaways** ==
77
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:
79
80 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81 * If you have feedback or ideas for us, talk to the Platypus
82 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 * Clear your browser cache (Ctrl + Shift + Del)
84 * Check out the release notes [[here>>doc:Main.Release Information.Portal.188 - Close Encounters.WebHome||target="blank"]]
85 * Start thinking about how the license tracker can aid your development
86 * Start thinking about major, minor, and patch
87 * Upgrade to the latest build number
88 * Keep making great integrations
89
90 Let's stay in touch and till next time!
91
92 {{info}}
93 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94
95 ~*~* Indicates a GEN3-only feature.
96 {{/info}})))((({{toc/}}))){{/container}}
97 {{/container}}