Changes for page 194 - Giant Leap

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-185 - Get ready
	1	+186 - Daemon Switch

Author

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

Content

...	...	@@ -2,46 +2,149 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
	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		-==**Audit trail User Management**==
8		-Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
9		-
10		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
	7	+== **New monitoring stack** ==
11	11
12		-==**Next Generation Monitoring & Alerting engine**==
13		-In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
14		-
15		-* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16		-* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17		-* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18		-* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19		-* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
20		-
21		-
22		-=== **Improvements** ===
23		-
24		-* Performance Deployment plan
25		-When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26		-
27		-* Flow Designer updates
28		-We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29		-
30		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31		-
32		-* Store
33		-We have fixed several smaller Store import issues to improve the user experience.
34		-
	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	+
	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"]]
	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, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}}
	17	+
	18	+== **Academy improvements** ==
	19	+
	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.
	21	+
	22	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
	23	+
	24	+== **Flow Designer Improvements** ==
	25	+
	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.
	28	+
	29	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]]
	30	+
	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.
	33	+
	34	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
	35	+
	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.
	38	+
	39	+== **Feedback items ** ==
	40	+
	41	+We have also solved other feedback items besides the flow designer's critical updates.
	42	+
	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.
	45	+
	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.
	48	+
	49	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
	50	+
	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.
	53	+
	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.
	56	+
	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.
	59	+
	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.
	62	+
	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.
	65	+
	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.
	68	+
	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.
	71	+
	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.
	74	+
	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.
	77	+
	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.
	80	+
	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	+//__Add Compatibility check when importing store items__//
	93	+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.
	94	+
	95	+//__Show dependencies between support objects__//
	96	+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.
	97	+
	98	+//__Improve rendering of validation definition when using multiple namespaces__//
	99	+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.
	100	+
	101	+== **Bug Fixes** ==
	102	+
	103	+//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
	104	+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.
	105	+
	106	+//__Show information in the Exception of error messages overview__//
	107	+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.
	108	+
	109	+//__Improve styling of cron trigger configuration pop-up__//
	110	+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.
	111	+
	112	+//__Prevent flow editing locks in specific situations__//
	113	+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.
	114	+
	115	+//__Generate property value empties the runtime selection__//
	116	+With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
	117	+
	118	+//__Make sure nothing of a system message is editable from your exit__//
	119	+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.
	120	+
	121	+//__Prevent users without view rights from seeing a weird screen in those phases__//
	122	+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.
	123	+
	124	+//__name of starting point of the flow test is incorrect__//
	125	+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.
	126	+
	127	+//__Audit Trail on User Management could break__//
	128	+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.
	129	+
	130	+//__Progress bar in the license tracker is shown twice__//
	131	+With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
	132	+
	133	+//__Compare flows with support objects in the new flow designer__//
	134	+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.
	135	+
35	35	== **Fancy Forum Answers** ==
36	36
37		-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:
	138	+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:
38	38
39		-* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40		-* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
	140	+* [[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"]]
	141	+* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
	142	+* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
41	41
	144	+
42	42	== **Key takeaways** ==
43	43
44		-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:
	147	+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:
45	45
46	46	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47	47	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -52,12 +52,11 @@
52	52	* Start thinking about major, minor, and patch
53	53	* Upgrade to the latest build number
54	54	* Keep making great integrations
55		-* Check out the new documentation portal.
56	56
57	57	Let's stay in touch and till next time!
58	58
59	59	{{info}}
60		-~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	162	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61
62	62	~*~* Indicates a GEN3-only feature.
63	63	{{/info}})))((({{toc/}}))){{/container}}