Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 33.1
edited by Erik Bakker
on 2022/10/24 11:13
on 2022/10/24 11:13
Change comment:
There is no comment for this version
To version 367.1
edited by CarlijnKokkeler
on 2024/01/29 15:34
on 2024/01/29 15:34
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 -1 86-DaemonSwitch1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,162 +1,93 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have hit the groundrunningthisquarter by focusingon more prominent features and spendinga substantialchunk of timefocusingwithusall on a lot ofsmaller feedbackitems andbugs. Alltheseitemswill be providedtoyouwiththisrelease.Among theseareflowdesignerimprovements,navigationimprovements,andconsistencyimprovements.Ontop of that, we havemadeour newmonitoringstackavailableto thefirstset of models.Soletusdiveinto all wehavetooffer this time!6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done. 6 6 7 -== ** Newmonitoringstack** ==8 +== **Pop-up Improvements** == 8 8 9 -This release will introduce a new monitoring stack available for models that run in the new runtime architecture of eMagiz. With the help of 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. 10 +//__Property releases__// 11 +When a new property release is created, this property release can now not only be viewed but also deleted. 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"]] 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 15 15 16 -{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}} 15 +//__Runtime deletion__// 16 +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. 17 17 18 -== **Academy improvements** == 18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 19 19 20 -On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning. 21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 21 21 22 - [[image:Main.Images.ReleaseBlog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]24 +== **Formatting & Alignments** == 23 23 24 -== **Flow Designer Improvements** == 26 +//__Input fields__// 27 +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. 25 25 26 -//__ Seelast changed date and changed by onresource level__//27 - Thisreleasewillreinstatethe abilitytoseewho changeda resourcelast andwhenit was changedforthelasttime. You can findthisinformationby double-clickingonaresource or viewingitsdetailsvia theviewbutton.29 +//__UI improvements__// 30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 28 28 29 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]] 32 +//__Component changes reversion__// 33 +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. 30 30 31 -//__Se eonwhich otherflowsaresourceisused__//32 -Th is releasewill reinstatetheability tosee whetheraresourceisused inotherflowswithinyour model ornot.This will helpto determine theimpactofa specific change.35 +//__State generation statistics__// 36 +The state generation graphs will now show the correct number of cache hits and misses. 33 33 34 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]] 38 +//__Queue browser timestamps__// 39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 35 35 36 -//__ Toggleoptiontoseethegeneratedresourceby default__//37 - Uponrequest, wehave made the toggle forthe generatedresourcesinthenewflow designeruser-dependent. This meansthatyou,as a user,candetermine thatthetoggleshouldalsobeon. This meansthat thegeneratedresourceswill beshownto you whenopeningany flow in eMagiz. When youswitch the toggle off, this willmeanthat you will**not** see thegeneratedresourcesby default.41 +//__Addition and deletion of internal recipients__// 42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 38 38 39 -== **Feedback items** ==44 +== **Feedback Items** == 40 40 41 -We have also solved other feedback items besides the flow designer's critical updates. 46 +//__Update flows__// 47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 42 42 43 -//__ Redirectto the Manage Dashboardfrom yourmodelhomepage__//44 - Directlynavigatingtothe Manage phase(ofany environment) will automatically redirectyouto the errormessageDashboard, asthat is thelandingpage oftheManagephase.49 +//__Q&A forum search__// 50 +The option to search by pressing the Enter key has been added to the Q&A forum. 45 45 46 -//__ Readable entryof a SpEL expression in a flow component__//47 - Asofnow,theinputfieldforyourSpEL expressionincertain flowcomponentswill dynamicallyexpandwhenyouenter a largeSpEL expression. This willimprove thereadabilityof your solutionand willmakeiteasiertoenterandvalidateyourSpELexpressions.52 +//__Memory settings__// 53 +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. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 55 +//__Runtime validation__// 56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 50 50 51 -//__ Keep Create andtheCreatePhasereleaseinsync__//52 - PreviouslytheCreate andthe Create Phasereleasemight havebecomeout of sync.As a result, comparing a releasetotheCreatePhaserelease couldyieldconfusingresults.With thisrelease,wehave madeseveralimprovementstopreventthisfromhappening.58 +//__Runtime overview image versions__// 59 +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. 53 53 54 -//__Mask password values in the unused properties overview__// 55 -All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview. 56 - 57 -//__Press Enter to Search for properties__// 58 -With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview. 59 - 60 -//__Styling update on tag selection on integration level__// 61 -With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly. 62 - 63 -//__Enter to close automated flow testing pop-up__// 64 -Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button. 65 - 66 -//__Improved naming of downloaded Event Streaming keystore__// 67 -When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client. 68 - 69 -//__Pop out on the Traces tab within Flow Testing__// 70 -In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow. 71 - 72 -//__Sorting User Management__// 73 -As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview. 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** == 107 107 108 -//__ Providecorrectfeedbackwhen a flow is transferred to Deploy for the first time__//109 -W iththis release,wehavemadeseveralimprovementstowhat feedback isgiventotheuser when moving a flow from CreatetoDeployforthefirst(uponcreatingyour first definitiveversion).This will ensure thatno confusingpop-ups will beshown that areincorrectandonly confusethe user further.63 +//__Removal of onramp__// 64 +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). 110 110 111 -//__ Show information in theException of error messagesoverview__//112 -W iththis release,wehaveresolvedthebugplaguing thispage.Asaresult,youwillagainsee information on this pagewhenthereisinformationtoshow.66 +//__Runtime statistics details__// 67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 113 113 114 -//__ Improvestylingof cron trigger configurationpop-up__//115 - The styling ofthis pop-up made itveryhardtoconfigurea crontrigger.Wehaveredesignedthestyling tomakethepop-upreadable again.69 +//__Deployment prechecks__// 70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 116 116 117 -//__Prevent flow editing locks in specific situations__// 118 -There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release. 119 - 120 -//__Generate property value empties the runtime selection__// 121 -With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password). 122 - 123 -//__Make sure nothing of a system message is editable from your exit__// 124 -Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices. 125 - 126 -//__Prevent users without view rights from seeing a weird screen in those phases__// 127 -With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently. 128 - 129 -//__name of starting point of the flow test is incorrect__// 130 -With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct. 131 - 132 -//__Audit Trail on User Management could break__// 133 -When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue. 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"]] 76 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 77 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 78 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 147 147 148 -== **Key takeaways** ==80 +== **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:82 +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. 86 +* 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}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 169 169 {{/container}} 105 +{{/container}}