Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 160.1
edited by CarlijnKokkeler
on 2023/10/11 09:25
on 2023/10/11 09:25
Change comment:
There is no comment for this version
To version 412.1
edited by Erik Bakker
on 2024/03/11 14:48
on 2024/03/11 14:48
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 06 -SituationalDeployment1 +216 - Hack Heaven - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,76 +1,97 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 + 6 +**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes. 4 4 5 - **Hithere, eMagiz developers!**Inthe last few weeks, we have donemuch work for theDeploy phase. Ontopofthat,wehave workedon several store functionalities.Next to this, we have several smaller feedback items from our hackathonefforts that are now releasedto you.8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** == 6 6 7 - == **DeploymentPlan**==10 +Placeholder for info from Bas 8 8 9 -//__Improved deployment plan to make the process better and more predictable__// 10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 12 +{{info}}Text{{/info}} 11 11 12 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 14 +== **Announcement - Spring 6** == 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 16 +Placeholder for info from Jelle 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 18 +{{warning}}Text{{/warning}} 20 20 21 -//__Cleanup old images__// 22 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 20 +== ** Updated release functionality - Infra flow selection** == 23 23 24 -//__Performance improvements for loading releases__// 25 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. 22 +This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level. 26 26 27 - == **StoreImprovements** ==24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 28 28 29 -//__Message definition elements order__// 30 -We fixed an issue that the orders of message definition’s elements were changed after imported. 26 +When you are in edit mode you can select a new version via the right-click option as you were used to for other flows. 31 31 32 - == **FeedbackItems** ==28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 33 33 34 -//__Alerting manual pause__// 35 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 30 +On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release. 36 36 37 -//__Ordering of graphs in Manage__// 38 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 39 39 40 -//__UTC times in Grafana panels__// 41 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 34 +== ** Updated deploy functionality on-premise - Multiple environments selection** == 42 42 43 -//__Update flow designer version__// 44 -The framework used in the flow designer has been updated to the latest version. 36 +{{warning}}The following is only applicable under the following conditions: 37 + * Windows 2022 server 38 + * Atleast one port opened (as a consequence of a hosted web service){{/warning}} 45 45 46 -//__Carwash track TLS versions in logging__// 47 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 40 +When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine. 48 48 49 -//__Moving channels in the flow designer__// 50 -Moving already attached channels in the flow designer has been made sligthly easier. 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 51 51 52 -//__Topic sizes description change__// 53 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 44 +== **Feedback Items** == 45 +//__Easier component selection in flow designer__// 46 +The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier. 54 54 55 -//__ Passwordchangenotification__//56 - Whenanaccount password change requestis made,even when thisfails,amailissent to theaccount owner toinformthe ownerabout theaction.48 +//__Improved handling of optionality in JSON on lists__// 49 +Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired. 57 57 58 -//__ Passwordcomparison__//59 - Whenchangingapassword,itiscomparedtoalistofknowndatabasebreachesforsecurity.Awarningisshownwhenthepasswordcorrespondswith apasswordinthe database.51 +//__Loading bar when searching for log entries__// 52 +To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search. 60 60 54 +//__Improved feedback when deleting elements from Capture__// 55 +To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes. 61 61 57 +//__Enhanced filter options in Manage__// 58 +With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places. 59 + 60 +//__Copy property names from Create__// 61 +This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying. 62 + 63 +//__Improved feedback during migration to the current-runtime architecture__// 64 +We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings. 65 + 66 +//__Block user from making changes to their cloud whilst another upgrade is still in progress__// 67 +We now block the user from making changes to their cloud configuration when another upgrade is still in progress. 68 + 69 +//__Cron trigger validation__// 70 +We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression. 71 + 62 62 == **Bug Fixes** == 73 +//__Queue name validation__// 74 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer. 63 63 64 -//__Flow designer styling__// 65 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 76 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 66 66 78 +//__Removal of onramp__// 79 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase. 80 + 81 +//__eMagiz login__// 82 +In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field. 83 + 67 67 == **Fancy Forum Answers** == 68 68 69 69 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: 70 70 71 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 88 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 89 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 90 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 91 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 92 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 72 72 73 -== **Key takeaways** ==94 +== **Key Takeaways** == 74 74 75 75 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 ... ... @@ -81,7 +81,6 @@ 81 81 * Check out the release notes [here] 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 next-generation-architecture only feature. 93 -{{/info}})))((({{toc/}}))){{/container}} 112 +{{/info}} 113 +))) 114 + 115 +((( 116 +{{toc/}} 117 +))) 94 94 {{/container}} 119 +{{/container}}