Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 34.1
edited by Erik Bakker
on 2022/10/24 13:35
on 2022/10/24 13:35
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 86 -DaemonSwitch1 +216 - Hack Heaven - Content
-
... ... @@ -1,162 +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!**We have hit the ground running this quarter by focusing on more prominent features and spending a substantialchunk of timefocusing with us all on a lot of smaller feedback items and bugs. Alltheseitemswillbe provided to you with thisrelease. Among these are flow designer improvements,navigation improvements, andconsistency improvements. On top of that, we have made our new monitoring stackavailableto thefirst set of models.So let us dive into all we have to offer this time!8 +== ** Announcement - TLS versions deprecated** == 6 6 7 - == **Newmonitoringstack**==10 +Placeholder for info from Bas 8 8 9 - This release will introduce a new monitoring stack availablefor modelsthat runinthe new runtime architecture ofeMagiz. With the helpof this monitoring stack, we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of these changes, please check out the following microlearnings.12 +{{info}}Text{{/info}} 10 10 11 -* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 12 -* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]] 13 -* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]] 14 -* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]] 14 +== **Announcement - Spring 6** == 15 15 16 - {{info}}Note that the new monitoring stack is onlyavailable for models that run the new runtime architecture. Shouldyou wish to become an earlyadopter,don't hesitate to get intouchwith us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]to discuss thepossibilities{{/info}}16 +Placeholder for info from Jelle 17 17 18 - == **Academy improvements** ==18 +{{warning}}Text{{/warning}} 19 19 20 - Ontop ofthat, we have added various microlearningsto our academy offering availableon docs.emagiz.com related to the newruntime architecture. You can identify thesemicrolearnings by looking at the following icon in frontof a microlearning.20 +== **Infra flow selection** == 21 21 22 - [[image:Main.Images.ReleaseBlog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]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. 23 23 24 - ==**Flow DesignerImprovements** ==24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 25 25 26 -//__See last changed date and changed by on resource level__// 27 -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. 26 +In edit mode, you can select a new version via the right-click option, which you already use for other flows. 28 28 29 -[[image:Main.Images.Release Blog.WebHome@ 186-release-blog--change-info.png]]28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 30 30 31 -//__See on which other flows a resource is used__// 32 -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. 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. 33 33 34 -[[image:Main.Images.Release Blog.WebHome@ 186-release-blog--resource-used-in-other-configs.png]]32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 35 35 36 -//__Toggle option to see the generated resource by default__// 37 -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. 34 +== **Multiple environments selection** == 38 38 39 -== **Feedback items ** == 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}} 40 40 41 -We have a lsosolvedotherfeedbackitemsbesidestheflowdesigner'scriticalupdates.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. 42 42 43 -//__Redirect to the Manage Dashboard from your model home page__// 44 -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. 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 45 45 46 -//__Readable entry of a SpEL expression in a flow component__// 47 -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. 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. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 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. 50 50 51 -//__Keep Create and the Create Phase release in sync__// 52 -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. 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. 53 53 54 -//__ Mask password valuesintheunused propertiesoverview__//55 - All propertyvaluesofthetype passwordcanbemaskedinthe propertiesoverviewscreen. However,thisbehavior wasdifferentwhen pressingthe unused propertiesoverview. With thisrelease, we havecorrectedthisbehavior toensurethat passwords arealsomasked inthisoverview.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. 56 56 57 -//__ PressEnter to Search for properties__//58 - Withthis release,wehaveaddedfunctionality that makes itpossibletopress**Enter**whensearchingfor propertiesin thepropertyoverview.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. 59 59 60 -//__ Styling update ontag selectiononintegrationlevel__//61 -With this release, we have improved the stylingoftagsdisplayedonthe integrationand system level. Thisway,the tagis betterreadable,andthe iconto remove aselectedtagiscompletely shownto theuserinstead ofpartly.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. 62 62 63 -//__ Enter toclose automatedflowtesting pop-up__//64 - Uponyourrequests, wehavemadethe pop-up detailingyourautomatedflowtest resultsto beclosable bypressing theEnterkeyonyourkeyboard. This savesyouthehassleof grabbingyour mouseandclicking thebutton.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. 65 65 66 -//__Improved naming ofdownloadedEventStreaming keystore__//67 - When downloadinga Keystorethatan EventStreamingclientneedsto accessatopic, thenamenowincludestheclientname**and**the environmentsoyoucaneasilydiscernthe differencebetweenthekeystoreswhendistributingthemtoyourclient.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. 68 68 69 -//__ Popoutonthe Traces tabwithinFlowTesting__//70 - In linewith the improvements we made beforewithinthe FlowTestingfunctionality,wehavenowaddedthepop-out functionality toall resultsshownin the tracestab. This will make it easier toanalyzewhat happensbetweenthestartandtheendof your flow.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. 71 71 72 -//__ SortingUserManagement__//73 - Asof this release,the usermanagementoverviewinDeployfor usersandroleswill besortedalphabeticallyto makeiteasiertofinda specificuserorrole withinthis overview.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. 74 74 75 -//__Improved warning on passthrough API operation__// 76 -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. 77 - 78 -//__Improved update functionality of Swagger file when changing data model__// 79 -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. 80 - 81 -{{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}} 82 - 83 -//__"Disapprove and go to environment"__// 84 -Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. 85 - 86 -//__Improve readability of API Gateway operations in Create and Deploy__// 87 -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. 88 - 89 -//__Add Topic Storage information to License Tracker__// 90 -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. 91 - 92 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] 93 - 94 -//__Add Compatibility check when importing store items__// 95 -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. 96 - 97 -//__Show dependencies between support objects__// 98 -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. 99 - 100 -//__Improve rendering of validation definition when using multiple namespaces__// 101 -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. 102 - 103 -//__Improved help texts on next-generation runtime functionality across the portal__// 104 -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. 105 - 106 106 == **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. 107 107 108 -//__Pro videcorrectfeedback whenaflowis transferredtoDeployforthefirst time__//109 -W ith this release,wehavemadeseveralimprovements to what feedbackis givento theuserwhen moving a flow from Create to Deployfor thefirst (upon creatingyour first definitiveversion). This willensurethat noconfusing pop-ups will beshownthat areincorrect and only confuse theuserfurther.78 +//__Property configuration pop-up resized__// 79 +We have resized the property configuration overviews to make the property value better readable. 110 110 111 -//__ Showinformation in theException oferrormessages overview__//112 - Withthis release, wehaveresolvedthebugplaguingthis page. As a result, you willagainsee information on this page whenthere isinformation to show.81 +//__Alphabetically sorted components in the flow designer__// 82 +As of this release, we now sort the components alphabetically in the flow designer. 113 113 114 -//__Improve st yling ofcrontriggerconfiguration pop-up__//115 - Thestylingof thispop-upmade it very hardtoconfigure a crontrigger.We have redesigned thestylingtomakethepop-upreadable again.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. 116 116 117 -//__ Preventflow editinglocks inspecific situations__//118 - There werespecificsituationswhen switchingbetweenDesignandCreatethat could leadtounexpectedbehavior in theCreate phase. Thisled toa flow editinglockwarning to the user. We have solved this problemin this release.87 +//__Improved sorting on catalog overview__// 88 +As of this release, we now sort the topics in the catalog by name. 119 119 120 -//__ Generate propertyvalueemptiestheruntimeselection__//121 - With this release,we have fixedthebug thatemptied theruntimeselectionupongeneratingaproperty value(i.e.,password).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. 122 122 123 -//__ Make sure nothingofasystem messageiseditable from your exit__//124 - Before,youcould changepart of your system messagefromyourexit(but noteverything).Thisledto confusion.As a result,wehavenowmade sure you cannotedit anything onthesystemmessagelevel fromyourexit tokeepit consistentwithourdesignchoices.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." 125 125 126 -//__ Preventuserswithout viewrightsfrom seeinga weirdscreen inthose phases__//127 -W ith thisrelease,we haveintroducedaconsistentapproachtowardswhatweshowauserthathasno viewrightsonacompletephase. Thismeansthat you will always seethesameinformationconsistently.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. 128 128 129 -//__ nameof starting pointoftheflow testisincorrect__//130 - With thisrelease, wehave ensuredthat the nameofthe starting pointof yourflowtestyouseeinthe"Results" tabiscorrect.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. 131 131 132 -//__ Audit Trailon UserManagement could break__//133 -Whe nperforming many changestousermanagement in Deployatonce,there was achancetheaudit trailfunctionalitywouldgiveanerrorblockingyoufrom continuing yourupdate. With thisrelease, we have solvedthat issue.102 +//__Improved helptext__// 103 +We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 134 134 135 -//__Progress bar in the license tracker is shown twice__// 136 -With this release, we have fixed a bug that showed the progress bar twice in the license tracker. 137 - 138 -//__Compare flows with support objects in the new flow designer__// 139 -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. 140 - 141 141 == **Fancy Forum Answers** == 142 142 143 143 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: 144 144 145 -* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]] 146 -* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]] 109 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 147 147 148 -== **Key takeaways** ==111 +== **Key Takeaways** == 149 149 150 -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: 151 151 152 152 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 153 153 * If you have feedback or ideas for us, talk to the Platypus 154 -* 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. 155 155 * Clear your browser cache (Ctrl + Shift + Del) 156 156 * Check out the release notes [here] 157 157 * Start thinking about how the license tracker can aid your development 158 158 * Start thinking about major, minor, and patch 159 -* Upgrade to the latest build number 160 160 * Keep making great integrations 161 161 162 162 Let's stay in touch and till next time! ... ... @@ -164,6 +164,11 @@ 164 164 {{info}} 165 165 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 166 166 167 -~*~* Indicates a GEN3-only feature. 168 -{{/info}})))((({{toc/}}))){{/container}} 129 +{{/info}} 130 +))) 131 + 132 +((( 133 +{{toc/}} 134 +))) 169 169 {{/container}} 136 +{{/container}}