Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

From 237.1 to 238.1 From 361.1 to 362.1

From version 238.1

edited by Erik Bakker
on 2023/10/26 10:32

Change comment: There is no comment for this version

To version 361.1

edited by Carlijn Kokkeler
on 2024/01/29 14:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--207 - Aligned State
++213 - Joyful Journeys

Author

@@ -1,1 +1,1 @@
--XWiki.ebakker
++XWiki.CarlijnKokkeler

Content

@@ -1,118 +1,85 @@
  {{container}}
--{{container layoutStyle="columns"}}(((
++{{container layoutStyle="columns"}}
++(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** This release ....
--{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
++== **Pop-up Improvements** ==
++//__Property releases__//
++When a new property release is created, this property release can now be viewed and deleted.
--== **State Generation~*~*** ==
++[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
--//__New components__//
--The following components have been added:
--* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
--* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
--* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
--* 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.
--* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
++//__Runtime deletion__//
++When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
--//__SpEL functions & JSON__//
--Added SpEL functions for:
--* Encoding & decoding Base64, Hex and hmac.
--* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
--* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
++//__Wiretap & debug error messages__//
++The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
--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`.
++//__Action messages__//
++The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
--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"]].
++== **Formatting & Alignments** ==
--{{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}}
++//__Input fields__//
++Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
--{{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}}
++//__UI improvements__//
++UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
--== **Metrics Storage Duration** ==
--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.
++//__Runtime overview image versions__//
++Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
--((((% border="3" cellpadding="10" cellspacing="10" style="width:400px" %)
--|=(% style="width: 120px;" %)Future|=(% style="width: 180px;" %)Minute level|=(% style="width: 180px;" %)Hour level
--|(% style="width:120px" %) Production|(% style="width:180px" %) 30 days|(% style="width:180px" %) 1 year
--|(% style="width:120px" %) Acceptance|(% style="width:180px" %) 14 days|(% style="width:180px" %) 6 months
--|(% style="width:120px" %) Test|(% style="width:180px" %) 7 days|(% style="width:180px" %) 3 months
--)))
++//__Component changes reversion__//
++In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
--== **Feedback Items** ==
++//__State generation statistics__//
++The state generation graphs will now show the correct number of cache hits and misses.
--//__Import from store__//
--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.
++//__Queue browser timestamps__//
++All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd  HH:mm:ss.SSS.
--//__Save and cancel buttons placement__//
--The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
++//__Addition and deletion of internal recipients__//
++Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
--//__User session times__//
--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.
++== **Feedback Items** ==
--//__Cancel and next buttons order__//
--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.
++//__Update flows__//
++In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
--//__Data sink page__//
--The data sink page has been moved to the “Explore” tab.
++//__Q&A forum search__//
++The option to search by pressing the Enter key has been added to the Q&A forum.
--//__Unused images removal__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
++//__Memory settings__//
++It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
--//__Flow Designer performance__//
--Performance improvements for the Flow Designer have been implemented.
++//__Runtime validation__//
++Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
--//__Properties with special characters__//
--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.
--//__Hidden flow fragements__//
--When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
--
--//__Resources disappearances__//
--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.
--
--//__Error channel for all inbounds__//
--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.
--
--//__Highlighting resources__//
--The performance of highlighting resources of selected components is improved in Read only mode.
--
  == **Bug Fixes** ==
--//__Topic and event-processor names__//
--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.
++//__Removal of onramp__//
++We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
--//__System alignment__//
--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.
++//__Runtime statistics details__//
++We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
--//__Error alerting__//
--The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
++//__Deployment prechecks__//
++During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
--//__Alerting__//
--For the next generation architecture models, several adaptations to triggers have been made.
--* 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%.
--* 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%.
--* 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.
--//__Unused containers__//
--Containers are set inactive when they are unused and removed in Design.
--
--//__Error popups when promoting a release version__//
--We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
--
  == **Fancy Forum Answers** ==
  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:
--* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
--* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
--* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
--* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
++* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
++* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
++* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
++== **Key Takeaways** ==
--== **Key takeaways** ==
--
  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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
@@ -122,7 +122,6 @@
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
  * Start thinking about major, minor, and patch
--* Upgrade to the latest build number
  * Keep making great integrations
  Let's stay in touch and till next time!
@@ -130,6 +130,11 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a next-generation-architecture only feature.
--{{/info}})))((({{toc/}}))){{/container}}
++{{/info}}
++)))
++
++(((
++{{toc/}}
++)))
  {{/container}}
++{{/container}}

Changes for page 213 - Joyful Journeys

Summary

Details

Navigation