Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+216 - Hack Heaven

Content

...	...	@@ -1,79 +1,124 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
	5	+
	6	+**Hi there, eMagiz developers!** 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. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
	8	+== ** Announcement - TLS versions deprecated** ==
6	6
7		-== **Release Properties** ==
8		-As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
	10	+Placeholder for info from Bas
9	9
10		-* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11		-* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12		-* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13		-* A, for most, new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
	12	+{{info}}Text{{/info}}
14	14
15		-{{info}}For more information, please check out the following microlearnings:
	14	+== **Announcement - Spring 6** ==
16	16
17		-* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18		-* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19		-* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
	16	+Placeholder for info from Jelle
20	20
21		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22		-{{/info}}
	18	+{{warning}}Text{{/warning}}
23	23
24		-== ** Manage - Graphs improvements ~*~* ** ==
25		-As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
	20	+== **Infra flow selection** ==
26	26
27		-[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
	22	+This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually.
28	28
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	25	+
	26	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
	27	+
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	29	+
	30	+We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release.
	31	+
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	33	+
	34	+== **Multiple environments selection** ==
	35	+
	36	+{{warning}}The following is only applicable under the following conditions:
	37	+ * Windows 2022 server
	38	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
	39	+
	40	+When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
	41	+
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	43	+
29	29	== **Feedback Items** ==
	45	+//__Easier component selection in flow designer__//
	46	+The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
30	30
31		-//__Improved editability when testing in eMagiz without Edit rights in Create__//
32		-Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
	48	+//__Improved handling of optionality in JSON on lists__//
	49	+Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties.
33	33
34		-//__Improved auditability on Deploy Architecture__//
35		-To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
	51	+With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired.
36	36
37		-//__Test your own exported store content__//
38		-We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
	53	+//__Loading bar when searching for log entries__//
	54	+To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.
39	39
40		-{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
	56	+//__Improved feedback when deleting elements from Capture__//
	57	+To better specify to the user which integration or system the user intends to delete, we have improved the text in the confirmation pop-up. This way, we can provide more information to the user to avoid mistakes.
41	41
42		-//__Improved comparison of flows in the releases overview__//
43		-We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
	59	+//__Enhanced filter options in Manage__//
	60	+With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
44	44
	62	+//__Copy property names from Create__//
	63	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	64	+
	65	+//__Improved feedback during migration to the current runtime architecture__//
	66	+Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order.
	67	+
	68	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	69	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	70	+
	71	+//__Cron trigger validation__//
	72	+We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
	73	+
45	45	== **Bug Fixes** ==
	75	+//__Making Edit (and View) the default action when configuring parameters__//
	76	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
46	46
47		-//__Improved validation on XPath header enricher__//
48		-To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
	78	+//__Property configuration pop-up resized__//
	79	+We have resized the property configuration overviews to make the property value better readable.
49	49
50		-//__Cancel behavior on flow testing property overview fixed__//
51		-We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
	81	+//__Alphabetically sorted components in the flow designer__//
	82	+As of this release, we now sort the components alphabetically in the flow designer.
52	52
53		-//__Cancel behavior on flow fragment level when exporting store content__//
54		-We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
	84	+//__Improved sorting on runtime overview__//
	85	+As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
55	55
56		-//__Adding numbers on containers in Deploy Architecture__//
57		-With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
	87	+//__Improved sorting on catalog overview__//
	88	+As of this release, we now sort the topics in the catalog by name.
58	58
	90	+//__Styling fix on rich text editors__//
	91	+Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
	92	+
	93	+//__Styling fix on release edit__//
	94	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	95	+
	96	+//__Removed false-positive alerts on transformations__//
	97	+When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation.
	98	+
	99	+//__Event Streaming Graphs - view thirty days back__//
	100	+Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further.
	101	+
	102	+//__Improved helptext__//
	103	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	104	+
59	59	== **Fancy Forum Answers** ==
60	60
61	61	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:
62	62
63		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	109	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
64	64
65		-== **Key takeaways** ==
	111	+== **Key Takeaways** ==
66	66
67		-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:
	113	+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:
68	68
69	69	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70	* If you have feedback or ideas for us, talk to the Platypus
71		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	117	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73	73	* Check out the release notes [here]
74	74	* Start thinking about how the license tracker can aid your development
75	75	* Start thinking about major, minor, and patch
76		-* Upgrade to the latest build number
77	77	* Keep making great integrations
78	78
79	79	Let's stay in touch and till next time!
...	...	@@ -81,6 +81,11 @@
81	81	{{info}}
82	82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83
84		-~*~* Indicates a next-generation-architecture only feature.
85		-{{/info}})))((({{toc/}}))){{/container}}
	129	+{{/info}}
	130	+)))
	131	+
	132	+(((
	133	+{{toc/}}
	134	+)))
86	86	{{/container}}
	136	+{{/container}}