Wiki source code of 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 4 | |||
| |
154.1 | 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. |
| |
1.1 | 6 | |
| |
172.1 | 7 | == **Release Date Change** == |
| |
182.1 | 8 | As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
172.1 | 9 | |
| |
154.1 | 10 | == **Deployment Plan** == |
| |
151.1 | 11 | |
| |
154.1 | 12 | //__Improved deployment plan to make the process better and more predictable__// |
| |
181.1 | 13 | The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment. |
| |
151.1 | 14 | |
| |
181.1 | 15 | {{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}} |
| 16 | |||
| |
154.1 | 17 | //__Editing release properties__// |
| 18 | With this release, it will be possible to change the description of a property by editing the property. | ||
| |
101.1 | 19 | |
| |
175.1 | 20 | //__Container memory settings__// |
| |
155.1 | 21 | A change in memory settings triggers redeployment of the container now. |
| |
124.1 | 22 | |
| |
155.1 | 23 | //__Properties tab__// |
| 24 | We have removed the deprecated tab Properties in the Deploy phase. | ||
| |
159.1 | 25 | |
| |
155.1 | 26 | //__Cleanup old images__// |
| |
157.1 | 27 | When a release is removed, the related unused images in the on-premises machines will be removed as well. |
| 28 | |||
| |
159.1 | 29 | //__Performance improvements for loading releases__// |
| 30 | Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. | ||
| 31 | |||
| |
154.1 | 32 | == **Store Improvements** == |
| |
124.1 | 33 | |
| |
160.1 | 34 | //__Message definition elements order__// |
| |
162.1 | 35 | We fixed an issue that the order of message definition elements was changed after being imported. |
| |
160.1 | 36 | |
| |
171.1 | 37 | //__Importing a store item with synchronous message definitions__// |
| |
161.1 | 38 | We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. |
| 39 | |||
| |
163.1 | 40 | //__Importing store items containing static copies__// |
| |
162.1 | 41 | We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. |
| 42 | |||
| |
178.1 | 43 | //__Importing store content__// |
| |
168.1 | 44 | We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. |
| 45 | |||
| |
171.1 | 46 | //__Store disclaimer__// |
| 47 | Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer. | ||
| 48 | |||
| |
154.1 | 49 | == **Feedback Items** == |
| |
149.1 | 50 | |
| |
154.1 | 51 | //__Alerting manual pause__// |
| 52 | 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. | ||
| |
151.1 | 53 | |
| |
154.1 | 54 | //__Ordering of graphs in Manage__// |
| 55 | 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). | ||
| |
151.1 | 56 | |
| |
155.1 | 57 | //__UTC times in Grafana panels__// |
| 58 | All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. | ||
| |
151.1 | 59 | |
| |
155.1 | 60 | //__Update flow designer version__// |
| |
184.1 | 61 | The framework used in the flow designer has been updated, improving performance. |
| |
155.1 | 62 | |
| |
157.1 | 63 | //__Carwash track TLS versions in logging__// |
| 64 | A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. | ||
| |
155.1 | 65 | |
| |
157.1 | 66 | //__Moving channels in the flow designer__// |
| 67 | Moving already attached channels in the flow designer has been made sligthly easier. | ||
| 68 | |||
| 69 | //__Topic sizes description change__// | ||
| 70 | In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. | ||
| 71 | |||
| |
159.1 | 72 | //__Password change notification__// |
| 73 | When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. | ||
| 74 | |||
| 75 | //__Password comparison__// | ||
| 76 | When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. | ||
| 77 | |||
| |
162.1 | 78 | //__Inactive user alerting__// |
| 79 | Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. | ||
| |
159.1 | 80 | |
| |
162.1 | 81 | //__Alphabetical sorting on user level in HTTP statistics__// |
| 82 | Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. | ||
| 83 | |||
| |
165.1 | 84 | |
| |
124.1 | 85 | == **Bug Fixes** == |
| |
122.1 | 86 | |
| |
159.1 | 87 | //__Flow designer styling__// |
| 88 | The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. | ||
| |
148.1 | 89 | |
| |
162.1 | 90 | //__Partial search for messages__// |
| |
170.1 | 91 | It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim". |
| |
162.1 | 92 | |
| 93 | //__Disk usage after cloud template update__// | ||
| |
164.1 | 94 | In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. |
| |
162.1 | 95 | |
| |
165.1 | 96 | //__Error handling migration__// |
| 97 | If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. | ||
| 98 | |||
| |
1.1 | 99 | == **Fancy Forum Answers** == |
| 100 | |||
| |
30.1 | 101 | 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: |
| |
1.1 | 102 | |
| |
166.1 | 103 | * [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] |
| |
177.1 | 104 | * [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] |
| 105 | * [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] | ||
| 106 | * [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] | ||
| 107 | * [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] | ||
| |
1.1 | 108 | |
| |
177.1 | 109 | |
| |
185.1 | 110 | == **Key Takeaways** == |
| |
1.1 | 111 | |
| |
149.1 | 112 | 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: |
| |
1.1 | 113 | |
| |
30.1 | 114 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 115 | * If you have feedback or ideas for us, talk to the Platypus |
| |
151.1 | 116 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. |
| |
1.1 | 117 | * Clear your browser cache (Ctrl + Shift + Del) |
| |
186.1 | 118 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.206 - Situational Deployment.WebHome||target="blank"]] |
| |
1.1 | 119 | * Start thinking about how the license tracker can aid your development |
| 120 | * Start thinking about major, minor, and patch | ||
| 121 | * Upgrade to the latest build number | ||
| 122 | * Keep making great integrations | ||
| 123 | |||
| 124 | Let's stay in touch and till next time! | ||
| 125 | |||
| 126 | {{info}} | ||
| |
30.1 | 127 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 128 | |
| |
141.1 | 129 | ~*~* Indicates a next-generation-architecture only feature. |
| |
1.1 | 130 | {{/info}})))((({{toc/}}))){{/container}} |
| 131 | {{/container}} |