Skip to Content

Changes for page 217 - Template Tango

Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 422.1
edited by CarlijnKokkeler
on 2024/03/25 14:39
Change comment: There is no comment for this version
To version 53.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 -217 - Template Tango
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,62 +1,88 @@
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!** In this release, new cloud templates for docker single and docker double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
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 -== **Cloud Template R12 Docker - Single Lane** ==
9 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]].
7 +== **3rd generation runtime bolstering** ==
10 10  
11 -== **Cloud Template R14 Docker - Double Lane** ==
12 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
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 -== **Feedback Items** ==
15 -//__Dynamic trigger__//
16 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
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.
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.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.
19 19  
20 -//__Copy to clipboard buttons__//
21 -Copy to clipboard buttons have been added to various pages:
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 - * Deploy agent pop-up
24 - * Create - Flow designer: Properties
25 - * Deploy - Property releases: Property details
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.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.
28 28  
29 -//__Reset H2 database__//
30 -For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
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.
31 31  
32 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
34 -* For on-premise runtimes, only a reset of the runtime is needed.
29 +== **Exportable Release Audit** ~* ==
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
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.
37 37  
38 -== **Bug Fixes** ==
39 -//__Runtime overview improvements__//
40 -The runtime overview has been improved regarding checks on the runtime version.
33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
41 41  
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**.
39 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
40 +
41 +== **Feedback items ** ==
42 +
43 +We have also solved other feedback items besides the flow designer's critical updates.
44 +
45 +//__Improved naming convention on Store related pages__//
46 +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.
47 +
48 +//__Press "Enter" to search on multiple pages__//
49 +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.
50 +
51 +* Deploy → Deployment Plan
52 +* Deploy → Properties → History
53 +* Deploy → User Management → Roles
54 +* Manage → Error Messages → Error Messages
55 +* Manage → Error Messages → Flows with Error Messages
56 +* Manage → Error Messages → Exceptions of Error Messages
57 +* Manage → Log Entries
58 +* Manage → Alerts
59 +* Manage → Triggers
60 +* Manage → Tags – Cant find (only Gen2)
61 +* Manage → Notifications
62 +* Manage → Notification Settings
63 +* Manage → Data Usage → History
64 +* Manage → Code mappings → All tabs
65 +
42 42  == **Fancy Forum Answers** ==
43 43  
44 44  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:
45 45  
46 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
47 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
70 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
48 48  
49 -== **Key Takeaways** ==
74 +== **Key takeaways** ==
50 50  
51 -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:
76 +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:
52 52  
53 53  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
54 54  * If you have feedback or ideas for us, talk to the Platypus
55 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
56 56  * Clear your browser cache (Ctrl + Shift + Del)
57 57  * Check out the release notes [here]
58 58  * Start thinking about how the license tracker can aid your development
59 59  * Start thinking about major, minor, and patch
85 +* Upgrade to the latest build number
60 60  * Keep making great integrations
61 61  
62 62  Let's stay in touch and till next time!
... ... @@ -64,11 +64,6 @@
64 64  {{info}}
65 65  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  
67 -{{/info}}
68 -)))
69 -
70 -(((
71 -{{toc/}}
72 -)))
93 +~*~* Indicates a GEN3-only feature.
94 +{{/info}})))((({{toc/}}))){{/container}}
73 73  {{/container}}
74 -{{/container}}