Changes for page 208 - Controlled State

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+186 - Daemon Switch

Content

...	...	@@ -2,115 +2,135 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
	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	6
7		-== **Queue Browser** ==
	7	+== **New monitoring stack** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	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	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
	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"]]
12	12
13		-To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
	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	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	18	+== **Transformation Improvements** ==
16	16
17		-After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
	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.
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	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.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	26	+[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	28	+== **Feedback items ** ==
33	33
34		-== **Message Redelivery ** ==
	30	+Apart from the key updates around functionality, we have also solved other feedback items.
35	35
36		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
	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.
37	37
38		-Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
	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.
39	39
40		-Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
	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	41
42		-On top of that we have added some additional functionality.
	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	43
44		-* Search option
45		- ** Original queue name
46		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
	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.
47	47
48		-== **3rd generation runtime bolstering** ==
	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	49
50		-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.
	50	+[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
51	51
52		-//__SOAP and REST web services migration, including splitting them__//
53		-With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
	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	54
55		-//__Changing SSL settings for 3rd generation runtime models works__//
56		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
	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	57
58		-//__Improved migration for JMS flows__//
59		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	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	60
61		-{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
	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.
62	62
63		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
64		-As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
	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.
65	65
66		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
67		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	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.
68	68
69		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
70		-With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
	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.
71	71
72		-//__Added "Reset" functionality__//
73		-With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
	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.
74	74
75		-== **Feedback items ** ==
	76	+[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
76	76
77		-We have also solved other feedback items besides the flow designer's critical updates.
	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.
78	78
79		-//__Improved naming convention on Store related pages__//
80		-We have improved various display names using the merge functionality within our store offering.
	81	+[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
81	81
82		-//__Update security protocols for our internal architecture__//
83		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
	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.
84	84
85		-//__Improved read-only description for "if exists" constructions in Transformations__//
86		-To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
	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.
87	87
	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.
88	88
89		-== **Bug fixes ** ==
	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.
90	90
91		-//__Decent validation feedback when not filling in the property value__//
92		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
	95	+== **Bug Fixes** ==
93	93
94		-//__Incorrect resource locations__//
95		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	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.
96	96
97		-//__Apply to environment in User Management performance improvement__//
98		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	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.”
99	99
	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	+
100	100	== **Fancy Forum Answers** ==
101	101
102		-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:
	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:
103	103
104		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
105		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
106		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
107		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
	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"]]
108	108
109	109	== **Key takeaways** ==
110	110
111		-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:
	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:
112	112
113		-* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	133	+* If you have questions surrounding our Program Increment Planning, please get in touch with
114	114	* If you have feedback or ideas for us, talk to the Platypus
115	115	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
116	116	* Clear your browser cache (Ctrl + Shift + Del)
...	...	@@ -123,7 +123,7 @@
123	123	Let's stay in touch and till next time!
124	124
125	125	{{info}}
126		-~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	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]]
127	127
128	128	~*~* Indicates a GEN3-only feature.
129	129	{{/info}})))((({{toc/}}))){{/container}}