Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 188.1
edited by Carlijn Kokkeler
on 2023/10/23 14:45
on 2023/10/23 14:45
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 207-AlignedState1 +185 - To determine - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.eMagiz - Content
-
... ... @@ -2,102 +2,64 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have donemuch workforstategeneration,sothat youcanderivemoreinformationfrom your data!Examplesareenrichment,aggregation,change detectionand duplicatedetection.Stategeneration functionality is onlyaccessible formodelswithan add-onstateenerationlicense.Nexttostate generation,severalimprovementsregardingthe alignment ofcomponentshave beenmade. Moreover, performanceimprovementsandbugfixeshavebeenimplemented.Lastly,achangeinthemetricsstoragedurationhasbeenperformed.5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one. 6 6 7 -== StateGeneration**7 +==**Flow Designer V3**== 8 8 9 -//__New components__// 10 -The following components have been added: 11 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one. 12 -* Infinispan metadata outbound channel adapter: Used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts. 13 -* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers. 14 -* 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. 15 -* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher. 9 +The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider. 10 + 11 +=== **Improvements** === 12 +The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy. 16 16 17 -//__SpEL functions & JSON__// 18 -Added SpEL functions for: 19 -* Encoding & decoding Base64, Hex and hmac. 20 -* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond). 21 -* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser). 14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 22 22 23 -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`. 16 +Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow. 17 + 18 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]] 19 + 20 +* **Alerts** 21 +In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location. 24 24 25 -Added support for `#JsonPath` usage in SpEL expressions. 23 +* **Resources** 24 +In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these. 25 + 26 +* **Support objects** 27 +The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used. 26 26 27 - 28 - ==**MetricsStorage Duration**==29 +* **Properties** 30 +The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry. 29 29 32 +=== **User interaction changes** === 33 +There are some small changes to consider compared to the old flow designer. Please take a moment to read these: 30 30 35 +* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select 36 +* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier 37 + 31 31 39 +== **Feedback items ** == 32 32 33 - ==**FeedbackItems**==41 +We have also solved other feedback items besides the key updates around functionality. 34 34 35 -//__ Alertingmanualpause__//36 - Afew releasesago wechangedthebehaviorof alerting inthe deployment plan. Now each timewhen a deployment planisexecuted thealertingwill beautomaticallyre-enabled whenthe deployercloses the deploymentplanorcloses the web browser. The majority of the usersare happywiththenew behavior, but thereare someusecasesthatyou donotwant start thealerting immediately.Withhisrelease, if alerting has been paused manually,this will notbe activatedautomatically afterareleasedeployment.43 +//__Set runtime field as first selected field on property level__// 44 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 37 37 38 - //__Ordering ofgraphsinManage__//39 - Thegraphsin Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).46 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 47 + 40 40 41 -//__UTC times in Grafana panels__// 42 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 43 - 44 -//__Update flow designer version__// 45 -The framework used in the flow designer has been updated, improving performance. 46 - 47 -//__Carwash track TLS versions in logging__// 48 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 49 - 50 -//__Moving channels in the flow designer__// 51 -Moving already attached channels in the flow designer has been made sligthly easier. 52 - 53 -//__Topic sizes description change__// 54 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 55 - 56 -//__Password change notification__// 57 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 58 - 59 -//__Password comparison__// 60 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 61 - 62 -//__Inactive user alerting__// 63 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 64 - 65 -//__Alphabetical sorting on user level in HTTP statistics__// 66 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 67 - 68 - 69 -== **Bug Fixes** == 70 - 71 -//__Flow designer styling__// 72 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 73 - 74 -//__Partial search for messages__// 75 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim". 76 - 77 -//__Disk usage after cloud template update__// 78 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 79 - 80 -//__Error handling migration__// 81 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 82 - 83 83 == **Fancy Forum Answers** == 84 84 85 -As always, this isa 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:51 +As always, a gentle reminder to all 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: 86 86 87 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 88 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 89 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 90 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 91 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 53 +* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]] 54 +* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]] 92 92 93 - 94 94 == **Key takeaways** == 95 95 96 -Thanks to all whohelpedbuildandthose who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:58 +Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 97 97 98 98 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 99 99 * If you have feedback or ideas for us, talk to the Platypus 100 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 101 101 * Clear your browser cache (Ctrl + Shift + Del) 102 102 * Check out the release notes [here] 103 103 * Start thinking about how the license tracker can aid your development ... ... @@ -104,12 +104,13 @@ 104 104 * Start thinking about major, minor, and patch 105 105 * Upgrade to the latest build number 106 106 * Keep making great integrations 69 +* Check out the new documentation portal. 107 107 108 108 Let's stay in touch and till next time! 109 109 110 110 {{info}} 111 -~* Indicates a Beta feature. If you would like to get access to this beta feature ,please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]74 +~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 112 112 113 -~*~* Indicates a next-generation-architecture only feature.76 +~*~* Indicates a GEN3-only feature. 114 114 {{/info}})))((({{toc/}}))){{/container}} 115 115 {{/container}}