Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+216 - Hack Heaven

Content

...	...	@@ -1,85 +1,136 @@
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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. 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		-== **Private Store** ==
8		-On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
	8	+== ** Announcement - TLS versions deprecated** ==
9	9
10		-{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
	10	+Placeholder for info from Bas
11	11
12		-== **3rd generation runtime bolstering** ==
	12	+{{info}}Text{{/info}}
13	13
14		-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.
	14	+== **Announcement - Spring 6** ==
15	15
16		-//__SOAP and REST web services migration including splitting them__//
17		-With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
	16	+In the next release, we expect to release a major version of our current runtime base image. 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.
18	18
19		-//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
	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 changes. 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 especially important 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 version changes and the Spring version changes, 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	+** In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes
	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}}
21	21
22		-//__Improved migration for JMS flows__//
23		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24	24
25		-{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
	32	+== **Infra flow selection** ==
26	26
27		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28		-As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
	34	+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.
29	29
30		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	36	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
32	32
33		-== **Feedback items ** ==
	38	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
34	34
35		-We have also solved other feedback items besides the flow designer's critical updates.
	40	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
36	36
37		-//__Improved naming convention on Store related pages__//
38		-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.
	42	+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.
39	39
40		-//__Press "Enter" to search on multiple pages__//
41		-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.
	44	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
42	42
43		-* Deploy → Deployment Plan
44		-* Deploy → Properties → History
45		-* Deploy → User Management → Roles
46		-* Manage → Error Messages → Error Messages
47		-* Manage → Error Messages → Flows with Error Messages
48		-* Manage → Error Messages → Exceptions of Error Messages
49		-* Manage → Log Entries
50		-* Manage → Alerts
51		-* Manage → Triggers
52		-* Manage → Tags – Cant find (only Gen2)
53		-* Manage → Notifications
54		-* Manage → Notification Settings
55		-* Manage → Data Usage → History
56		-* Manage → Code mappings → All tabs
	46	+== **Multiple environments selection** ==
57	57
58		-== **Bug fixes ** ==
	48	+{{warning}}The following is only applicable under the following conditions:
	49	+ * Windows 2022 server
	50	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
59	59
60		-//__Loading problems of Deployment plan execution overview__//
61		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
	52	+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.
62	62
	54	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	55	+
	56	+== **Feedback Items** ==
	57	+//__Easier component selection in flow designer__//
	58	+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.
	59	+
	60	+//__Improved handling of optionality in JSON on lists__//
	61	+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.
	62	+
	63	+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.
	64	+
	65	+//__Loading bar when searching for log entries__//
	66	+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.
	67	+
	68	+//__Improved feedback when deleting elements from Capture__//
	69	+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.
	70	+
	71	+//__Enhanced filter options in Manage__//
	72	+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.
	73	+
	74	+//__Copy property names from Create__//
	75	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	76	+
	77	+//__Improved feedback during migration to the current runtime architecture__//
	78	+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.
	79	+
	80	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	81	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	82	+
	83	+//__Cron trigger validation__//
	84	+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.
	85	+
	86	+== **Bug Fixes** ==
	87	+//__Making Edit (and View) the default action when configuring parameters__//
	88	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
	89	+
	90	+//__Property configuration pop-up resized__//
	91	+We have resized the property configuration overviews to make the property value better readable.
	92	+
	93	+//__Alphabetically sorted components in the flow designer__//
	94	+As of this release, we now sort the components alphabetically in the flow designer.
	95	+
	96	+//__Improved sorting on runtime overview__//
	97	+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.
	98	+
	99	+//__Improved sorting on catalog overview__//
	100	+As of this release, we now sort the topics in the catalog by name.
	101	+
	102	+//__Styling fix on rich text editors__//
	103	+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.
	104	+
	105	+//__Styling fix on release edit__//
	106	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	107	+
	108	+//__Removed false-positive alerts on transformations__//
	109	+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.
	110	+
	111	+//__Event Streaming Graphs - view thirty days back__//
	112	+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.
	113	+
	114	+//__Improved helptext__//
	115	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	116	+
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	121	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
70	70
71		-== **Key takeaways** ==
	123	+== **Key Takeaways** ==
72	72
73		-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:
	125	+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:
74	74
75	75	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76	76	* If you have feedback or ideas for us, talk to the Platypus
77		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	129	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78	78	* Clear your browser cache (Ctrl + Shift + Del)
79	79	* Check out the release notes [here]
80	80	* Start thinking about how the license tracker can aid your development
81	81	* Start thinking about major, minor, and patch
82		-* Upgrade to the latest build number
83	83	* Keep making great integrations
84	84
85	85	Let's stay in touch and till next time!
...	...	@@ -87,6 +87,11 @@
87	87	{{info}}
88	88	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89	89
90		-~*~* Indicates a GEN3-only feature.
91		-{{/info}})))((({{toc/}}))){{/container}}
	141	+{{/info}}
	142	+)))
	143	+
	144	+(((
	145	+{{toc/}}
	146	+)))
92	92	{{/container}}
	148	+{{/container}}