Wiki source code of 250 - Fix Fest
Last modified by Erik Bakker on 2025/07/28 12:21
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier. | ||
| 7 | |||
| 8 | == **Improved navigation on flow level in Create** == | ||
| 9 | |||
| 10 | With this release, we add a new option to enter "Start Editing" mode while working on a flow in Create. Apart from entering this mode via the Flow Designer overview and the Transformation view, you can now also enter "Start Editing" mode directly from the Message Definition level (i.e., Topic In, System Message, and CDM). Additionally, we now introduce the "Open in Design" button at this level to align with the current navigation on the Transformation level. | ||
| 11 | |||
| 12 | [[image:Main.Images.Release Blog.WebHome@release-250-new-navigation-options-create.png]] | ||
| 13 | |||
| 14 | {{warning}}Note that the "Open in Design" will currently not function 100% accurately when the same message type is used across multiple integration patterns.{{/warning}} | ||
| 15 | |||
| 16 | == **Custom resources - Easier Editable** == | ||
| 17 | |||
| 18 | For both custom XSLTs and Groovy scripts, we introduce functionality that allows you to edit these resources from the UI in the Flow Designer **after** initially uploading the resource to your flow. | ||
| 19 | |||
| 20 | [[image:Main.Images.Release Blog.WebHome@release-250-edit-content-custom-resource.png]] | ||
| 21 | |||
| 22 | == **Minor Changes** == | ||
| 23 | |||
| 24 | //__Export - PNG__// | ||
| 25 | When exporting to PNG, the filename now includes a logical name that contains the technical name of your model, the phase that was exported, and the time of the export. | ||
| 26 | |||
| 27 | //__Capture - Settings__// | ||
| 28 | This overview will now display the technical names, when known, of systems, as well as their display names. | ||
| 29 | |||
| 30 | [[image:Main.Images.Release Blog.WebHome@release-250-capture-settings.png]] | ||
| 31 | |||
| 32 | //__Capture - System__// | ||
| 33 | Users can quickly create multiple tenants in a multi-tenant system by using the new “Save and add new” button. The button saves the previously created tenant and opens a new page to create a new tenant. | ||
| 34 | |||
| 35 | //__Design - Settings__// | ||
| 36 | Make it clear that only the model owner can alter the settings displayed under Design> Settings. | ||
| 37 | |||
| 38 | [[image:Main.Images.Release Blog.WebHome@release-250-design-settings-info.png]] | ||
| 39 | |||
| 40 | //__Create - Flow Designer__// | ||
| 41 | The expressions of recipient routers are visible in the grid to show the conditions along with them. Additionally, the grid has been updated to Data Grid 2, which offers a more visually appealing display. | ||
| 42 | |||
| 43 | //__Create - Transformation__// | ||
| 44 | When viewing a transformation with a datatype conversion from or to ‘date’, ‘time’, or ‘datetime’, the time zone used in the formatting is now shown without the need to enter edit mode. | ||
| 45 | |||
| 46 | //__Deploy - Releases__// | ||
| 47 | We have updated the UI and user experience in Release > Details > Flow versions and Integrations tabs. Furthermore, we have added the option to display the integration name rather than the message type name, allowing you to see which API operation you are adding or removing from a release. | ||
| 48 | |||
| 49 | //__Deploy - Architecture__// | ||
| 50 | Cloudslots that do not have an active environment will no longer be planned for upgrade, thereby removing unnecessary emails from being delivered to model owners. | ||
| 51 | |||
| 52 | //__Deploy - Properties__// | ||
| 53 | Updated hover text of the generate button to reflect that values will be replaced. | ||
| 54 | |||
| 55 | [[image:Main.Images.Release Blog.WebHome@release-250-on-hover-text-property.png]] | ||
| 56 | |||
| 57 | //__Manage - Error Messages__// | ||
| 58 | Users with view rights in Manage can now change the status of error messages. | ||
| 59 | |||
| 60 | == **Bug Fixes** == | ||
| 61 | |||
| 62 | //__Design - Message Tree__// | ||
| 63 | The attribute order is exchanged between the moved attributes, rather than performing an algebraic calculation to obtain a new value, thereby avoiding double jumps during the movement. | ||
| 64 | |||
| 65 | //__Create - Message Definition__// | ||
| 66 | A longer time is given to the user to change the fields. Additionally, the pattern field is no longer time-bound, as it requires a longer input. | ||
| 67 | |||
| 68 | //__Create - Flow Designer__// | ||
| 69 | Within the Flow Designer, we have fixed the following bugs. | ||
| 70 | * Validation in the JDBC stored procedure inbound channel adapter is now shown on the right element. | ||
| 71 | * Wiretap channel does not cause an error when its ID is too long. | ||
| 72 | * When changing a filter with a discard channel to start throwing exceptions on rejection instead of sending them to the discard channel, the UI will now correctly reflect this. | ||
| 73 | * When copying a component which have a field value longer than 64 characters and contains the flow’s name, then pasting, the field will not be limited to 64 characters. | ||
| 74 | * Linetokenizer -> Strict of the Flat file to XML transformer and 'Allow empty array' of the system message are not editable anymore when not in 'start editing'. | ||
| 75 | |||
| 76 | //__Create - Transformation__// | ||
| 77 | Within the transformation functionality, we fixed the following bugs. | ||
| 78 | * Users are now able to switch between “Custom XPath” and “Convert datatype” options for the “Transform from date/time” transformer. | ||
| 79 | * Users can return to the correct design phase message mapping. | ||
| 80 | * User permissions are modified for the From Boolean Transformer so that the user can see the Value Mappings. | ||
| 81 | |||
| 82 | //__Create - Flow Testing__// | ||
| 83 | Flow tests that contain Kafka Message Listener Adapter components can be executed again. | ||
| 84 | |||
| 85 | //__Create - Create Flow Version__// | ||
| 86 | We have fixed an issue that caused an error requiring Deploy permission when creating and transferring a new API operation to Deploy, despite having only permission in Capture, Design, and Create. | ||
| 87 | |||
| 88 | //__Deploy - User Management__// | ||
| 89 | We fixed an issue where the list of API operations was not displayed, as these API operations were assigned to the related user. | ||
| 90 | |||
| 91 | {{info}}Additionally, help text is converted to the latest help text format.{{/info}} | ||
| 92 | |||
| 93 | //__Deploy - Architecture__// | ||
| 94 | Within deploy architecture, we fixed the following bugs. | ||
| 95 | * Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. | ||
| 96 | * You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model. | ||
| 97 | |||
| 98 | [[image:Main.Images.Release Blog.WebHome@release-250-pending-changes-double-lane.png]] | ||
| 99 | |||
| 100 | {{info}}As you can see in the screenshot above, you now have to decide whether to apply your pending changes to availability zone B first or apply both zones at once in this pop-up instead of being confronted with a secondary pop-up after seeing the list of pending changes. While that resolves the reported bug, it also improves the user experience when interacting with this part of the platform.{{/info}} | ||
| 101 | |||
| 102 | == **Fancy Forum Answers** == | ||
| 103 | |||
| 104 | As always, this is a gentle reminder to ask questions via the Q&A forum, which is available in the eMagiz iPaaS portal. This way, we can all benefit from the knowledge within the community. | ||
| 105 | |||
| 106 | == **Key Takeaways** == | ||
| 107 | |||
| 108 | Thanks to all who helped build the product and those who tested and provided feedback to improve it. To end this post, here are some key takeaways for you: | ||
| 109 | |||
| 110 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 111 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 112 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 113 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 114 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.250 - Fix Fest.WebHome||target="blank"]] | ||
| 115 | * Start thinking about how the license tracker can aid your development | ||
| 116 | * Start thinking about major, minor, and patch | ||
| 117 | * Keep making great integrations | ||
| 118 | |||
| 119 | Let's stay in touch and till next time! | ||
| 120 | |||
| 121 | {{info}} | ||
| 122 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 123 | |||
| 124 | {{/info}} | ||
| 125 | ))) | ||
| 126 | |||
| 127 | ((( | ||
| 128 | {{toc/}} | ||
| 129 | ))) | ||
| 130 | {{/container}} | ||
| 131 | {{/container}} |