Changes for page 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 168.1
edited by Carlijn Kokkeler
on 2023/10/11 13:32
on 2023/10/11 13:32
Change comment:
There is no comment for this version
To version 172.1
edited by Carlijn Kokkeler
on 2023/10/12 10:49
on 2023/10/12 10:49
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,6 +4,9 @@ 4 4 5 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. 6 6 7 +== **Release Date Change** == 8 +As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM. 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]] 9 + 7 7 == **Deployment Plan** == 8 8 9 9 //__Improved deployment plan to make the process better and more predictable__// ... ... @@ -29,7 +29,7 @@ 29 29 //__Message definition elements order__// 30 30 We fixed an issue that the order of message definition elements was changed after being imported. 31 31 32 -//__Imp roting a store item with synchronous message definitions__//35 +//__Importing a store item with synchronous message definitions__// 33 33 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. 34 34 35 35 //__Importing store items containing static copies__// ... ... @@ -38,6 +38,9 @@ 38 38 //__Importing Store content__// 39 39 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. 40 40 44 +//__Store disclaimer__// 45 +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. 46 + 41 41 == **Feedback Items** == 42 42 43 43 //__Alerting manual pause__// ... ... @@ -82,7 +82,7 @@ 82 82 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. 83 83 84 84 //__Partial search for messages__// 85 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 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". 86 86 87 87 //__Disk usage after cloud template update__// 88 88 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. ... ... @@ -90,7 +90,6 @@ 90 90 //__Error handling migration__// 91 91 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. 92 92 93 - 94 94 == **Fancy Forum Answers** == 95 95 96 96 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: