Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 67.1
edited by Erik Bakker
on 2023/01/18 10:25
on 2023/01/18 10:25
Change comment:
There is no comment for this version
To version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
on 2024/03/11 15:13
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 90-FastForward1 +216 - Hack Heaven - Content
-
... ... @@ -1,131 +1,124 @@ 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, 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. 4 4 5 - **Hithere, eMagiz developers!**It has beena while sinceour last deployment on the 9th of December. As a result we have finished up a lotofnewimprovements to our3rd generation runtime offering and fixed a variety of annoying bugsas well as some smallimprovements.This release is characterizedby themajor steps we took torelease several major features on our 3rd generation runtime among whicharethequeue browser andmessage redelivery functionality.8 +== ** Announcement - TLS versions deprecated** == 6 6 7 - == **QueueBrowser**==10 +Placeholder for info from Bas 8 8 9 -{{ warning}}Notethat this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}12 +{{info}}Text{{/info}} 10 10 11 - Toenhance theobservability of your integration landscapewhile running in the 3rd generation runtimearchitecture we have added anew featuretoour Managephase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage.Withthe help of the queue browser you can, as the name suggests, browse your queue.14 +== **Announcement - Spring 6** == 12 12 13 - To do so, we offer two options within this functionality. We have the Explore function and wehave the Wiretap function. When selecting a queue andopting for theExploreoption you get a live view ofwhat data is currently presenton the queue. When selecting the Wiretapfunctionality you automatically wiretap your queue and are presented with copies (on a special queue) ofyouractual message that pass through the queuefromthemoment you pressed the Wiretap button.16 +Placeholder for info from Jelle 14 14 15 - [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]18 +{{warning}}Text{{/warning}} 16 16 17 - Afterselecting the queueandchoosing the option eMagiz will showyou the list of messages (oldest first) that arecurrently on the queue (Explore option)or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.20 +== **Infra flow selection** == 18 18 19 -* Delete the message from the queue (Explore option) 20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue. 21 -* Clear message from the wiretap queue (Wiretap option) 22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore 23 -* Refresh messages list (both options) 24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first 25 -* Save as test message 26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality. 27 -* Download 28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed. 22 +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 -[[image:Main.Images.Release Blog.WebHome@ 190-release-blog--queue-browser-explore-overview.png]]24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 31 31 32 - [[image:Main.Images.ReleaseBlog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]26 +In edit mode, you can select a new version via the right-click option, which you already use for other flows. 33 33 34 - == **MessageRedelivery ** ==28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 35 35 36 - {{warning}}Notethat thisfunctionalityonlyworkswhenyourJMSserverisrunningonthe3rdgenerationruntimeandthe functionality is enabledfor youenvironment.{{/warning}}30 +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. 37 37 38 -[[image:Main.Images.Release Blog.WebHome@ 190-release-blog--message-redelivery-overview.png]]32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 39 39 40 - Justas with our current offering we now offer our message redelivery functionality for our 3rd generationarchitecture. To enhance the user experience we have placed this functionality as well underthe "Explore" optionin Manage. Whenselecting the messageredelivery option you willsee all messages that arecurrentlyin need tobe redelivered (as anerror occurred).34 +== **Multiple environments selection** == 41 41 42 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before. 36 +{{warning}}The following is only applicable under the following conditions: 37 + * Windows 2022 server 38 + * At least one port opened (as a consequence of a hosted web service){{/warning}} 43 43 44 - Ontopofthatwehave addedsomeadditionalfunctionality.40 +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 45 46 -* Search option 47 - ** Original queue name 48 - ** Original message ID (which can be found as a header called jms_messageid in the error message view) 49 -* Save as test message 50 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. 51 -* Download 52 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed. 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 53 53 54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 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 displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier. 55 55 56 -== **3rd generation runtime bolstering** == 48 +//__Improved handling of optionality in JSON on lists__// 49 +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. 57 57 58 - This release willintroducevariousimprovementsforour3rdgenerationruntime.Belowyouwill find themost noteworthyenhancementswemadetothe3rd generationruntime and its interactionwiththe portal.51 +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. 59 59 60 -//__ Define memory settingsforon-premiseruntimesfromDeployArchitecture__//61 - With this release, youarenowable todefinethememorysettings (andthereforethememory limits)ofyour on-premiseruntimesinthe same manner as cloudruntimes.Inall casesyou can nowdefine andchangethe memory settingsviaDeploy Architecture.In contrast tohowthesevaluesareactualized forcloudruntimesyouneed tocreate anewrelease and deployit to actualize the changeson-premise.53 +//__Loading bar when searching for log entries__// 54 +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. 62 62 63 -//__ Emptyruntime feedback when deployinga release(or settingthereleaseas active)__//64 -To prevent thatyouarenotbeingabletodeploy arelease toyourenvironmentduetoa mismatch betweenwhatis in yourrelease andin DeployArchitecturewehavenow added afeedbackpop-upwhen deployingareleasethatnotifiesyouforwhich runtimesthereisa mismatch betweenyourrelease andDeploy Architecture.56 +//__Improved feedback when deleting elements from Capture__// 57 +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. 65 65 66 -//__ Auto-fillnamespacesforSOAP hosted webservices__//67 - Based onyour configurationinDesigneMagiz willnowauto-fillthe namespacewhenyou hostaSOAP web service.Thisavoids anypotentialproblemsinvalidatingmessages.59 +//__Enhanced filter options in Manage__// 60 +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. 68 68 69 -//__ UpdatedH2 databasesetting__//70 - As of this release,we have improvedtheconfigurationofour H2 databases that are usedwithineMagiz.ThisnewsettingwillensurethattheruntimecontrolswhentheH2 database isshutdown.62 +//__Copy property names from Create__// 63 +This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying. 71 71 72 -{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}} 65 +//__Improved feedback during migration to the current runtime architecture__// 66 +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. 73 73 74 -//__ Runtimesettingsoption addedto contextmenuonruntimelevelDeploy Architecture__//75 - As a replacementofthecurrentHTTPsettingscontextmenuwehave added anew menuitem called runtime settings.Ontop of beingable to configure your HTTP settings(which you need to defineforahosted web service)younowalso candefinewhether the control bus needs to work for this runtime.68 +//__Block user from making changes to their cloud while another upgrade is still in progress__// 69 +We now block users from changing their cloud configuration when another upgrade is ongoing. 76 76 77 -//__ Deploy Agentoption addedto context menu on machinelevel Deploy Architecture__//78 -W ith this release,wehave added acontext menuitem thatallowsuserto deploy the agentthatisneededtorunyour 3rd generationarchitectureon-premise.Formoreinformationon howtoinstall thispleasecheckoutthis[[microlearning>>doc:Main.eMagizAcademy.Microlearnings.Expert Level.SolutionArchitecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]71 +//__Cron trigger validation__// 72 +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. 79 79 80 -//__Added "Reset" functionality__// 81 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime. 74 +== **Bug Fixes** == 75 +//__Making Edit (and View) the default action when configuring parameters__// 76 +We have made the Edit (and View) button the default action when configuring parameters in a transformation. 82 82 83 -== **Feedback items ** == 78 +//__Property configuration pop-up resized__// 79 +We have resized the property configuration overviews to make the property value better readable. 84 84 85 -We have also solved other feedback items besides the flow designer's critical updates. 81 +//__Alphabetically sorted components in the flow designer__// 82 +As of this release, we now sort the components alphabetically in the flow designer. 86 86 87 -//__Improved namingconventionon Storerelated pages__//88 - Wehave improvedvariousdisplaynames using themergefunctionalitywithinourstore offering.84 +//__Improved sorting on runtime overview__// 85 +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. 89 89 90 -//__ Update securityprotocols forour internal architecture__//91 - Parts ofour internalinfrastructure(i.e., docs.emagiz.com)havebeenupdatedto adhereto thelatestsecuritystandards.87 +//__Improved sorting on catalog overview__// 88 +As of this release, we now sort the topics in the catalog by name. 92 92 93 -//__ Improved read-onlydescription for "if exists"constructionsin Transformations__//94 - To makeitclear whatthe"if exists"checkdoeswhilenot beingin"Start Editing" mode,we have improvedthedescriptionsouserswithouteditrightsorwithout wantingtoenterthe"StartEditing"modecan read andinterpretwhatthecheckdoes.90 +//__Styling fix on rich text editors__// 91 +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. 95 95 93 +//__Styling fix on release edit__// 94 +As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header." 96 96 97 -== **Bug fixes ** == 96 +//__Removed false-positive alerts on transformations__// 97 +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. 98 98 99 -//__ Decentvalidationfeedback whennotfillinginthe propertyvalue__//100 - We havefixedthe validationfeedbackyougetwhennotfillingin theproperty valueusingthe "Checkproperties"functionality.99 +//__Event Streaming Graphs - view thirty days back__// 100 +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. 101 101 102 -//__I ncorrect resource locations__//103 -We have fixedseveralinstanceswherethe resourcelocationwasnotgeneratedcorrectlyinthe 3rdgenerationruntime.102 +//__Improved helptext__// 103 +We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 104 104 105 -//__Apply to environment in User Management performance improvement__// 106 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 107 - 108 108 == **Fancy Forum Answers** == 109 109 110 110 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: 111 111 112 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 113 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 114 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 115 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 109 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 116 116 117 -== **Key takeaways** ==111 +== **Key Takeaways** == 118 118 119 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:113 +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: 120 120 121 121 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 122 122 * If you have feedback or ideas for us, talk to the Platypus 123 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 117 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 124 124 * Clear your browser cache (Ctrl + Shift + Del) 125 125 * Check out the release notes [here] 126 126 * Start thinking about how the license tracker can aid your development 127 127 * Start thinking about major, minor, and patch 128 -* Upgrade to the latest build number 129 129 * Keep making great integrations 130 130 131 131 Let's stay in touch and till next time! ... ... @@ -133,6 +133,11 @@ 133 133 {{info}} 134 134 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 135 135 136 -~*~* Indicates a GEN3-only feature. 137 -{{/info}})))((({{toc/}}))){{/container}} 129 +{{/info}} 130 +))) 131 + 132 +((( 133 +{{toc/}} 134 +))) 138 138 {{/container}} 136 +{{/container}}