Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+216 - Hack Heaven

Content

...	...	@@ -1,88 +1,135 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
	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.
6	6
7		-== **3rd generation runtime bolstering** ==
	8	+== ** Announcement - TLS versions deprecated** ==
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	10	+Placeholder for info from Bas
10	10
11		-//__Migration of JMS backup configuration improved__//
12		-With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
	12	+{{info}}Text{{/info}}
13	13
14		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15		-As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
	14	+== **Announcement - Spring 6** ==
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	16	+We expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture in the next release. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
19	19
20		-//__Code mapping functionality available on 3rd generation runtime__//
21		-As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
	18	+{{warning}}
	19	+* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
	20	+* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
	21	+** Simple job launcher (data pipelines)
	22	+** Job explorer (data pipelines)
	23	+** HTTP components message sender (support object)
	24	+** Web service outbound gateway (with a 'message sender' attribute specified)
	25	+** SFTP session factory (support object)
	26	+** API gateways with OAuth2 as security mechanism.
	27	+* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
	28	+** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. The release notes of the base image will specify the changes in more detail.
	29	+* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
22	22
23		-//__Improved the performance when activating a release__//
24		-With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
	31	+== **Infra flow selection** ==
25	25
26		-//__Failing runtimes won't be restarted indefinitely anymore__//
27		-We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
	33	+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
29		-== **Exportable Release Audit** ~* ==
	35	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
30	30
31		-On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	37	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
32	32
33		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	39	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
34	34
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Works **only** for releases that are promoted and made active on **Production**
37		- * You will **only** see changes made during the **current** calendar year
38		- * On the first of April all objects of the **last** calendar year will be **removed**.
39		- ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	41	+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.
40	40
41		-== **Feedback items ** ==
	43	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
42	42
43		-We have also solved other feedback items besides the flow designer's critical updates.
	45	+== **Multiple environments selection** ==
44	44
45		-//__Improved naming convention on Store related pages__//
46		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
	47	+{{warning}}The following is only applicable under the following conditions:
	48	+ * Windows 2022 server
	49	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
47	47
48		-//__Press "Enter" to search on multiple pages__//
49		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
	51	+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.
50	50
51		-* Deploy → Deployment Plan
52		-* Deploy → Properties → History
53		-* Deploy → User Management → Roles
54		-* Manage → Error Messages → Error Messages
55		-* Manage → Error Messages → Flows with Error Messages
56		-* Manage → Error Messages → Exceptions of Error Messages
57		-* Manage → Log Entries
58		-* Manage → Alerts
59		-* Manage → Triggers
60		-* Manage → Tags – Cant find (only Gen2)
61		-* Manage → Notifications
62		-* Manage → Notification Settings
63		-* Manage → Data Usage → History
64		-* Manage → Code mappings → All tabs
	53	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
65	65
	55	+== **Feedback Items** ==
	56	+//__Easier component selection in flow designer__//
	57	+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.
	58	+
	59	+//__Improved handling of optionality in JSON on lists__//
	60	+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.
	61	+
	62	+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.
	63	+
	64	+//__Loading bar when searching for log entries__//
	65	+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.
	66	+
	67	+//__Improved feedback when deleting elements from Capture__//
	68	+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.
	69	+
	70	+//__Enhanced filter options in Manage__//
	71	+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.
	72	+
	73	+//__Copy property names from Create__//
	74	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	75	+
	76	+//__Improved feedback during migration to the current runtime architecture__//
	77	+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.
	78	+
	79	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	80	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	81	+
	82	+//__Cron trigger validation__//
	83	+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.
	84	+
	85	+== **Bug Fixes** ==
	86	+//__Making Edit (and View) the default action when configuring parameters__//
	87	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
	88	+
	89	+//__Property configuration pop-up resized__//
	90	+We have resized the property configuration overviews to make the property value better readable.
	91	+
	92	+//__Alphabetically sorted components in the flow designer__//
	93	+As of this release, we now sort the components alphabetically in the flow designer.
	94	+
	95	+//__Improved sorting on runtime overview__//
	96	+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.
	97	+
	98	+//__Improved sorting on catalog overview__//
	99	+As of this release, we now sort the topics in the catalog by name.
	100	+
	101	+//__Styling fix on rich text editors__//
	102	+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.
	103	+
	104	+//__Styling fix on release edit__//
	105	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	106	+
	107	+//__Removed false-positive alerts on transformations__//
	108	+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.
	109	+
	110	+//__Event Streaming Graphs - view thirty days back__//
	111	+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.
	112	+
	113	+//__Improved helptext__//
	114	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	115	+
66	66	== **Fancy Forum Answers** ==
67	67
68	68	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:
69	69
70		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	120	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
73	73
74		-== **Key takeaways** ==
	122	+== **Key Takeaways** ==
75	75
76		-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:
	124	+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:
77	77
78	78	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79	79	* If you have feedback or ideas for us, talk to the Platypus
80		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	128	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81	81	* Clear your browser cache (Ctrl + Shift + Del)
82	82	* Check out the release notes [here]
83	83	* Start thinking about how the license tracker can aid your development
84	84	* Start thinking about major, minor, and patch
85		-* Upgrade to the latest build number
86	86	* Keep making great integrations
87	87
88	88	Let's stay in touch and till next time!
...	...	@@ -90,6 +90,11 @@
90	90	{{info}}
91	91	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92	92
93		-~*~* Indicates a GEN3-only feature.
94		-{{/info}})))((({{toc/}}))){{/container}}
	140	+{{/info}}
	141	+)))
	142	+
	143	+(((
	144	+{{toc/}}
	145	+)))
95	95	{{/container}}
	147	+{{/container}}