Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+192 - Small Step

Content

...	...	@@ -2,163 +2,144 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** With this release we 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 import data models and transformation on top of system messages 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.
	5	+**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger functionality.
6	6
7		-== **Store - Next phase** ==
	7	+== **Start/Stop Flows** ~*~* ==
8	8
9		-This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
	9	+{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
10	10
11		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
	11	+To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12	12
13		-{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
	13	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
14	14
15		-== **New eMagiz Mendix Connector** ==
	15	+
	16	+{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
	17	+
	18	+
	19	+ observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
16	16
17		-With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
	21	+We offer alerting on five types.
18	18
19		-{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
	23	+* Error message
	24	+* Log message
	25	+* Queue consumers
	26	+* Messages in queue
	27	+* Queue throughput
20	20
21		-== **Flow version restore** ~* ==
	29	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
22	22
23		-On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect.
	31	+These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	33	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
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}}
	35	+Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
32	32
33		-== **Academy improvements** ==
	37	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
34	34
35		-On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning.
	39	+== **Debugger ** ~*~* ~* ==
36	36
37		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
	41	+{{warning}}Note that this functionality only works when the following criteria are met.
	42	+* Your JMS server is running on the 3rd generation runtime
	43	+* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
	44	+* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
38	38
39		-== **Flow Designer Improvements** ==
	46	+As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
40	40
41		-//__See last changed date and changed by on resource level__//
42		-This release will reinstate the ability to see who changed a resource last and when it was changed for the last time. You can find this information by double-clicking on a resource or viewing its details via the view button.
	48	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
43	43
44		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]]
	50	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
45	45
46		-//__See on which other flows a resource is used__//
47		-This release will reinstate the ability to see whether a resource is used in other flows within your model or not. This will help to determine the impact of a specific change.
	52	+Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
48	48
49		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
	54	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
50	50
51		-//__Toggle option to see the generated resource by default__//
52		-Upon request, we have made the toggle for the generated resources in the new flow designer user-dependent. This means that you, as a user, can determine that the toggle should also be on. This means that the generated resources will be shown to you when opening any flow in eMagiz. When you switch the toggle off, this will mean that you will **not** see the generated resources by default.
	56	+{{info}}Note the following limitations when working with the debugger.
	57	+ * Your entire model needs to be migrated to the 3rd generation runtime
	58	+ * Only **one** flow **per** runtime can be debugged **per** environment
	59	+ * There is only **one** overview in which **all** debugged messages are shown
	60	+ * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
	61	+ * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
	62	+ ** After five minutes the debug functionality will be shutdown automatically under water.
	63	+ ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
53	53
54		-== **Feedback items ** ==
	65	+== **Volume mapping - Network Share** ==
55	55
56		-We have also solved other feedback items besides the flow designer's critical updates.
	67	+This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
57	57
58		-//__Redirect to the Manage Dashboard from your model home page__//
59		-Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase.
	69	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
60	60
61		-//__Readable entry of a SpEL expression in a flow component__//
62		-As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions.
	71	+[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
63	63
64		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
	73	+== **Feedback items ** ==
65	65
66		-//__Keep Create and the Create Phase release in sync__//
67		-Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening.
	75	+We have also solved other feedback items besides the flow designer's critical updates.
68	68
69		-//__Mask password values in the unused properties overview__//
70		-All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview.
	77	+//__Show status on machine level under Deploy Architecture__//
	78	+With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
71	71
72		-//__Press Enter to Search for properties__//
73		-With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
	80	+//__Improved validation feedback on non-supported WSS4J interceptor __//
	81	+We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
74	74
75		-//__Styling update on tag selection on integration level__//
76		-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.
	83	+//__Improve help text in flow testing on Java classes__//
	84	+We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
77	77
78		-//__Enter to close automated flow testing pop-up__//
79		-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.
	86	+//__Improved readibility of notification when trying to delete a runtime__//
	87	+When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
80	80
81		-//__Improved naming of downloaded Event Streaming keystore__//
82		-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.
	89	+//__Improved sorting of missing properties overview__//
	90	+We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
83	83
84		-//__Pop out on the Traces tab within Flow Testing__//
85		-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.
	92	+//__Improved notification when error message cannot be found__//
	93	+We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
86	86
87		-//__Sorting User Management__//
88		-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.
	95	+//__Additional lifecycle management overview__//
	96	+We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
89	89
90		-//__Improved warning on passthrough API operation__//
91		-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.
	98	+//__Improved feedback when memory settings are negative__//
	99	+We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
92	92
93		-//__Improved update functionality of Swagger file when changing data model__//
94		-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.
	101	+//__Auto upgrade for a cloud template default to "ON"__//
	102	+For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
95	95
96		-{{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}}
	104	+//__Removed an irrelevant refresh button on a flow designer component__//
	105	+We have removed an irrelevant refresh button on the standard filter component.
97	97
98		-//__"Disapprove and go to environment"__//
99		-Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
	107	+//__Notification list shows all notifications on default__//
	108	+When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
100	100
101		-//__Improve readability of API Gateway operations in Create and Deploy__//
102		-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.
	110	+== **Bug fixes ** ==
103	103
104		-//__Add Topic Storage information to License Tracker__//
105		-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.
	112	+//__Keep selection when copying properties__//
	113	+We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
106	106
107		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
	115	+//__Check on security header improved for API Gateway__//
	116	+We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
108	108
109		-//__Add Compatibility check when importing store items__//
110		-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.
	118	+//__Don't show systems with only "external" flows in Design__//
	119	+We fixed a bug that caused systems to appear in Design in cases where there should be none.
111	111
112		-//__Show dependencies between support objects__//
113		-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.
	121	+//__Fix styling of mendix login in some occurences__//
	122	+When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
114	114
115		-//__Improve rendering of validation definition when using multiple namespaces__//
116		-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.
	124	+//__Change timing of wake-up of cloud slots on Friday__//
	125	+To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
117	117
118		-//__Improved help texts on next-generation runtime functionality across the portal__//
119		-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.
	127	+//__Fixed a typo in the Topic statistics overview__//
	128	+We fixed a typo in the topic statistics overview.
120	120
121		-== **Bug Fixes** ==
	130	+//__Fixed a typo in the HTTP statistics overview__//
	131	+We fixed a typo in the HTTP statistics overview.
122	122
123		-//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
124		-With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further.
	133	+//__Activatation of release history when executing a deployment__//
	134	+We ensured that the release history is activated when executing a deployment.
125	125
126		-//__Show information in the Exception of error messages overview__//
127		-With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show.
128		-
129		-//__Improve styling of cron trigger configuration pop-up__//
130		-The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again.
131		-
132		-//__Prevent flow editing locks in specific situations__//
133		-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.
134		-
135		-//__Generate property value empties the runtime selection__//
136		-With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
137		-
138		-//__Make sure nothing of a system message is editable from your exit__//
139		-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.
140		-
141		-//__Prevent users without view rights from seeing a weird screen in those phases__//
142		-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.
143		-
144		-//__Name of starting point of the flow test is incorrect__//
145		-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.
146		-
147		-//__Audit Trail on User Management could break__//
148		-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.
149		-
150		-//__Progress bar in the license tracker is shown twice__//
151		-With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
152		-
153		-//__Compare flows with support objects in the new flow designer__//
154		-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.
155		-
156	156	== **Fancy Forum Answers** ==
157	157
158	158	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:
159	159
160		-* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
161		-* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
	140	+* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
	141	+* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
	142	+* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
162	162
163	163	== **Key takeaways** ==
164	164