Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+206 - Situational Deployment

Author

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

Content

...	...	@@ -2,150 +2,110 @@
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 few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **Store - Next phase** ==
	7	+== **Deployment Plan** ==
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	+//__Improved deployment plan to make the process better and more predictable__//
	10	+The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
10	10
11		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
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}}
	15	+//__JMS memory setting check__//
	16	+A change in memory settings triggers redeployment of the container now.
14	14
15		-== **New eMagiz Mendix Connector** ==
	18	+//__Properties tab__//
	19	+We have removed the deprecated tab Properties in the Deploy phase.
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	+//__Cleanup old images__//
	22	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
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}}
	24	+//__Performance improvements for loading releases__//
	25	+Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
20	20
21		-== **Flow version restore** ~* ==
	27	+== **Store Improvements** ==
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.
	29	+//__Message definition elements order__//
	30	+We fixed an issue that the order of message definition elements was changed after being imported.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	32	+//__Importing a store item with synchronous message definitions__//
	33	+We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
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	+//__Importing store items containing static copies__//
	36	+We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
32	32
33		-== **Feedback items ** ==
	38	+//__Importing Store content__//
	39	+We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
34	34
35		-We have also solved other feedback items besides the flow designer's critical updates.
	41	+//__Store disclaimer__//
	42	+Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
36	36
37		-//__Redirect to the Manage Dashboard from your model home page__//
38		-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.
	44	+== **Feedback Items** ==
39	39
40		-//__Readable entry of a SpEL expression in a flow component__//
41		-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.
	46	+//__Alerting manual pause__//
	47	+A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
42	42
43		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
	49	+//__Ordering of graphs in Manage__//
	50	+The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
44	44
45		-//__Keep Create and the Create Phase release in sync__//
46		-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.
	52	+//__UTC times in Grafana panels__//
	53	+All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
47	47
48		-//__Mask password values in the unused properties overview__//
49		-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.
	55	+//__Update flow designer version__//
	56	+The framework used in the flow designer has been updated to the latest version.
50	50
51		-//__Press Enter to Search for properties__//
52		-With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
	58	+//__Carwash track TLS versions in logging__//
	59	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
53	53
54		-//__Styling update on tag selection on integration level__//
55		-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.
	61	+//__Moving channels in the flow designer__//
	62	+Moving already attached channels in the flow designer has been made sligthly easier.
56	56
57		-//__Enter to close automated flow testing pop-up__//
58		-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.
	64	+//__Topic sizes description change__//
	65	+In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
59	59
60		-//__Improved naming of downloaded Event Streaming keystore__//
61		-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.
	67	+//__Password change notification__//
	68	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
62	62
63		-//__Pop out on the Traces tab within Flow Testing__//
64		-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.
	70	+//__Password comparison__//
	71	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
65	65
66		-//__Sorting User Management__//
67		-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.
	73	+//__Inactive user alerting__//
	74	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
68	68
69		-//__Improved warning on passthrough API operation__//
70		-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.
	76	+//__Alphabetical sorting on user level in HTTP statistics__//
	77	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
71	71
72		-//__Improved update functionality of Swagger file when changing data model__//
73		-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.
	79	+//__SOAP Web services path__//
	80	+Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
74	74
75		-{{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}}
76		-
77		-//__"Disapprove and go to environment"__//
78		-Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
79		-
80		-//__Improve readability of API Gateway operations in Create and Deploy__//
81		-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.
82		-
83		-//__Add Topic Storage information to License Tracker__//
84		-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.
85		-
86		-[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
87		-
88		-//__Add Compatibility check when importing store items__//
89		-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.
90		-
91		-//__Show dependencies between support objects__//
92		-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.
93		-
94		-//__Improve rendering of validation definition when using multiple namespaces__//
95		-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.
96		-
97		-//__Improved help texts on next-generation runtime functionality across the portal__//
98		-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.
99		-
100	100	== **Bug Fixes** ==
101	101
102		-//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
103		-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.
	84	+//__Flow designer styling__//
	85	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
104	104
105		-//__Show information in the Exception of error messages overview__//
106		-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.
	87	+//__Partial search for messages__//
	88	+It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
107	107
108		-//__Improve styling of cron trigger configuration pop-up__//
109		-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.
	90	+//__Disk usage after cloud template update__//
	91	+In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
110	110
111		-//__Prevent flow editing locks in specific situations__//
112		-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.
	93	+//__Error handling migration__//
	94	+If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
113	113
114		-//__Generate property value empties the runtime selection__//
115		-With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
116		-
117		-//__Make sure nothing of a system message is editable from your exit__//
118		-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.
119		-
120		-//__Prevent users without view rights from seeing a weird screen in those phases__//
121		-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.
122		-
123		-//__Name of starting point of the flow test is incorrect__//
124		-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.
125		-
126		-//__Audit Trail on User Management could break__//
127		-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.
128		-
129		-//__Progress bar in the license tracker is shown twice__//
130		-With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
131		-
132		-//__Compare flows with support objects in the new flow designer__//
133		-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.
134		-
135	135	== **Fancy Forum Answers** ==
136	136
137	137	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:
138	138
139		-* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
140		-* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
	100	+* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
141	141
142	142	== **Key takeaways** ==
143	143
144		-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:
	104	+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:
145	145
146	146	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
147	147	* If you have feedback or ideas for us, talk to the Platypus
148		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	108	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
149	149	* Clear your browser cache (Ctrl + Shift + Del)
150	150	* Check out the release notes [here]
151	151	* Start thinking about how the license tracker can aid your development
...	...	@@ -158,6 +158,6 @@
158	158	{{info}}
159	159	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
160	160
161		-~*~* Indicates a GEN3-only feature.
	121	+~*~* Indicates a next-generation-architecture only feature.
162	162	{{/info}})))((({{toc/}}))){{/container}}
163	163	{{/container}}