Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 101.1
edited by Erik Bakker
on 2023/04/13 08:56
on 2023/04/13 08:56
Change comment:
There is no comment for this version
To version 169.1
edited by Eva Torken
on 2023/10/11 14:16
on 2023/10/11 14:16
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 - 195-Easter Party1 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.etorken - Content
-
... ... @@ -2,101 +2,107 @@ 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 focusedappingupthepreviousquarterandstartingthenewone.When this happens,wego silent forfew weeksplan forthe upcoming quarter duringour PI rituals. Thistimeweaddedthefamous "Hackathon"to the end of the PI weeksowecould start the Easterbreak with excellentspirit after solving several smaller feedback itemsand bugsreportedby you. Severalof those stories will be included in thisandthe upcomingrelease. On top ofthat, we introduce various improvements to our API Gatewaypattern and our 3rd generationruntime architecture. Subsequently,wewillreleasea new runtime image supportingthe multiple improvements.5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you. 6 6 7 -== ** Releaseproperties** ==**7 +== **Deployment Plan** == 8 8 9 -With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]]. 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. 10 10 11 -As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s). 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 12 12 13 -{{info}}The following considerations need to be taken into account when using this functionality: 14 -* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture 15 -* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted 16 -* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment). 17 -*{{/info}} 15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 18 18 19 -== **API improvements** == 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 20 20 21 -//__ Improvedauto-generatederror handling__//22 -When youcreateanewoperationin yourAPI gateway,eMagizwill now automaticallygeneratethecorrect schemas, HTTP codes,andexamplesfor thisoperation basedon industry standards.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 23 24 -//__ Switch defaultmessage format__//25 - Wehave improvedthelogic whenyou switch thessage formatof your gateway messagefrom XML to JSON or viceversa. Asa result,theSwagger filewill bechangedaccordingly.Once youupdate the relevantflow in Createand deploy the solution, the Swagger UI will automaticallymatchthe expectedresult.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 26 27 -//__Re-using elements in gateway message__// 28 -This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message. 27 +== **Store Improvements** == 29 29 30 -//__ Improved namingof API operationswhen addingintegrationstoCreate__//31 - Previouslywhen you addedAPI operations to the Createphase,theHTTPoperation(i.e., POST, PUT, GET) was notvisibleto a user. Asresult, it became tough for a usertodiscern between specific operationsoncemultipleof themwere used onone resource(i.e., Order, Invoice, Lead).Toclarify this for the user, the displayname defined in Design (insteadof Capture)is now used withinthisoverview forthese operations.29 +//__Message definition elements order__// 30 +We fixed an issue that the order of message definition elements was changed after being imported. 32 32 33 -== **3rd generation improvements** == 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 34 35 -//__ Updateoftheticalertingengine__//36 - Inthis release, we have updatedthe static alertingengine thatdetermines when oneof the static alerts, asdefined by eMagiz,should betriggered(or not). Thischangewillimprovethe performanceoftheolutionandwillensurethatthealerts areactivated correctly.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 37 38 -//__ Add "Datapipeline"functionality__//39 - Thisreleaseintroducesthe "datapipeline"functionalitytothe 3rd generationruntime. This removesnother blockage formodelswaitingonthis beforemigratingtothe3rdgenerationruntime.38 +//__Importing Store content__// 39 +We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. 40 40 41 -//__Fix related to the debugger__// 42 -This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated. 41 +== **Feedback Items** == 43 43 44 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 43 +//__Alerting manual pause__// 44 +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. 45 45 46 -//__ Improvedmigrationprocess__//47 -Th isreleaseintroduced afixthat allows ausermigrateeventprocessorswithcustomerrorhandlingwithoutmanualintervention.46 +//__Ordering of graphs in Manage__// 47 +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). 48 48 49 -//__ Deploymentplanchange__//50 - Inthisrelease,thepreparereleasestepwillnot startautomaticallyanymore.Thispreventsheuserfromwaitingforthis actiontobe finishedbefore theycancontinuedeployingthesolutionotheir environment.49 +//__UTC times in Grafana panels__// 50 +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. 51 51 52 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 52 +//__Update flow designer version__// 53 +The framework used in the flow designer has been updated to the latest version. 53 53 54 -== **Feedback items ** == 55 +//__Carwash track TLS versions in logging__// 56 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 55 55 56 -//__ LicenseTrackerimprovements__//57 - Withthisrelease, we have addedseveral new features availableto purchase.On top of that, additional informationonthe license,suchaddingnotesand seeingedatasink packets, is now available.58 +//__Moving channels in the flow designer__// 59 +Moving already attached channels in the flow designer has been made sligthly easier. 58 58 59 -//__ Ability toviewthe message definitionfor a topic__//60 - Currently,youcan easilynavigate tothemessagedefinitionof a topicviathecontextmenuinDesign,evenifthereisno eventprocessorlinkedto the topic.61 +//__Topic sizes description change__// 62 +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. 61 61 62 -//__ Restrictedaccessforuploadingcustom certificates toendpoints__//63 - To improveourcloud offerings'generalsecurityandpreventusersfromuploading thewrong certificates,wehaveowrestrictedaccesstothisviewto ensurehatonlythe administratorcan executethis change.This allowsforadiscussion betweentheteam implementingthesolutionand eMagiz before actions are taken.64 +//__Password change notification__// 65 +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. 64 64 65 -== **Bug fixes ** == 67 +//__Password comparison__// 68 +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 66 67 -//__I mproved deletionbehavior forenumerations__//68 - To prevent thateMagiz will incorrectly deleteenumeration lists when you pressa"Cancel"button,wehaveimprovedthedeletionbehaviorwhen viewingenumerations intheCreatephaseofeMagiz.70 +//__Inactive user alerting__// 71 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 69 69 70 -//__ Prevent"async"apioperations__//71 - With thisrelease,wehave removedthebility toselectthe"async" optionwhen thedefaultmessageformatisAPI Management.73 +//__Alphabetical sorting on user level in HTTP statistics__// 74 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 72 72 73 -//__ Importinga response definitionbrokethequestdefinition__//74 - Currently, importing a responsedefinition breaks therequestdefinition.Withhis release,wehavechangedthis behavior,ensuringthatonlytheresponsedefinitionishangedwhenimportingand nottherequestdefinition.76 +//__SOAP Web services path__// 77 +Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 75 75 76 -//__Removing a flow does not update the API "all-entry" anymore__// 77 -When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow. 79 +== **Bug Fixes** == 78 78 79 -//__ Stopdeployment plan when a propertys missing__//80 - Currently, theexecution ofyourdeploymentplancontinues wheneMagiznoticesamissingproperty. Ashis isconfusingforausernd not desirable,we haveupdatedthe logictoensurethatwhenthis happens,the executionstops. This allowsyou to fillinthe properties,and once filled in,youcanontinue with the remainder of the deployment plan.81 +//__Flow designer styling__// 82 +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. 81 81 82 -//__ Cap stacktraceoferror messagesand log entries__//83 - To preventthatenormoustack tracesoferrormessages andlogesneedtoberocessed by various systems, wehavenowlimitedwhatis keptsoonlytherelevantinformationisshownto theuser.84 +//__Partial search for messages__// 85 +It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 84 84 87 +//__Disk usage after cloud template update__// 88 +In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 89 + 90 +//__Error handling migration__// 91 +If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 92 + 85 85 == **Fancy Forum Answers** == 86 86 87 87 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: 88 88 89 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]] 90 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]] 91 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]] 97 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 92 92 93 93 == **Key takeaways** == 94 94 95 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:101 +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: 96 96 97 97 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 98 98 * If you have feedback or ideas for us, talk to the Platypus 99 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 105 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 100 100 * Clear your browser cache (Ctrl + Shift + Del) 101 101 * Check out the release notes [here] 102 102 * Start thinking about how the license tracker can aid your development ... ... @@ -109,6 +109,6 @@ 109 109 {{info}} 110 110 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 111 111 112 -~*~* Indicates a GEN3-only feature.118 +~*~* Indicates a next-generation-architecture only feature. 113 113 {{/info}})))((({{toc/}}))){{/container}} 114 114 {{/container}}