Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
Change comment:
There is no comment for this version
To version 505.1
edited by CarlijnKokkeler
on 2024/05/06 13:38
on 2024/05/06 13:38
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 - 189- PrivateEye1 +220 - Patch Parade - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,85 +1,88 @@ 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). 8 +== **Feedback Items** == 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}} 10 +//__Integration pattern information__// 11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration. 11 11 12 - == **3rdgenerationruntime bolstering** ==13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 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. 15 +//__Message queue history__// 16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase. 15 15 16 -//__SOAP and REST web services migration including splitting them__// 17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal. 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 18 18 19 -//__ ChangingSSL settings for 3rd generationruntimemodelsworks__//20 - Aswiththecurrentruntimearchitecture,you cannowalso changetheSSL settings if neededforamodel running inthe 3rd generation runtime.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 21 21 22 -//__Improved migration for JMS flows__// 23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 24 24 25 -{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 26 26 27 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 -As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 29 29 30 -//__ Deploymentplan isupdated correctly when completly migrated to the 3rd generation runtime architecture__//31 - Wehave fixed a bugthat generatedanincorrectdefaultdeploymentplanonceyouwerefullymigrated tothe3rd generationruntime.30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 32 32 33 -== **Feedback items ** == 33 +//__Machine deletion__// 34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 34 34 35 - We havealsosolvedotherfeedback itemsbesides the flow designer's critical updates.36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 36 36 37 -//__Improved naming convention on Store related pages__// 38 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 38 +== **Bug Fixes** == 39 +//__Annotation styling__// 40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 39 39 40 -//__Press "Enter" to search on multiple pages__// 41 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 42 42 43 -* Deploy → Deployment Plan 44 -* Deploy → Properties → History 45 -* Deploy → User Management → Roles 46 -* Manage → Error Messages → Error Messages 47 -* Manage → Error Messages → Flows with Error Messages 48 -* Manage → Error Messages → Exceptions of Error Messages 49 -* Manage → Log Entries 50 -* Manage → Alerts 51 -* Manage → Triggers 52 -* Manage → Tags – Cant find (only Gen2) 53 -* Manage → Notifications 54 -* Manage → Notification Settings 55 -* Manage → Data Usage → History 56 -* Manage → Code mappings → All tabs 44 +//__Filter rejection warnings__// 45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 57 57 58 - == **Bugfixes** ==47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 59 59 60 -//__ Loadingproblemsof Deployment plan execution overview__//61 - Wehave fixedaproblem that could cause issueswhentrying toshowthedeploymentplan executionoverviewafterpressing theDeploybuttonin Deploy-> Releases.49 +//__Manage Explore__// 50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 62 62 52 +//__Page refreshing__// 53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 54 + 55 +//__Message redelivery__// 56 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page. 57 + 58 +//__Deployment plan__// 59 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 60 + 61 +//__Overview pages__// 62 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 63 + 64 +//__Memory check__// 65 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines. 66 + 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: 66 66 67 -* [[ Synchronousfilepick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]68 -* [[ Receivinge-mailvia IMAPor POP3 - Setup>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]69 -* [[ Bestwayof ReceivingandSendingMail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]71 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 72 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 73 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 70 70 71 -== **Key takeaways** ==75 +== **Key Takeaways** == 72 72 73 -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:77 +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: 74 74 75 75 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 76 76 * If you have feedback or ideas for us, talk to the Platypus 77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 81 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 78 * Clear your browser cache (Ctrl + Shift + Del) 79 -* Check out the release notes [here] 83 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 80 80 * Start thinking about how the license tracker can aid your development 81 81 * Start thinking about major, minor, and patch 82 -* Upgrade to the latest build number 83 83 * Keep making great integrations 84 84 85 85 Let's stay in touch and till next time! ... ... @@ -87,6 +87,11 @@ 87 87 {{info}} 88 88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 90 -~*~* Indicates a GEN3-only feature. 91 -{{/info}})))((({{toc/}}))){{/container}} 93 +{{/info}} 94 +))) 95 + 96 +((( 97 +{{toc/}} 98 +))) 92 92 {{/container}} 100 +{{/container}}