Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-216 - Hack Heaven
	1	+205 - World Explorers

Author

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

Content

...	...	@@ -1,34 +1,71 @@
1		-As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions.
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}(((
	3	+[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]].
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
4	4
5		-=====New features=====
6		-* When deploying the on-premise agent for an on-premise machine, users now have the option to select “Multiple environments” when the selected OS-type is Windows. This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture), to the same on-premise machine (the ‘physical’ machine) that are running Windows Server 2022 as an operating system was not possible. Now we have implemented a fix that will allow users to run these multi-environment setups on their Windows Server 2022 machines.
	7	+== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
7	7
8		-=====Minor changes=====
	9	+As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
9	9
10		-* Capture - Generic: When deleting a system, tenant or integration, more information is provided on what you are deleting (#1174)
11		-* Create - Transformation: An optional list in JSON will only create a list if there are items for that list. Otherwise, no list will be created by default. (#941)
12		-* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the name of the property. (#1175)
13		-* Create - Flow designer: When specifying a cron trigger in an inbound component, the validity of the cron is checked to ensure that no issues with the expression occur after deploying the flow version. (#1165)
14		-* Create - Settings: Warning pop-up that is shown when you try to migrate your JMS server to 3rd Generation runtime and there are other containers that need to be migrated first shows the list of other containers. (#1248)
15		-* Deploy - Releases: Implemented some usability improvements in Deploy > Releases. Users can now select the flow version of the infra flows (for each pattern respectively) by right-clicking the light-green eMagiz platform component (much like in Create). When the infra flow version has been edited in a release, the platform will color light-blue to signify this change in infra version. Additionally, the context menu containing the versions also shows a caption now to show what exact component has been right clicked and whose flow versions are showing (entry/exit/onramp/offramp/etc.)
16		-* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144)
17		-* Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits, and show a message that changes are pending. (#1079)
18		-* Deploy - Architecture: Pending changes will now block continueing after pressing “Apply to environment”, instead of when pressing “Apply Changes” in the next screen. (#606)
19		-* Manage - Monitoring: progress bar is added when users haves long searches on “Log entries”. (#1133)
20		-* Manage - Alerting - Triggers - New: It is now possible to filter across Queues, Topics, Recipients and Runtimes when adding a new trigger. (#1089)
21		-* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)
22		-* Catalog: Topics are now sorted alphabetically (#1231)
	11	+== **Feedback Items** ==
23	23
24		-====Bug fixes====
	13	+//__Improved Validation when migrating to the next-generation architecture__//
	14	+To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
25	25
26		-* Generic: Styling fix has been implemented for the text editor area in some places: QnA forum (posts and answers), Edit store item popup (documentation field) and the Flow > Other > Documentation input field in popup. (#1246)
27		-* Generic: The helptext for the protocols field on the Jetty server and the SSL Web service message sender is now clearer and shows which options are possible. (#1247)
28		-* Create - Transformation: The ‘View’ and ‘Edit’ button under parameters are default behaviour when you are editting. (#1241)
29		-* Create - Transformation: if one attribute rule from “string” to “nonEmptyString” has a filter with type “If exists” and with empty check, then no warning about type incompatible will be generated. For the current transformation with the false positive warnings, clicking “Refresh” button in the right panel will clean them. (#689)
30		-* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164)
31		-* Deploy - Property Overview: Resized window such that all property names are not cut off half way. (#1081)
32		-* Deploy - Runtime Overview: Sorting in status is possible. (#1240)
33		-* Deploy - Releases: We fixed a small styling issue when you edit the release by adding/removing the operations to the system in the API pattern. The cursor “Red stop sign“ and “Green plus“ are showing correctly now. (#788)
34		-* Monitoring - Event streaming statistics: graphs can show up to 30 days.
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	17	+
	18	+//__Improved HTTP Statistics__//
	19	+To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	20	+
	21	+//__Show values on the runtime level in Deploy Architecture__//
	22	+We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	23	+
	24	+{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
	25	+* JMS - The number of queues in the active release.
	26	+* Messaging Container - The number of messaging integrations in the active release.
	27	+* Messaging Connector - The number of messaging integrations related to this system in the active release.
	28	+* API Gateway Container - The number of operations in the active release.
	29	+* Event Streaming Container - The number of event processors in the active release.
	30	+
	31	+There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	32	+
	33	+== **Bug Fixes** ==
	34	+
	35	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	36	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	37	+
	38	+//__Ensure that differing container configurations deploy the correct configuration__//
	39	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	40	+
	41	+//__Remove queurying options in Manage__//
	42	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
	43	+
	44	+== **Fancy Forum Answers** ==
	45	+
	46	+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:
	47	+
	48	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	49	+
	50	+== **Key takeaways** ==
	51	+
	52	+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:
	53	+
	54	+* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	55	+* If you have feedback or ideas for us, talk to the Platypus
	56	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	57	+* Clear your browser cache (Ctrl + Shift + Del)
	58	+* Check out the release notes [here]
	59	+* Start thinking about how the license tracker can aid your development
	60	+* Start thinking about major, minor, and patch
	61	+* Upgrade to the latest build number
	62	+* Keep making great integrations
	63	+
	64	+Let's stay in touch and till next time!
	65	+
	66	+{{info}}
	67	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	68	+
	69	+~*~* Indicates a next-generation-architecture only feature.
	70	+{{/info}})))((({{toc/}}))){{/container}}
	71	+{{/container}}