Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 273.1
edited by Erik Bakker
on 2025/07/28 12:18
on 2025/07/28 12:18
Change comment:
There is no comment for this version
To version 108.1
edited by CarlijnKokkeler
on 2023/09/18 11:00
on 2023/09/18 11:00
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 -2 50 -FixFest1 +205 - World Explorers - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,49 +1,71 @@ 1 -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. 1 +{{container}} 2 +{{container layoutStyle="columns"}}((( 3 +[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 2 2 3 - Pleasefind outmore on our[[Releaseblog>>Main.ReleaseInformation.ReleaseBlogs.250-FixFest.WebHome||target="blank"]].5 +**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider. 4 4 5 -== ==Newfeatures ====7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** == 6 6 7 -* Create - Flow Designer: Custom resources in the form of XSLT files and Groovy scripts can be previewed and edited directly in the flow designer. (#1115) 8 -* Create - Flow Designer: Two navigation buttons (Start/Stop editing and “Open in Design“) are added to the following pages. (#1607) 9 -** Messaging: 10 -*** System message 11 -*** CDM message 12 -** API gateway: 13 -*** Gateway message 14 -*** System message 15 -** Event streaming: 16 -*** Topic in 17 -*** Topic out 9 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains. 18 18 19 -== ==Minor changes ====11 +== **Feedback Items** == 20 20 21 -* General - Export: When exporting to PNG, the filename now has a logical name, containing the technical name of your model, the phase that was exported, and the time of the export. (#266) 22 -* Capture - Settings: This overview will now show the technical names, when known, of systems as well as their display name. (#810) 23 -* Capture - System: Users can quickly create multiple tenants in a multi-tenant system by using the new button called “Save and add new”. The button saves the previously created tenant and opens a new page to create a new tenant. (#1527) 24 -* Design - Settings: Make clear that only the model owner can alter the settings displayed under Design - Settings (#1638) 25 -* Create - Flow Designer: 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. (#1649) 26 -* Create - Transformation: 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. (#945) 27 -* Deploy - Releases: 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. (#1581) 28 -* Deploy - Architecture: Cloudslots that do not have an active environment will not be planned to be upgraded anymore, removing unnecessary emails being delivered to model owners. (#1594) 29 -* Deploy - Properties: Updated hover text of the generate button to reflect that values will be replaced. (#1160) 30 -* Manage - Error Messages: Users with view rights in Manage can now change the status of error messages. (#1669) 13 +//__Improved Validation when migrating to the next-generation architecture__// 14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture. 31 31 32 - ====Bug fixes====16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}} 33 33 34 -* Design - Message Tree: Attribute order is exchanged between the moved attributes rather than making an algebraic calculation to obtain a new value to avoid double jumps during the movement. (#1593) 35 -* Create - Message Definition: 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. (#1575) 36 -* Create - Flow Designer: Validation in JDBC stored procedure inbound channel adapter is now shown on the right element. (#1557) 37 -* Create - Flow Designer: Wiretap channel does not cause an error when its ID is too long. (#1606) 38 -* Create - Flow Designer: 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. (#1621) 39 -* Create - Flow Designer: 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. (#1398) 40 -* Create - Flow Designer: 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'. (#1612) 41 -* Create - Transformation: Users are now able to switch between “Custom XPath” and “Convert datatype” options for the “Transform from date/time” transformer. (#1662) 42 -* Create - Transformation: Users can return to the correct design phase message mapping. (#1348) 43 -* Create - Transformation: User permissions are modified for the From Boolean Transformer so that the user can see the Value Mappings. (#1622) 44 -* Create - Flow Testing: Flow tests that contain Kafka Message Listener Adapter components can be executed again. (#1672) 45 -* Create - Create Flow Version: We fixed an issue where you got an error, which requires Deploy permission, when you create and transfer the new API operation to Deploy, since you only have permission in Capture, Design, and Create. (#1677) 46 -* Deploy - Architecture: You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model. (#1651) 47 -* Deploy - Architecture: Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. (#1455) 48 -* Deploy - User Management: We fixed an issue where the list of API operations did not show since these API operations were assigned to the related user. (#1678) 49 -** Additionally, help text is converted to the latest help text format. 18 +//__Improved HTTP Statistics__// 19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview. 20 + 21 +//__Show values on the runtime level in Deploy Architecture__// 22 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution. 23 + 24 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence. 25 +* JMS - The number of queues in the active release. 26 +* Messaging Container - The number of messaging integrations in the active release. 27 +* Messaging Connector - The number of messaging integrations related to this system in the active release. 28 +* API Gateway Container - The number of operations in the active release. 29 +* Event Streaming Container - The number of event processors in the active release. 30 + 31 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}} 32 + 33 +== **Bug Fixes** == 34 + 35 +//__Gain the ability again to configure certificates in Deploy Architecture again__// 36 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. 37 + 38 +//__Ensure that differing container configurations deploy the correct configuration__// 39 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers. 40 + 41 +//__Remove queurying options in Manage__// 42 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors. 43 + 44 +== **Fancy Forum Answers** == 45 + 46 +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: 47 + 48 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 49 + 50 +== **Key takeaways** == 51 + 52 +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: 53 + 54 +* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 55 +* If you have feedback or ideas for us, talk to the Platypus 56 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 57 +* Clear your browser cache (Ctrl + Shift + Del) 58 +* Check out the release notes [here] 59 +* Start thinking about how the license tracker can aid your development 60 +* Start thinking about major, minor, and patch 61 +* Upgrade to the latest build number 62 +* Keep making great integrations 63 + 64 +Let's stay in touch and till next time! 65 + 66 +{{info}} 67 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 68 + 69 +~*~* Indicates a next-generation-architecture only feature. 70 +{{/info}})))((({{toc/}}))){{/container}} 71 +{{/container}}