Skip to Content

Changes for page 217 - Template Tango

Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 420.1
edited by CarlijnKokkeler
on 2024/03/25 12:15
Change comment: There is no comment for this version
To version 154.1
edited by CarlijnKokkeler
on 2023/10/10 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +206 - Situational Deployment
Content
... ... @@ -1,52 +1,50 @@
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 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!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
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 +== **Deployment Plan** ==
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 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
13 13  
14 -== **Feedback Items** ==
15 -//__Custom trigger__//
16 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
19 19  
20 -//__Copy to clipboard buttons__//
21 -Copy to clipboard buttons have been added to various pages:
16 +
17 +
18 +== **Store Improvements** ==
19 +
22 22  
23 - * Deploy agent pop-up
24 - * Create - Flow designer: Properties
25 - * Deploy - Property releases: Property details
21 +== **Feedback Items** ==
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
23 +//__Alerting manual pause__//
24 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
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 +//__Ordering of graphs in Manage__//
27 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
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.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
37 -
38 38  == **Bug Fixes** ==
39 -//__Runtime overview improvements__//
40 -The runtime overview has been improved regarding checks on the runtime version.
41 41  
32 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
33 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
34 +
35 +//__Ensure that differing container configurations deploy the correct configuration__//
36 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
37 +
38 +//__Remove queurying options in Manage__//
39 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
40 +
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"]]
45 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
48 48  
49 -== **Key Takeaways** ==
47 +== **Key takeaways** ==
50 50  
51 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:
52 52  
... ... @@ -57,6 +57,7 @@
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
58 +* 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 -)))
66 +~*~* Indicates a next-generation-architecture only feature.
67 +{{/info}})))((({{toc/}}))){{/container}}
73 73  {{/container}}
74 -{{/container}}