Changes for page 241 - Wild West

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-241 - Wild West
	1	+217 - Template Tango

Author

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

Content

...	...	@@ -1,31 +1,14 @@
1		-In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
	1	+In the last sprint cycle, we focused on delivering new cloud templates for docker single and docker double lane. Moreover, we have added clipboard buttons to several pages, and migrated the generic alert trigger "More than 100 messages on queue over 10 minutes" to a dynamic trigger. Lastly, we enabled the removal of eMagiz infra H2 databases for connector machines, and improved the checks on the runtime versions in the runtime overview.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
4	4
5		-====Minor Changes====
	5	+====New features====
6	6
7		-* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8		-* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608)
9		-* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually.
10		-* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11		-* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12		-* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
	7	+* Create - Flow Designer: Copy to clipboard buttons have been added to various pages.
	8	+* Deploy - Releases: Copy to clipboard buttons have been added to various pages.
	9	+* Deploy - Architecture: For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed. To use this new functionality, new Cloud Templates are available in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for single and double environments. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	10	+* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
13	13
14	14	====Bug fixes====
15	15
16		-* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17		-* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18		-* Design - Message Definition: small improvements are introduced:
19		-** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20		-** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21		-* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597)
22		-* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
23		-* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24		-* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
25		-* Create - Components: The browser page now displays the correct page title (#1509)
26		-* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27		-* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
28		-* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526)
29		-* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30		-* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408)
31		-* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)
	14	+* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)