Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31

From version 546.1
edited by CarlijnKokkeler
on 2024/06/03 13:30
Change comment: There is no comment for this version
To version 52.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,59 +1,87 @@
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!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
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 -== **Feedback Items** ==
9 -//__Cron triggers__//
10 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
7 +== **3rd generation runtime bolstering** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
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.
13 13  
14 -//__Design changes__//
15 -If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
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.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
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.
18 18  
19 -== **Bug Fixes** ==
20 -//__Trigger activation__//
21 -Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
22 22  
23 -//__Multiple users deploying__//
24 -Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
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.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
27 27  
28 -//__Invalid memory configurations__//
29 -We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +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.
30 30  
31 -//__Property value synchronization__//
32 -Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
29 +== **Exportable Release Audit** ~* ==
33 33  
34 -//__JMS number__//
35 -The number on the JMS container correctly displays the amount of queues present in Design.
31 +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.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
38 38  
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Works **only** for releases that are promoted and made active on **Production**
37 + * You will **only** see changes made during the **current** calendar year
38 + * On the first of April all objects of the **last** calendar year will be **removed**{{/warning}}
39 +
40 +== **Feedback items ** ==
41 +
42 +We have also solved other feedback items besides the flow designer's critical updates.
43 +
44 +//__Improved naming convention on Store related pages__//
45 +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 +
47 +//__Press "Enter" to search on multiple pages__//
48 +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.
49 +
50 +* Deploy → Deployment Plan
51 +* Deploy → Properties → History
52 +* Deploy → User Management → Roles
53 +* Manage → Error Messages → Error Messages
54 +* Manage → Error Messages → Flows with Error Messages
55 +* Manage → Error Messages → Exceptions of Error Messages
56 +* Manage → Log Entries
57 +* Manage → Alerts
58 +* Manage → Triggers
59 +* Manage → Tags – Cant find (only Gen2)
60 +* Manage → Notifications
61 +* Manage → Notification Settings
62 +* Manage → Data Usage → History
63 +* Manage → Code mappings → All tabs
64 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 -* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
69 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
70 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
71 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
45 45  
46 -== **Key Takeaways** ==
73 +== **Key takeaways** ==
47 47  
48 -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 +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:
49 49  
50 50  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
81 +* Check out the release notes [here]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
84 +* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,11 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -{{/info}}
65 -)))
66 -
67 -(((
68 -{{toc/}}
69 -)))
92 +~*~* Indicates a GEN3-only feature.
93 +{{/info}})))((({{toc/}}))){{/container}}
70 70  {{/container}}
71 -{{/container}}