Changes for page 190 - Fast Forward

Summary

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

Details

Page properties

Content

...	...	@@ -66,29 +66,29 @@
66	66	//__Auto-fill namespaces for SOAP hosted webservices__//
67	67	Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
68	68
69		-//__Updated H2 database setting__//
70		-As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
	69	+{{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}}
71	71
72		-{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
	71	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	72	+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.
73	73
74		-//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
75		-As a replacement of the current HTTP settings context menu we have added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service) you now also can define whether the control bus needs to work for this runtime.
	74	+//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
	75	+We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
76	76
77		-//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
78		-With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
	77	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	78	+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.
79	79
80		-//__Performance improvement creating a release__//
81		-With this release, we have improved the performance of creating a release.
	80	+//__Added "Reset" functionality__//
	81	+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.
82	82
83	83	== **Feedback items ** ==
84	84
85	85	We have also solved other feedback items besides the flow designer's critical updates.
86	86
87		-//__Sensitive information stored in properties is masked __//
88		-We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
	87	+//__Improved naming convention on Store related pages__//
	88	+We have improved various display names using the merge functionality within our store offering.
89	89
90		-//__Confirmation pop-up displaying whether your topology changes in Deploy Architecture__//
91		-To give the user additional feedback of what will happen on the cloud slot when the user presses "Apply to environment" we have now added a confirmation pop-up that is shown when you migrate from the current runtime architecture to the 3rd generation runtime.
	90	+//__Update security protocols for our internal architecture__//
	91	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
92	92
93	93	//__Improved read-only description for "if exists" constructions in Transformations__//
94	94	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.
...	...	@@ -96,11 +96,11 @@
96	96
97	97	== **Bug fixes ** ==
98	98
99		-//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
100		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
	99	+//__Decent validation feedback when not filling in the property value__//
	100	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
101	101
102		-//__Synchronization of Event Streaming topic states__//
103		-We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
	102	+//__Incorrect resource locations__//
	103	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
104	104
105	105	//__Apply to environment in User Management performance improvement__//
106	106	We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.