Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
on 2022/12/06 15:57
Change comment:
There is no comment for this version
To version 468.1
edited by CarlijnKokkeler
on 2024/04/23 11:20
on 2024/04/23 11:20
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 89 -PrivateEye1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,87 +1,67 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Private Store** == 8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 9 9 10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 9 +== **Feedback Items** == 10 +//__Machine agents__// 11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE. 11 11 12 -== **3rd generation runtime bolstering** == 13 +//__Custom webhook__// 14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more HERE. 13 13 14 -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. 16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 15 15 16 -//__ SOAP and REST web servicesmigration, includingsplittingthem__//17 - With thisrelease, we have releasedthemigration process that will allow you to migrate SOAPand REST webservicesto the 3rd generationruntime.At the same time, you can directlysplittheall-entryto eliminatethat construction. A specificmigrationpathfor this will be publishedinthedocumentation portal.19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 18 18 19 -//__Changing SSL settings for 3rd generation runtime models works__// 20 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime. 22 +== **Bug Fixes** == 23 +//__Error handling__// 24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 21 21 22 -//__ ImprovedmigrationforJMS flows__//23 - This releasewill improvethemigrationof JMS flows whenmigratingto the3rdgeneration runtime.26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 24 24 25 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}} 29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 26 26 27 -//__ Removed theabilityto add "Debug components"toaflow running inthe 3rd generation runtime architecture__//28 - As of this release,youcan no longeradd debugcomponentson a flowalready migratedtothe 3rdgeneration runtime. This functionalitywill not work in the3rd generationruntime and would break yourflow.32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 29 29 30 -//__ Deployment plan isupdatedcorrectly when completly migrated to the 3rd generation runtimearchitecture__//31 - Wehavefixedabugthatgeneratedanincorrectdefaultdeploymentplan onceyouwerefullymigratedto the3rdgenerationruntime.35 +//__Unused properties__// 36 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 32 32 33 -//__ Correct property generationfor Event Streaming flowsusing the3rd generation runtime architecture__//34 - With this release,the properties generatedforEventStreaming flowsrunninginthe 3rd generationruntimeareconfiguredcorrectly to mimictheonesintheimage.38 +//__Enumeration values__// 39 +Enumeration values for event processors can now be edited in Create. 35 35 36 -//__Added "Reset" functionality__// 37 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime. 41 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 38 38 39 -== **Feedback items ** == 43 +//__SFTP sessions__// 44 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE. 40 40 41 -We have also solved other feedback items besides the flow designer's critical updates. 42 - 43 -//__Improved naming convention on Store related pages__// 44 -We have improved various display names using the merge functionality within our store offering. 45 - 46 -//__Update security protocols for our internal architecture__// 47 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards. 48 - 49 -//__Improved read-only description for "if exists" constructions in Transformations__// 50 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does. 51 - 52 - 53 -== **Bug fixes ** == 54 - 55 -//__Decent validation feedback when not filling in the property value__// 56 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality. 57 - 58 -//__Incorrect resource locations__// 59 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 60 - 61 -//__Apply to environment in User Management performance improvement__// 62 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 63 - 64 64 == **Fancy Forum Answers** == 65 65 66 66 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: 67 67 68 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 69 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 70 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 71 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 50 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 51 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 52 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 72 72 73 -== **Key takeaways** ==54 +== **Key Takeaways** == 74 74 75 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:56 +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 76 77 77 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 * If you have feedback or ideas for us, talk to the Platypus 79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 60 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 80 * Clear your browser cache (Ctrl + Shift + Del) 81 -* Check out the release notes [here] 62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 82 82 * Start thinking about how the license tracker can aid your development 83 83 * Start thinking about major, minor, and patch 84 -* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! ... ... @@ -89,6 +89,11 @@ 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -~*~* Indicates a GEN3-only feature. 93 -{{/info}})))((({{toc/}}))){{/container}} 72 +{{/info}} 73 +))) 74 + 75 +((( 76 +{{toc/}} 77 +))) 94 94 {{/container}} 79 +{{/container}}