Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-216 - Hack Heaven
	1	+187 - Integration Sponsor

Content

...	...	@@ -1,136 +1,164 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	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.
	5	+**Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.
7	7
8		-== ** Announcement - TLS versions deprecated** ==
	7	+== **Store - Next phase** ==
9	9
10		-Placeholder for info from Bas
	9	+This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier. For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].
11	11
12		-{{info}}Text{{/info}}
	11	+== **Flow version restore** ~* ==
13	13
14		-== **Announcement - Spring 6** ==
	13	+On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect.
15	15
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.
	15	+{{warning}}Note, that the following restrictions apply when restoring to a previous version:
	16	+ * Changes made on definition and transformation level are **not** restored
	17	+ * You will not be able to restore to any flow version that was created before October 17th, 2022
	18	+ * You will not be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back{{/warning}}
17	17
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}}
	20	+== **Academy improvements** ==
30	30
	22	+On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning.
31	31
32		-== **Infra flow selection** ==
	24	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
33	33
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.
	26	+== **Flow Designer Improvements** ==
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	28	+//__See last changed date and changed by on resource level__//
	29	+This release will reinstate the ability to see who changed a resource last and when it was changed for the last time. You can find this information by double-clicking on a resource or viewing its details via the view button.
37	37
38		-In edit mode, you can select a new version via the right-click option, which you already use for other flows.
	31	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]]
39	39
40		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	33	+//__See on which other flows a resource is used__//
	34	+This release will reinstate the ability to see whether a resource is used in other flows within your model or not. This will help to determine the impact of a specific change.
41	41
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.
	36	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
43	43
44		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	38	+//__Toggle option to see the generated resource by default__//
	39	+Upon request, we have made the toggle for the generated resources in the new flow designer user-dependent. This means that you, as a user, can determine that the toggle should also be on. This means that the generated resources will be shown to you when opening any flow in eMagiz. When you switch the toggle off, this will mean that you will **not** see the generated resources by default.
45	45
46		-== **Multiple environments selection** ==
	41	+== **Feedback items ** ==
47	47
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}}
	43	+We have also solved other feedback items besides the flow designer's critical updates.
51	51
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.
	45	+//__Redirect to the Manage Dashboard from your model home page__//
	46	+Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase.
53	53
54		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	48	+//__Readable entry of a SpEL expression in a flow component__//
	49	+As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions.
55	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.
	51	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
59	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.
	53	+//__Keep Create and the Create Phase release in sync__//
	54	+Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening.
62	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.
	56	+//__Mask password values in the unused properties overview__//
	57	+All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview.
64	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.
	59	+//__Press Enter to Search for properties__//
	60	+With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
67	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.
	62	+//__Styling update on tag selection on integration level__//
	63	+With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly.
70	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.
	65	+//__Enter to close automated flow testing pop-up__//
	66	+Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button.
73	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.
	68	+//__Improved naming of downloaded Event Streaming keystore__//
	69	+When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client.
76	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.
	71	+//__Pop out on the Traces tab within Flow Testing__//
	72	+In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow.
79	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.
	74	+//__Sorting User Management__//
	75	+As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview.
82	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.
	77	+//__Improved warning on passthrough API operation__//
	78	+Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create.
85	85
	80	+//__Improved update functionality of Swagger file when changing data model__//
	81	+Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly.
	82	+
	83	+{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}}
	84	+
	85	+//__"Disapprove and go to environment"__//
	86	+Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
	87	+
	88	+//__Improve readability of API Gateway operations in Create and Deploy__//
	89	+When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation.
	90	+
	91	+//__Add Topic Storage information to License Tracker__//
	92	+On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz.
	93	+
	94	+[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
	95	+
	96	+//__Add Compatibility check when importing store items__//
	97	+We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening.
	98	+
	99	+//__Show dependencies between support objects__//
	100	+As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects.
	101	+
	102	+//__Improve rendering of validation definition when using multiple namespaces__//
	103	+With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end.
	104	+
	105	+//__Improved help texts on next-generation runtime functionality across the portal__//
	106	+With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime.
	107	+
86	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	89
90		-//__Property configuration pop-up resized__//
91		-We have resized the property configuration overviews to make the property value better readable.
	110	+//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
	111	+With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further.
92	92
93		-//__Alphabetically sorted components in the flow designer__//
94		-As of this release, we now sort the components alphabetically in the flow designer.
	113	+//__Show information in the Exception of error messages overview__//
	114	+With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show.
95	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.
	116	+//__Improve styling of cron trigger configuration pop-up__//
	117	+The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again.
98	98
99		-//__Improved sorting on catalog overview__//
100		-As of this release, we now sort the topics in the catalog by name.
	119	+//__Prevent flow editing locks in specific situations__//
	120	+There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release.
101	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.
	122	+//__Generate property value empties the runtime selection__//
	123	+With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
104	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."
	125	+//__Make sure nothing of a system message is editable from your exit__//
	126	+Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices.
107	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.
	128	+//__Prevent users without view rights from seeing a weird screen in those phases__//
	129	+With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently.
110	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.
	131	+//__Name of starting point of the flow test is incorrect__//
	132	+With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct.
113	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.
	134	+//__Audit Trail on User Management could break__//
	135	+When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue.
116	116
	137	+//__Progress bar in the license tracker is shown twice__//
	138	+With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
	139	+
	140	+//__Compare flows with support objects in the new flow designer__//
	141	+We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer.
	142	+
117	117	== **Fancy Forum Answers** ==
118	118
119	119	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:
120	120
121		-* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	147	+* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
	148	+* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
122	122
123		-== **Key Takeaways** ==
	150	+== **Key takeaways** ==
124	124
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:
	152	+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:
126	126
127	127	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
128	128	* If you have feedback or ideas for us, talk to the Platypus
129		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	156	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
130	130	* Clear your browser cache (Ctrl + Shift + Del)
131	131	* Check out the release notes [here]
132	132	* Start thinking about how the license tracker can aid your development
133	133	* Start thinking about major, minor, and patch
	161	+* Upgrade to the latest build number
134	134	* Keep making great integrations
135	135
136	136	Let's stay in touch and till next time!
...	...	@@ -138,11 +138,6 @@
138	138	{{info}}
139	139	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
140	140
141		-{{/info}}
142		-)))
143		-
144		-(((
145		-{{toc/}}
146		-)))
	169	+~*~* Indicates a GEN3-only feature.
	170	+{{/info}})))((({{toc/}}))){{/container}}
147	147	{{/container}}
148		-{{/container}}