Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 29.1
edited by Erik Bakker
on 2022/10/24 09:03
on 2022/10/24 09:03
Change comment:
There is no comment for this version
To version 106.1
edited by Erik Bakker
on 2023/04/25 13:59
on 2023/04/25 13:59
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 -1 86 -DaemonSwitch1 +196 - The Last Post - Content
-
... ... @@ -2,135 +2,72 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavehitthegroundrunningin this quarterby not onlyfocusing onlargerfeaturesbutalso spenda substantialchunkoftimeonfocusingwithusallona lotof smaller feedback items and bugs.Allthese itemswillbeprovidedto youwith this release.Amongthese are flowdesigner improvements, navigation improvements,and consistency improvements. On top ofthat, we have made ournew monitoring stack availableto a firstset of models. So let us dive into all we have to offerthis time!5 +**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer. 6 6 7 -== ** Newmonitoringstack** ==7 +== **"Live" mode on flow testing** == 8 8 9 - This release willintroduceaewmonitoringstackthat is available formodelshat runinthe new runtimearchitectureofeMagiz.Withthe helpofthis monitoringstackwehaveredesignedvarious screensinManageandrestructuredouralertingapproach.Forasneak previewofwhatthesechangesentailpleasecheckout the followingmicrolearnings.9 +With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested. 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-alerting-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.HTTP Statistics.WebHome||target="blank"]] 11 +By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions. 15 15 16 - {{info}}Note that the newmonitoringstackis onlyavailablefor models that run thenew runtimearchitecture.Should you wish to becomean early adopter pleasecontact us at productmanagement@emagiz.comto discuss thepossibilities{{/info}}13 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]] 17 17 18 - ==**TransformationImprovements**==15 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode. 19 19 20 -//__Toggle between Design and Create__// 21 -This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design. 17 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]] 22 22 23 -//__Improved Transformation options for booleans__// 24 -On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks. 19 +== **3rd generation improvements** == 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 21 +//__Event Streaming statistics completion__// 22 +In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment. 27 27 28 -== **Feedback items ** == 24 +//__Deployments on next generation architecture__// 25 +This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture. 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 27 +//__Clean queues option__// 28 +This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview. 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. 30 +== **Feedback items ** == 34 34 35 -//__ UpdatedinfographicCapture__//36 - Asof now, we haveupdated theinfographicon theCapturephasetoincorporate the newlookandfeelandexplainthe updatedfunctionalityinCapture.32 +//__On-premise containers are started upon slot wakeup__// 33 +With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning. 37 37 38 -//__ Updatederrorfeedbackin Design__//39 - Before,you couldsee a transformation errorinDesigneventhough thetransformation was notused in yoursolution(i.e.,“datapipeline”functionality).However,whenyounowdefineapecificintegration as adata pipelinesolution,theerror willnotbeshown.35 +//__See Fixed IP in Deploy Architecture__// 36 +To improve our cloud offerings' we now display the configured fixed IP on your cloud connectors. This will unlock you as the user to easily communicate this value to external parties without involvement on our end. 40 40 41 -//__ Improvedstylingof TopicStorageinDesignArchitecture__//42 - When havingalargenumber oftopicsin yournvironment,the topic storageoverviewin DesignArchitecturewillnowbeimproved as thehorizontalscrollbarisgone.38 +//__Resource path is shown to the user__// 39 +You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information. 43 43 44 -//__ Improvedstylingoferror feedback on User Managementin Deploy__//45 -With this release we haveimproved thestyling ofthefeedbackpop-upyougetinUsermanagementafterpressing“Applyto environment”andseveralupdatescould not be executed.41 +//__Flow designer improvements__// 42 +With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion. 46 46 47 -//__ Show only theten latestflowversionswhen selectinga flow versioninaRelease__//48 - Toimprovethequality andspeedof defining arelease,wewill showonlythelatesttenversions ofa flowinthe releasewidget,asthesetenaremostlikelytobeselectedby a user.Ifyouneedan olderversion,youcanadd itvia the“Details”option onhe release.44 +//__Improved capabilities of a company contact__// 45 +With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact. 49 49 50 - [[image:Main.Images.ReleaseBlog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]47 +== **Bug fixes ** == 51 51 52 -//__Optional ClientSecretwhen usingthegrant_typePassword whencalling an OAuth2.0 IDP__//53 - Before,youneededto definetheClientSecret even forthe grant_typePassword, where it isnot alwaysrequired.We havecorrected thisbehaviorto ensurethat thisisinlinewiththe OAuth2.0 specification.49 +//__Optional API parameters are handled correctly__// 50 +Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box. 54 54 55 -//__C learAPIGatewaySystemmessage__//56 -With this release, we have ad dedtheClear button thatyou already know fromthe messagingpatterntotheAPI Gatewaysystemmessage.This unifiestheoptionsbetween thetwoatternsin Design on the system message level.52 +//__Without CDM rights nothing related to any data model can be edited anymore__// 53 +With this release, we have made sure that nothing related to any data model can be edited without having the proper rights. 57 57 58 -//__ Additionalinformation inPropertyHistory__//59 - Toimprovetheusability of the property historypagein Deploy, we nowalsoshowtheruntimeonwhicha particularpropertyischanged.Thisis particularlyusefulwhen changing thesamepropertyused on different runtimes.55 +//__Improved sorting of Design and Deploy archticture__// 56 +With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views. 60 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:60 +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' willnotbeset sinceit isnot a String and noConverter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]126 -* [[ KafkaConsumer Mendix StringDeserializer is notworking>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]127 -* [[ Namespaceprefix'xs'hasnotbeendeclared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]62 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 63 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]] 64 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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:68 +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 70 +* 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]] 83 +~* 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}}