Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 29.1
edited by Erik Bakker
on 2022/10/24 09:03
Change comment: There is no comment for this version
To version 504.1
edited by CarlijnKokkeler
on 2024/05/06 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -186 - Daemon Switch
1 +220 - Patch Parade
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,150 +1,94 @@
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!** We have hit the ground running in this quarter by not only focusing on larger features but also spend a substantial chunk of time on focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to a first set of models. So let us dive into all we have to offer this time!
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **New monitoring stack** ==
8 +== **Feedback Items** ==
8 8  
9 -This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of what these changes entail please check out the following microlearnings.
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
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"]]
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
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}}
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
17 17  
18 -== **Transformation Improvements** ==
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
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.
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
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.
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27 27  
28 -== **Feedback items ** ==
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29 29  
30 -Apart from the key updates around functionality, we have also solved other feedback items.
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
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 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
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.
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
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.
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 -
44 -//__Improved styling of error feedback on User Management in Deploy__//
45 -With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
46 -
47 -//__Show only the ten latest flow versions when selecting a flow version in a Release__//
48 -To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
49 -
50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
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 -
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 95  == **Bug Fixes** ==
39 +//__Annotation styling__//
40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
96 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.
42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
99 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.”
44 +//__Filter rejection warnings__//
45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
102 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.
47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
105 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.
49 +//__Manage Explore__//
50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
108 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.
52 +//__Page refreshing__//
53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
111 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.
55 +//__Message redelivery__//
56 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
114 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.
58 +//__Deployment plan__//
59 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
117 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 all 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:
63 +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' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
126 -* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
127 -* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
65 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
66 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
67 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
128 128  
129 -== **Key takeaways** ==
69 +== **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:
71 +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:
132 132  
133 -* If you have questions surrounding our Program Increment Planning, please get in touch with
73 +* 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 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 +* 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)
137 -* Check out the release notes [here]
77 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
138 138  * Start thinking about how the license tracker can aid your development
139 139  * Start thinking about major, minor, and patch
140 -* Upgrade to the latest build number
141 141  * Keep making great integrations
142 142  
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]]
85 +~* 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 -~*~* Indicates a GEN3-only feature.
149 -{{/info}})))((({{toc/}}))){{/container}}
87 +{{/info}}
88 +)))
89 +
90 +(((
91 +{{toc/}}
92 +)))
150 150  {{/container}}
94 +{{/container}}