Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 165.1
edited by Carlijn Kokkeler
on 2023/10/11 12:44
on 2023/10/11 12:44
Change comment:
There is no comment for this version
To version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
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 -20 6-Situational Deployment1 +201 - Be Informed - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,104 +2,67 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last few weeks, we have donemuchworkfortheDeployphase.Ontopofthat, wehave workedonseveralstorefunctionalities.Nextto this,we have several smallerfeedbackitemsfromour hackathon efforts that are nowreleasedto you.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you. 6 6 7 -== **Deployment Plan** == 7 +== **Announcement - Release Properties** == 8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 9 - //__Improveddeployment planto makeheprocess betterandmore predictable__//10 - Thealgorithmforgenarating adefaultdeploymentplanis improvedtokeepjmsdowntimeand alertingtoa minimum.Next to this,thestart/stop/restartmachinedeploymentstepsarenowalsoexecutedcorrectlyfor aws andon-premisesmachines.10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 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. 13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 14 14 15 - //__JMSmemorysettingcheck__//16 - Achangeinmemorysettingstriggers redeployment of thecontainer now.15 +== ** Breadcrumb navigation in eMagiz ** == 16 +With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel. 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 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. 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. 26 - 27 -== **Store Improvements** == 28 - 29 -//__Message definition elements order__// 30 -We fixed an issue that the order of message definition elements was changed after being imported. 31 - 32 -//__Improting a store item with synchronous message definitions__// 33 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 34 - 35 -//__Importing store items containing static copies__// 36 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 37 - 38 38 == **Feedback Items** == 39 39 40 -//__ Alertingmanual pause__//41 - A fewreleasesagowechanged thebehaviorofalerting in thedeploymentplan. Now eachtime whenadeploymentplan isexecuted the alertingwillbe automatically re-enabledwhenthe deployercloses the deployment plan orclosestheebbrowser.Themajorityoftheusersare happywith thenew behavior,butthere are someusecases that youdonot wantstartthealertingimmediately.Withthis release,if alertinghas beenpaused manually, this willnotbeactivatedautomaticallyafterrelease deployment.22 +//__Improved layout of catalog page in Design__// 23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations. 42 42 43 -//__ OrderingofgraphsinManage__//44 - The graphsinManage are noworderedaccordingtoimportance.Thismeanshat runtimestatisticsare sortedby "Process CPU usage"(highestfirst),queue statistics aresorted by "Messagesinqueue"(highestfirst),and HTTPstatistics aresorted by"Unsuccessful requests" (highest first).25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 45 45 46 -//__ UTCtimesinGrafanapanels__//47 - AllGrafana panelsnow show UTC times,which arenormallyusedin eMagiz,insteadoflocal (browser)time zones.Thisway, itiseasiertomatchgraphswith loggingeventsor alerts.28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 48 48 49 -//__ Updateflowdesignerversion__//50 - Theframeworkusedin theflowdesigner hasbeenupdatedtothelatestversion.31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal we have improved the audit trail to better specify who changed what at which point in time. 51 51 52 -//__ CarwashtrackTLS versions inlogging__//53 - Anewlogging featurewill bereleased,enablingus tomakebetterchoices indeprecating old encryptionstandards.34 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 54 54 55 -//__Moving channels in the flow designer__// 56 -Moving already attached channels in the flow designer has been made sligthly easier. 57 - 58 -//__Topic sizes description change__// 59 -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. 60 - 61 -//__Password change notification__// 62 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 63 - 64 -//__Password comparison__// 65 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 66 - 67 -//__Inactive user alerting__// 68 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 69 - 70 -//__Alphabetical sorting on user level in HTTP statistics__// 71 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 72 - 73 -//__SOAP Web services path__// 74 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 75 - 76 76 == **Bug Fixes** == 77 77 78 -//__ Flowdesignerstyling__//79 -T hestylingoftheflowdesigner'sleftcomponentpanelhasbeenrestructured,solvingararebugwhichwouldbreakthe stylingof certainfunctionalities.39 +//__Avoid clicking on other components while deleting another__// 40 +To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 80 80 81 -//__ Partialsearchformessages__//82 - Itisnowpossible tosearchonmessagespartiallyinManageMonitoring.Forexample,search for Uptimecanbedoneby searching for "up" "time" "ptim".42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved several things with regards to the validation feedback when migrating to the next-generation architecture. 83 83 84 -//__ Diskusage after cloudtemplateupdate__//85 - In thelast cloud template updatetherewasansuewithdisk performance.This hasbeenresolved inthisrelease.You canmanually upgradeyour cloudtemplate,or relyon automaticupdates.45 +//__Make sure that user credentials can be viewed with view rights__// 46 +This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights. 86 86 87 -//__ Error handlingmigration__//88 - If thereisno custom error handling, when migrating to Gen3,the errorchannelto “errorChannel”is only createdforthefirstinbound in anentryflow. Thishasbeenfixed byaddinga migrationstep,wherewe settheerrorchannelofallinboundsin aflowto “errorChannel”ifthecustomerrorhandling istto false.48 +//__Refresh behavior within the deployment plan is fixed__// 49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 89 89 90 90 == **Fancy Forum Answers** == 91 91 92 92 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: 93 93 94 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 95 95 96 96 == **Key takeaways** == 97 97 98 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:61 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 99 99 100 100 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 101 101 * If you have feedback or ideas for us, talk to the Platypus 102 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 65 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 103 103 * Clear your browser cache (Ctrl + Shift + Del) 104 104 * Check out the release notes [here] 105 105 * Start thinking about how the license tracker can aid your development ... ... @@ -112,6 +112,6 @@ 112 112 {{info}} 113 113 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 114 114 115 -~*~* Indicates a next-generation-architecture only feature.78 +~*~* Indicates a GEN3-only feature. 116 116 {{/info}})))((({{toc/}}))){{/container}} 117 117 {{/container}}