Changes for page 241.1 - Wild West
Last modified by Erik Bakker on 2025/04/04 08:35
From version 59.1
edited by Erik Bakker
on 2023/03/14 08:51
on 2023/03/14 08:51
Change comment:
There is no comment for this version
To version 239.1
edited by Erik Bakker
on 2025/04/04 08:35
on 2025/04/04 08:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 194 -GiantLeap1 +2411 - Wild West - Content
-
... ... @@ -1,33 +1,10 @@ 1 - The releaseintroducesvariousimprovementson our 3rd generationruntime architecture andvarious otherfixesin otherpartsoftheportal.Subsequently,we willreleaseanewruntimeimage supportingthe variousimprovements.1 +In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]]. 4 - 5 -=====New features===== 6 - 7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]]. 8 -* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889) 9 - 10 -=====Minor changes===== 11 - 12 -* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not. 13 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) 14 -* Deploy - User Management: Roles are sorted alphabetically. (#806) 15 -* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date. 16 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements. 17 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833) 18 - 19 19 ====Bug fixes==== 20 20 21 -* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases. 22 -* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object. 23 -* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902) 24 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters). 25 -* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action. 26 -* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries. 27 -* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825) 28 -* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898) 29 -* Manage - Alerting: Editable column shows the correct value. 5 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release. 6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release. 30 30 31 31 ====Remarks==== 32 32 33 -* Create- Flow designer:Afterthedeployment, the‘VersionCompare' and'VersionRestore’featureswill beunavailablefora fewhours,becauseof data migration. Youwill get an error statingthatthe versionisnotcompatiblewith theselected featureuntil migration hasfinished.10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.