Wiki source code of 174 - Feedback Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:28
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 3 | |||
| 4 | **Hi there, eMagiz developers!** We have looked back and ahead to the upcoming Q within the IP week and through our PI planning in the last several weeks. Apart from planning new functionalities and improvements, we have also finished up loads of smaller items that will be made available with this release. Notably among these are flow testing improvements, MFA configuration improvements, consistency improvements and many more. So let us dive into all that we have to offer this time around! | ||
| 5 | |||
| 6 | == **MFA Configuration** == | ||
| 7 | |||
| 8 | After you log in and you do not have configured your MFA yet you will be prompted by the system to set up the MFA configuration. Note that users that don’t configure the MFA will not be allowed to access anything within the portal until they have configured the MFA. | ||
| 9 | |||
| 10 | == **Feedback items ** == | ||
| 11 | Apart from the key updates around functionality, we have also solved other feedback items. | ||
| 12 | |||
| 13 | //__Sorting API Catalog__// | ||
| 14 | With this release we have sorted all operations in your API Gateway Catalog alphabetically based on the name of your operation path. This makes it easier to find certain paths and change them. | ||
| 15 | |||
| 16 | //__Export Keystore Event Streaming__// | ||
| 17 | Previously, when you exported the relevant keystore to connect to a topic eMagiz provided a generic name for the exported keystore. Now we changed this to give a better description that refers to the display name of the system/user for which the keystore is for. | ||
| 18 | |||
| 19 | //__Mendix Credentials Page Gone__// | ||
| 20 | With this release, the obsolete Mendix credentials page in Design has been removed to avoid confusion what it might do or not. | ||
| 21 | |||
| 22 | //__Auto generation of technical names__// | ||
| 23 | With this release we have improved the way in which we auto generated technical names based on the provided display name by the user. Most notably, we changed the functionality so that it will not remove any vowels when your display name does not exceed the maximum allotted number of characters for a technical name. | ||
| 24 | |||
| 25 | //__Test case deletion__// | ||
| 26 | With this release we have added a confirmation pop-up when you want to delete a test case. This should prevent users from accidentally throwing away a test case that they would still need. | ||
| 27 | |||
| 28 | //__Irrelevant features deleted from license tracker__// | ||
| 29 | We removed features that were not relevant from a license tracker perspective from the license tracker overview. | ||
| 30 | |||
| 31 | //__Topic Sorting__// | ||
| 32 | When you need to select a topic in or a topic out when configuring an event processor you previously had a hard time finding the right topic if you had a lot of topics in your model. To improve this process we sort the shown options alphabetically so you can find the relevant topic much easier. | ||
| 33 | |||
| 34 | //__Operation deletion__// | ||
| 35 | With this release we have added a confirmation pop-up when you want to delete an operation. This should prevent users from accidentally throwing away an operation that they would still need. | ||
| 36 | |||
| 37 | //__Entering your MFA__// | ||
| 38 | Whit this release we have improved the process of entering your MFA. At first we have ensured that when you click on the field to enter your MFA the cursor will always start at the front. Subsequently we made sure that you can press Enter once you have field in your MFA code instead of having to click the button. | ||
| 39 | |||
| 40 | //__Change root__// | ||
| 41 | We have added a progress bar when you change the root entity so you get informed that eMagiz is doing something and you do not have to click again. | ||
| 42 | |||
| 43 | //__Sorting Tags when linking them__// | ||
| 44 | From this release on we have sorted the tags you see when linking them to your system or your integration in Capture. | ||
| 45 | |||
| 46 | //__Removal of AQMP Status page__// | ||
| 47 | We have removed the AMQP status page as it has become obsolete | ||
| 48 | |||
| 49 | //__Removal Event Streaming Tab in Deploy__// | ||
| 50 | We have removed the Event Streaming tab in Deploy as it holds no value for users. | ||
| 51 | |||
| 52 | == **Bug fixes** == | ||
| 53 | See below for all bug fixes that are solved with this release. | ||
| 54 | |||
| 55 | //__Hello eMagiz__// | ||
| 56 | When you enter for example status.emagiz.com (which is not yet available) you will now be routed to the eMagiz website instead of running into a security pop-up in your browser. | ||
| 57 | |||
| 58 | //__Select Client Information__// | ||
| 59 | Previously, it was impossible to select alternative options when configuring your client information settings in your REST template after the introduction of build .59. With the release of the new build number (.61) this bug is resolved allowing you to select all valid options again from the portal. | ||
| 60 | |||
| 61 | //__Test a split in a flow__// | ||
| 62 | With this release it will become possible to test a split functionality within a flow and create a success response when you configure the test case correctly. | ||
| 63 | |||
| 64 | //__Incorrect MFA Feedback__// | ||
| 65 | Previously, it could happen in certain situations that you got a very annoying and non-specific error. We have now fixed that you don’t get this error when you are not yet MFA authenticated. | ||
| 66 | |||
| 67 | //__Show the test results always in the pop-out__// | ||
| 68 | Previously, you would only see the messages in the pop-out in your result overview when you had defined an expected message. Now we have changed the functionality to also show the actual message in the pop-out when you did not define an expected message. | ||
| 69 | |||
| 70 | //__Hovering over an integration in the release overview__// | ||
| 71 | Previously, when you hovered over an integration in the release overview you would see the build number twice. We have now resolved this so you only see the build number only once. | ||
| 72 | |||
| 73 | //__Selecting a new flow version in a release__// | ||
| 74 | Before, you would have to click twice for the first flow version you wanted to add to your release. With this release we have solved that behavior. | ||
| 75 | |||
| 76 | //__Refresh option Manage Dashboard__// | ||
| 77 | We have added a refresh option to the Manage Dashboard to help the user when the Manage Dashboard incorrectly loads the first time. | ||
| 78 | |||
| 79 | //__Synchronous Mendix communication without import mapping__// | ||
| 80 | With this release we will introduce a new eMagiz Mendix Connector. You will need to upgrade to this version (5.1.0) when you do synchronous communication with Mendix without using an import (and/or export) mapping. | ||
| 81 | |||
| 82 | //__Navigation to Response Mapping__// | ||
| 83 | We fixed that when you directly navigated to the response mapping from the context menu in Design you would end up on a blank page. As of this release eMagiz will lead you to your message mapping again. | ||
| 84 | |||
| 85 | //__JSON Transformations in Event Processors__// | ||
| 86 | We have solved the issues with JSON transformation within Event Processors so they now offer the same functionality as when you would execute a JSON transformation in a messaging or API Gateway solution. | ||
| 87 | |||
| 88 | //__Wrong description of component__// | ||
| 89 | We fixed the wrong description of the XML validating filter component. | ||
| 90 | |||
| 91 | == **Fancy Forum Answers** == | ||
| 92 | |||
| 93 | As always, a gentle reminder to all 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: | ||
| 94 | |||
| 95 | * [[JSON output: need Array instead of object>>https://my.emagiz.com/p/question/172825635700362789||target="blank"]] | ||
| 96 | * [[Sending out a POST with a HTTP outbound gateway without a Content-Type (Payload is empty)>>https://my.emagiz.com/p/question/172825635700362787||target="blank"]] | ||
| 97 | * [[How to put data in a CDATA element?>>https://my.emagiz.com/p/question/172825635700362790||target="blank"]] | ||
| 98 | |||
| 99 | == **Key takeaways** == | ||
| 100 | |||
| 101 | Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: | ||
| 102 | |||
| 103 | * If you have questions surrounding our Program Increment Planning, please get in touch with | ||
| 104 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 105 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 106 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 107 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.Feedback Fiesta.WebHome||target="blank"]] | ||
| 108 | * Start thinking about how the license tracker can aid your development | ||
| 109 | * Start thinking about major, minor, and patch | ||
| 110 | * Upgrade to the latest build number | ||
| 111 | * Keep making great integrations | ||
| 112 | |||
| 113 | Let's stay in touch and till next time! | ||
| 114 | |||
| 115 | {{info}} | ||
| 116 | ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 117 | |||
| 118 | ~*~* Indicates a GEN3-only feature. | ||
| 119 | {{/info}})))((({{toc/}}))){{/container}}{{/container}} |