Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 41.1
edited by Erik Bakker
on 2022/11/07 16:35
on 2022/11/07 16:35
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 - 187-Integration Sponsor1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,151 +1,83 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** W ith this releasewe will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available.This means that you can now importdata models and transformation on top of systemmessages in Design and accelerators in Create.Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.6 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 -== **Store - Next phase** == 8 +{{warning}} 9 +Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. 10 +{{/warning}} 8 8 9 - Thisrelease will introducethenextphase of the Store to our whole community. With this new functionalityyou can now import data model messages (i.e. CDM, API Gateway Data modelor Event Streamingdata model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.12 +== **Quicker Deployment Plan** == 10 10 11 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--current-store-offering.png]]14 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now! 12 12 13 - {{info}}FormoreinformationontheStore please check outthis [[course>>doc:Main.eMagizAcademy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]].As a reminder you canfindall documentation on all available Storecontent published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}16 +== **Next Generation Architecture Default** == 14 14 15 - ==**NeweMagizMendixConnector**==18 +With this release, the next generation architecture will become the default. New models will use this generation as default. 16 16 17 - With this releasewe introduceanew versionof the eMagiz Mendix Connector. Thisversion (6.0.0) will work both with thecurrent runtimearchitectureand the new runtime architecture makingthemigration fromthecurrent runtimerchitecture to the new runtime architecture easier. The new versionof theeMagiz Mendix Connector can befound inthe Mendix Marketplace and in the eMagiz portal.20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]] 18 18 19 - {{info}}Migratingthe runtime from the eMagiz portalworks the same as for any other runtime.Theigrationpath to migratecanbe found [[here>>doc:Main.eMagiz Support.MigrationPaths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}22 +== **Cloud Template R11 Docker - Single Lane** == 20 20 21 - ==**Flowversion restore**~*==24 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]]. 22 22 23 - Ontop of that we will alsolauncha new Beta feature to the community thatallows you to restoreyourflow to a previous version.Thisway youcan quickly undo changesmade that were incorrect.26 +== **Cloud Template R13 Docker - Double Lane** == 24 24 25 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--flow-version-restore.png]]28 +This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 26 26 27 -{{warning}}Note, that the following restrictions apply when restoring to a previous version: 28 - * Changes made on definition and transformation level are **not** restored 29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 30 +== **Feedback Items** == 32 32 33 -== **Feedback items ** == 32 +//__Unused properties overview__// 33 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 35 +* Not used by any runtime that is in the Create phase release. 36 +* Not required by a flow that is in the Create phase release. 37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 36 36 37 -//__ Redirectto the Manage Dashboard from your modelhome page__//38 - Directlynavigatingto theManagehase(ofanyenvironment) willautomaticallyredirectyouto theerrormessageDashboard,asthatisthelandingpageof theManagephase.39 +//__Send build requests asynchronously__// 40 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 39 39 40 -//__ Readable entry of a SpEL expressionin a flowcomponent__//41 - As of now, theinput field for your SpELexpression in certainflowcomponents willdynamically expand when you enter alarge SpEL expression.This willmprovethe readabilityof your solutionandwillmakeiteasierto enterand validate your SpEL expressions.42 +//__Queue explorer milliseconds__// 43 +The queue browser now displays milliseconds in the timestamps. 42 42 43 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 45 +//__Cancel and next buttons order__// 46 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 44 44 45 -//__ Keep Create and the Create Phasereleaseinsync__//46 - Previously theCreate andthe CreatePhasereleasemight have become out ofsync.As aresult, comparing a release totheCreate Phase releasecouldyield confusingresults.Withthisrelease,we havemadeeveralimprovementsto preventthisfrom happening.48 +//__Unused images__// 49 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 47 47 48 -//__ Mask password valuesin theunused properties overview__//49 -A llpropertyvaluesofthetype password can bemaskedinthe properties overviewscreen.However,this behavior wasdifferentwhenpressingthe unusedpropertiesoverview. With this release,we have corrected thisbehaviorto ensurethat passwords arelso maskedin this overview.51 +//__Carwash logging__// 52 +A new logging feature enabling us to make better choices in encryption standards will be released. 50 50 51 -//__ Press EnteroSearchfor properties__//52 - With thisrelease,wehave added functionalitythatmakes itpossibletopress**Enter** whensearchingforpropertiesin thepropertyoverview.54 +//__Static alerts queue consumers__// 55 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 53 53 54 -//__Styling update on tag selection on integration level__// 55 -With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly. 56 - 57 -//__Enter to close automated flow testing pop-up__// 58 -Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button. 59 - 60 -//__Improved naming of downloaded Event Streaming keystore__// 61 -When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client. 62 - 63 -//__Pop out on the Traces tab within Flow Testing__// 64 -In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow. 65 - 66 -//__Sorting User Management__// 67 -As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview. 68 - 69 -//__Improved warning on passthrough API operation__// 70 -Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create. 71 - 72 -//__Improved update functionality of Swagger file when changing data model__// 73 -Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly. 74 - 75 -{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}} 76 - 77 -//__"Disapprove and go to environment"__// 78 -Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. 79 - 80 -//__Improve readability of API Gateway operations in Create and Deploy__// 81 -When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation. 82 - 83 -//__Add Topic Storage information to License Tracker__// 84 -On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz. 85 - 86 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] 87 - 88 -//__Add Compatibility check when importing store items__// 89 -We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening. 90 - 91 -//__Show dependencies between support objects__// 92 -As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects. 93 - 94 -//__Improve rendering of validation definition when using multiple namespaces__// 95 -With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end. 96 - 97 -//__Improved help texts on next-generation runtime functionality across the portal__// 98 -With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime. 99 - 100 100 == **Bug Fixes** == 101 101 102 -//__ Provide correct feedback when a flowistransferredtoDeploy forthe firsttime__//103 - Withthis release,wehavemadeseveralimprovementsto whatfeedbackis givento theuserwhenmoving a flow from Create toDeployforthe first (upon creatingyour firstdefinitiveversion).Thiswill ensure that noconfusingpop-upswill be shownthat areincorrectandonlyconfusetheuser further.59 +//__Flow Designer connection line__// 60 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 104 104 105 -//__ Show informationin the Exception oferror messagesoverview__//106 -W iththisrelease,wehaveresolved thebugplaguingthis page. As aresult,youwillagain see informationonthispagewhenthereis informationto show.62 +//__Portal for migrated models__// 63 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 107 107 108 -//__ Improve styling of cron triggerconfigurationpop-up__//109 - Thestylingofthispop-upmadeitveryhardtoconfigureacrontrigger.Wehave redesignedthe stylingtomake thepop-up readableagain.65 +//__Error channel inbounds__// 66 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 110 110 111 -//__Prevent flow editing locks in specific situations__// 112 -There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release. 113 - 114 -//__Generate property value empties the runtime selection__// 115 -With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password). 116 - 117 -//__Make sure nothing of a system message is editable from your exit__// 118 -Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices. 119 - 120 -//__Prevent users without view rights from seeing a weird screen in those phases__// 121 -With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently. 122 - 123 -//__Name of starting point of the flow test is incorrect__// 124 -With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct. 125 - 126 -//__Audit Trail on User Management could break__// 127 -When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue. 128 - 129 -//__Progress bar in the license tracker is shown twice__// 130 -With this release, we have fixed a bug that showed the progress bar twice in the license tracker. 131 - 132 -//__Compare flows with support objects in the new flow designer__// 133 -We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer. 134 - 135 135 == **Fancy Forum Answers** == 136 136 137 137 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: 138 138 139 -* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]] 140 -* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]] 72 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 141 141 142 142 == **Key takeaways** == 143 143 144 -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:76 +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: 145 145 146 146 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 * If you have feedback or ideas for us, talk to the Platypus 148 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 149 149 * Clear your browser cache (Ctrl + Shift + Del) 150 150 * Check out the release notes [here] 151 151 * Start thinking about how the license tracker can aid your development ... ... @@ -158,6 +158,12 @@ 158 158 {{info}} 159 159 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 160 160 161 -~*~* Indicates a GEN3-only feature. 162 -{{/info}})))((({{toc/}}))){{/container}} 93 +~*~* Indicates a next-generation-architecture only feature. 94 +{{/info}} 95 +))) 96 + 97 +((( 98 +{{toc/}} 99 +))) 163 163 {{/container}} 101 +{{/container}}