Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

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

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.eMagiz

Content

...	...	@@ -2,93 +2,148 @@
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 this quarter by focusing on more prominent features and spending a substantial chunk of time 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 the 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 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 these changes, 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-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"]]
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, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}}
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	18	+== **Academy 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	+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.
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.
	22	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	24	+== **Flow Designer Improvements** ==
31	31
32		-== **3rd generation runtime bolstering** ==
	26	+//__See last changed date and changed by on resource level__//
	27	+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.
33	33
34		-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.
	29	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]]
35	35
36		-//__SOAP and REST web services migration, including splitting them__//
37		-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.
	31	+//__See on which other flows a resource is used__//
	32	+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.
38	38
39		-//__Changing SSL settings for 3rd generation runtime models works__//
40		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
	34	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
41	41
42		-//__Improved migration for JMS flows__//
43		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	36	+//__Toggle option to see the generated resource by default__//
	37	+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.
44	44
45		-{{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}}
	39	+== **Feedback items ** ==
46	46
47		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
48		-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.
	41	+We have also solved other feedback items besides the flow designer's critical updates.
49	49
50		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
51		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	43	+//__Redirect to the Manage Dashboard from your model home page__//
	44	+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.
52	52
53		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
54		-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.
	46	+//__Readable entry of a SpEL expression in a flow component__//
	47	+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.
55	55
56		-//__Added "Reset" functionality__//
57		-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.
	49	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
58	58
59		-== **Feedback items ** ==
	51	+//__Keep Create and the Create Phase release in sync__//
	52	+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.
60	60
61		-We have also solved other feedback items besides the flow designer's critical updates.
	54	+//__Mask password values in the unused properties overview__//
	55	+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.
62	62
63		-//__Improved naming convention on Store related pages__//
64		-We have improved various display names using the merge functionality within our store offering.
	57	+//__Press Enter to Search for properties__//
	58	+With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
65	65
66		-//__Update security protocols for our internal architecture__//
67		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
	60	+//__Styling update on tag selection on integration level__//
	61	+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.
68	68
69		-//__Improved read-only description for "if exists" constructions in Transformations__//
70		-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.
	63	+//__Enter to close automated flow testing pop-up__//
	64	+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.
71	71
	66	+//__Improved naming of downloaded Event Streaming keystore__//
	67	+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.
72	72
73		-== **Bug fixes ** ==
	69	+//__Pop out on the Traces tab within Flow Testing__//
	70	+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.
74	74
75		-//__Decent validation feedback when not filling in the property value__//
76		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
	72	+//__Sorting User Management__//
	73	+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.
77	77
78		-//__Incorrect resource locations__//
79		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	75	+//__Improved warning on passthrough API operation__//
	76	+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.
80	80
81		-//__Apply to environment in User Management performance improvement__//
82		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	78	+//__Improved update functionality of Swagger file when changing data model__//
	79	+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.
83	83
	81	+{{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}}
	82	+
	83	+//__"Disapprove and go to environment"__//
	84	+Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
	85	+
	86	+//__Improve readability of API Gateway operations in Create and Deploy__//
	87	+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.
	88	+
	89	+//__Add Topic Storage information to License Tracker__//
	90	+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.
	91	+
	92	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
	93	+
	94	+//__Add Compatibility check when importing store items__//
	95	+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.
	96	+
	97	+//__Show dependencies between support objects__//
	98	+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.
	99	+
	100	+//__Improve rendering of validation definition when using multiple namespaces__//
	101	+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.
	102	+
	103	+//__Improved help texts on next-generation runtime functionality across the portal__//
	104	+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.
	105	+
	106	+== **Bug Fixes** ==
	107	+
	108	+//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
	109	+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.
	110	+
	111	+//__Show information in the Exception of error messages overview__//
	112	+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.
	113	+
	114	+//__Improve styling of cron trigger configuration pop-up__//
	115	+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.
	116	+
	117	+//__Prevent flow editing locks in specific situations__//
	118	+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.
	119	+
	120	+//__Generate property value empties the runtime selection__//
	121	+With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
	122	+
	123	+//__Make sure nothing of a system message is editable from your exit__//
	124	+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.
	125	+
	126	+//__Prevent users without view rights from seeing a weird screen in those phases__//
	127	+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.
	128	+
	129	+//__Name of starting point of the flow test is incorrect__//
	130	+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.
	131	+
	132	+//__Audit Trail on User Management could break__//
	133	+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.
	134	+
	135	+//__Progress bar in the license tracker is shown twice__//
	136	+With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
	137	+
	138	+//__Compare flows with support objects in the new flow designer__//
	139	+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.
	140	+
84	84	== **Fancy Forum Answers** ==
85	85
86	86	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:
87	87
88		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
89		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
90		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
91		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
	145	+* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
	146	+* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
92	92
93	93	== **Key takeaways** ==
94	94