Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 239.1
edited by Carlijn Kokkeler
on 2023/10/26 10:36
Change comment: There is no comment for this version
To version 410.1
edited by Erik Bakker
on 2024/03/11 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +216 - Hack Heaven
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,120 +1,90 @@
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, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
4 4  
5 -**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
8 +== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6 6  
7 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
10 +Placeholder for info from Bas
8 8  
9 -== **State Generation~*~*** ==
12 +{{info}}{{/info}}
10 10  
11 -//__New components__//
12 -The following components have been added:
13 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
14 -* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
15 -* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
16 -* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
17 -* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
14 +== **Announcement - Spring 6** ==
18 18  
19 -//__SpEL functions & JSON__//
20 -Added SpEL functions for:
21 -* Encoding & decoding Base64, Hex and hmac.
22 -* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
23 -* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
16 +Placeholder for info from Jelle
24 24  
25 -Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
18 +{{warning}}{{/warning}}
26 26  
27 -Added support for `#JsonPath` usage in SpEL expressions. With this functionality, you can access your JSON payloads in a similar way as you would access XML payloads using [[xPath>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Create your transformations.advanced-create-your-transformations-xpath-advanced||target="blank"]].
20 +== ** Updated release functionality - Infra flow selection** ==
28 28  
29 -{{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
22 +This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
30 30  
31 -{{warning}}The library used for Code Mappings has been changed. Any customer with next generation architecture runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
32 32  
33 -== **Metrics Storage Duration** ==
34 -We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
26 +When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
35 35  
36 -((((% border="3" cellpadding="10" cellspacing="10" style="width:400px" %)
37 -|=(% style="width: 120px;" %)Future|=(% style="width: 180px;" %)Minute level|=(% style="width: 180px;" %)Hour level
38 -|(% style="width:120px" %) Production|(% style="width:180px" %) 30 days|(% style="width:180px" %) 1 year
39 -|(% style="width:120px" %) Acceptance|(% style="width:180px" %) 14 days|(% style="width:180px" %) 6 months
40 -|(% style="width:120px" %) Test|(% style="width:180px" %) 7 days|(% style="width:180px" %) 3 months
41 -)))
28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
42 42  
43 -== **Feedback Items** ==
30 +On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
44 44  
45 -//__Import from store__//
46 -The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
47 47  
48 -//__Save and cancel buttons placement__//
49 -The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
34 +== ** Updated deploy functionality on-premise - Multiple environments selection** ==
50 50  
51 -//__User session times__//
52 -The user session times for next generation architecture dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
36 +{{warning}}The following is only applicable under the following conditions:
37 + * Windows 2022 server
38 + * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
53 53  
54 -//__Cancel and next buttons order__//
55 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
40 +When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
56 56  
57 -//__Data sink page__//
58 -The data sink page has been moved to the “Explore” tab.
42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
59 59  
60 -//__Unused images removal__//
61 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
44 +== **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 they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
62 62  
63 -//__Flow Designer performance__//
64 -Performance improvements for the Flow Designer have been implemented.
48 +//__Improved handling of optionality in JSON on lists__//
49 +Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
65 65  
66 -//__Properties with special characters__//
67 -When a user would migrate to the next generation architecture and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
51 +//__Loading bar when searching for log entries__//
52 +To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
68 68  
69 -//__Hidden flow fragements__//
70 -When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
54 +//__Improved feedback when deleting elements from Capture__//
55 +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.
71 71  
72 -//__Resources disappearances__//
73 -Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
57 +//__Enhanced filter options in Manage__//
58 +With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
74 74  
75 -//__Error channel for all inbounds__//
76 -If there is no custom error handling, next generation migration would set the error channel to “errorChannel” only for the first inbound in an entry flow. We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
60 +//__Copy property names from Create__//
61 +This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
77 77  
78 -//__Highlighting resources__//
79 -The performance of highlighting resources of selected components is improved in Read only mode.
80 80  
81 81  == **Bug Fixes** ==
65 +//__Queue name validation__//
66 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
82 82  
83 -//__Topic and event-processor names__//
84 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
68 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
85 85  
86 -//__System alignment__//
87 -The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases. This will be done for existing systems as well.
70 +//__Removal of onramp__//
71 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
88 88  
89 -//__Error alerting__//
90 -The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
73 +//__eMagiz login__//
74 +In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
91 91  
92 -//__Alerting__//
93 -For the next generation architecture models, several adaptations to triggers have been made.
94 -* For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
95 -* For the next generation architecture models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
96 -* The next generation architecture configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
97 -
98 -//__Unused containers__//
99 -Containers are set inactive when they are unused and removed in Design.
100 -
101 -//__Error popups when promoting a release version__//
102 -We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
103 -
104 -{{warning}}There is a new eMagiz Mendix connector available because a memory leak was found, only affecting customers that have been fully migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. {{/warning}}
105 -
106 106  == **Fancy Forum Answers** ==
107 107  
108 108  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:
109 109  
110 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
111 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
112 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
113 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
80 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
81 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
82 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
83 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
84 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
114 114  
86 +== **Key Takeaways** ==
115 115  
116 -== **Key takeaways** ==
117 -
118 118  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:
119 119  
120 120  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -124,7 +124,6 @@
124 124  * Check out the release notes [here]
125 125  * Start thinking about how the license tracker can aid your development
126 126  * Start thinking about major, minor, and patch
127 -* Upgrade to the latest build number
128 128  * Keep making great integrations
129 129  
130 130  Let's stay in touch and till next time!
... ... @@ -132,6 +132,11 @@
132 132  {{info}}
133 133  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
134 134  
135 -~*~* Indicates a next-generation-architecture only feature.
136 -{{/info}})))((({{toc/}}))){{/container}}
104 +{{/info}}
105 +)))
106 +
107 +(((
108 +{{toc/}}
109 +)))
137 137  {{/container}}
111 +{{/container}}