Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 27.1
edited by Erik Bakker
on 2022/10/24 09:02
on 2022/10/24 09:02
Change comment:
There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2022/11/21 13:11
on 2022/11/21 13:11
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -18 6-DaemonSwitch1 +188 - Close Encounters - Content
-
... ... @@ -2,135 +2,83 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehave hit the ground running in thisquarter by not only focusing on larger featuresbut also spenda substantialchunk of time on focusing with usall onalotof smallerfeedbackitemsandbugs.All these itemswill be providedtoyou with this release. Amongthese areflowdesignerimprovements, navigationimprovements,andconsistencyimprovements.Ontop of that, wehavemadeournewmonitoringstackavailableoa first setof models.So let us dive into allwehave toofferthistime!5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -== ** Newmonitoringstack** ==7 +== **3rd generation runtime bolstering** == 8 8 9 -This release will introduce a new monitoringstackthatis available formodelsthatruninthe newruntimearchitectureofeMagiz.Withthehelpof thismonitoring stack wehaveredesigned various screensin Manage andrestructuredouralerting approach. For a sneakpreviewof whatthesechanges entail pleasecheckout thefollowing microlearnings.9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 10 10 11 -* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 12 -* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 13 -* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]] 14 -* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-apigateway-http-statistics.WebHome||target="blank"]] 11 +//__Migration of JMS backup configuration improved__// 12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime. 15 15 16 -{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter please contact us at productmanagement@emagiz.com to discuss the possibilities{{/info}} 14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 17 17 18 -== **Transformation Improvements** == 17 +//__Autogenerated exits can be deployed at once__// 18 +This release has fixed a bug that prevented you from deploying an exit flow correctly. 19 19 20 -//__ TogglebetweenDesign andCreate__//21 - This releasewill introduce a togglethatallowsyouto quickly navigatebetweentheCreateTransformationandthe Design Message Mapping.In bothCreateasDesign,a new buttonis addedonthe transformationlevelthatallowsyouto openthetransformationinDesign (or Create)dependingon whereyouarecurrently. Thisshould make navigatingeasierwhenyou makeamistake or forget somethinginDesign.20 +//__Code mapping functionality available on 3rd generation runtime__// 21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality. 22 22 23 -//__Improved Transformationoptionsforbooleans__//24 - Ontopofthat, we willintroduceadditionalfunctionalitytotransform"Booleantoenumeration," "enumerationto Boolean,"and" Boolean to Boolean." Justasyou areusedtofor the "enumerationto enumeration"transformation,you can now definea valuemappingfor each combinationmentionedabove.See below foranexampleof how thislooks.23 +//__Improved the performance when activating a release__// 24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 26 +//__Failing runtimes won't be restarted indefinitely anymore__// 27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped. 27 27 28 -== ** Feedbackitems** ==29 +== **Exportable Release Audit** ~* == 29 29 30 - Apartfromthekeyupdates aroundfunctionality,wehavealsosolved otherfeedback items.31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 31 31 32 -//__Correctly define the size of a cloud slot when creating it for the first time__// 33 -Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted. 33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 34 35 -//__Updated infographic Capture__// 36 -As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture. 35 +{{warning}}Note that the following restrictions apply when exporting an audit document: 36 + * Changes made on definition and transformation level are **not** restored 37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 38 + * 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 39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 37 37 38 -//__Updated error feedback in Design__// 39 -Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown. 41 +== **Feedback items ** == 40 40 41 -//__Improved styling of Topic Storage in Design Architecture__// 42 -When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone. 43 +We have also solved other feedback items besides the flow designer's critical updates. 43 43 44 -//__ Improved stylingoferrorfeedback on User Managementin Deploy__//45 -W ith this releasewehaveimprovedthe styling ofthefeedback pop-up you get inUsermanagementafterpressing“Applyto environment”andseveral updates could notbe executed.45 +//__Data Sink Refactor__// 46 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately. 46 46 47 -//__ Show only thetenlatestflowversionswhenselecting a flow versionin a Release__//48 - Toimprovethe qualityandeedof definingarelease,we will showonlythe latesttenversionsofa flowintherelease widget,asthesetenaremostlikelytobeselected by a user. If youneedan older version,you canadditvia the“Details” optionontheelease.48 +//__Improved naming convention on Store related pages__// 49 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 51 +//__Press "Enter" to search on multiple pages__// 52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 51 51 52 -//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__// 53 -Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification. 54 +* Deploy → Deployment Plan 55 +* Deploy → Properties → History 56 +* Deploy → User Management → Roles 57 +* Manage → Error Messages → Error Messages 58 +* Manage → Error Messages → Flows with Error Messages 59 +* Manage → Error Messages → Exceptions of Error Messages 60 +* Manage → Log Entries 61 +* Manage → Alerts 62 +* Manage → Triggers 63 +* Manage → Tags – Cant find (only Gen2) 64 +* Manage → Notifications 65 +* Manage → Notification Settings 66 +* Manage → Data Usage → History 67 +* Manage → Code mappings → All tabs 54 54 55 -//__Clear API Gateway System message__// 56 -With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level. 57 - 58 -//__Additional information in Property History__// 59 -To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes. 60 - 61 -//__Save Tag when ready__// 62 -With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model. 63 - 64 -//__View deployment step information when having view rights__// 65 -With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment. 66 - 67 -//__Validating external recipients in notification settings__// 68 -Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values. 69 - 70 -//__Automatically link enumeration list to attribute__// 71 -When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually. 72 - 73 -//__Approve and go to environment__// 74 -With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment. 75 - 76 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]] 77 - 78 -//__Remove irrelevant information on a runtime in Design Architecture__// 79 -We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below. 80 - 81 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]] 82 - 83 -//__Add question about message redelivery in Capture__// 84 -When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution. 85 - 86 -//__Prevent pressing “Apply to environment” multiple times leading to conflicts__// 87 -With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period. 88 - 89 -//__Add “State” to the topic details in Deploy Architecture__// 90 -Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched. 91 - 92 -//__Improved stability of logging on the Gen3 Architecture__// 93 -With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally. 94 - 95 -== **Bug Fixes** == 96 - 97 -//__Various updates when importing store items in Design including a transformation__// 98 -With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this. 99 - 100 -//__Opening flow testing widget in specific circumstances was not working__// 101 -With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.” 102 - 103 -//__Improved styling when adding a large message to a flow test__// 104 -With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message. 105 - 106 -//__Errors on the UI do not keep following me__// 107 -Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete. 108 - 109 -//__Navigating back to the transformation in Create works again__// 110 -With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see. 111 - 112 -//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__// 113 -With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz. 114 - 115 -//__Selecting tags when drawing a line in Capture__// 116 -We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture. 117 - 118 -//__Remove invalid selection when configuring a cron trigger via the tooling__// 119 -With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution. 120 - 121 121 == **Fancy Forum Answers** == 122 122 123 -As always, a gentle reminder to a ll 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:71 +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: 124 124 125 -* [[ Header 'X' withvalue '0' willnot besetsince it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]126 -* [[ Kafka Consumer Mendix StringDeserializerisnotworking>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]127 -* [[ Namespaceprefix 'xs' hasnotbeen declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 128 128 129 129 == **Key takeaways** == 130 130 131 -Thanks to all that help build ,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:79 +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: 132 132 133 -* If you have questions surrounding our Program Increment Planning, please get in touch with 81 +* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 134 134 * If you have feedback or ideas for us, talk to the Platypus 135 135 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 136 136 * Clear your browser cache (Ctrl + Shift + Del) ... ... @@ -143,7 +143,7 @@ 143 143 Let's stay in touch and till next time! 144 144 145 145 {{info}} 146 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 94 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 148 148 ~*~* Indicates a GEN3-only feature. 149 149 {{/info}})))((({{toc/}}))){{/container}}