Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 41.1
edited by Erik Bakker
on 2022/11/07 16:35
on 2022/11/07 16:35
Change comment:
There is no comment for this version
To version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
on 2024/01/29 14:49
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 87-IntegrationSponsor1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,156 +1,97 @@ 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!** Withthis releasewe will releaseseveral impactful features and enablers toour community. Among others thenextphaseofthe eMagiz Storewill becomepublicly available. Thismeans that you can now import data modelsand transformation on top of system messages inDesignand accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 6 6 7 -== **Store - Next phase** == 8 8 9 -This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier. 9 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 10 10 11 -[[image:Main.Images.Release Blog.WebHome@ 187-release-blog--current-store-offering.png]]13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 12 12 13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/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. 14 14 15 -== **New eMagiz Mendix Connector** == 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. 16 16 17 -With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal. 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. 18 18 19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} 20 20 21 -== **F low versionrestore**~*==25 +== **Formatting & Alignments** == 22 22 23 -On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect. 27 +//__Input fields__// 28 +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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 26 26 27 -{{warning}}Note, that the following restrictions apply when restoring to a previous version: 28 - * Changes made on definition and transformation level are **not** restored 29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 33 +//__Runtime overview image versions__// 34 +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. 32 32 33 -== **Feedback items ** == 36 +//__Component changes reversion__// 37 +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. 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 39 +//__State generation statistics__// 40 +The state generation graphs will now show the correct number of cache hits and misses. 36 36 37 -//__ Redirectto the Manage Dashboard from your model homepage__//38 - Directlynavigating to theManagephase(ofany environment) willautomaticallyredirectyouto the error messageDashboard,as thatisthelandingpage oftheManagephase.42 +//__Queue browser timestamps__// 43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 39 39 40 -//__ Readable entryofaSpELexpression inflowcomponent__//41 - As ofnow,theinput fieldforyour SpELexpression incertain flow componentswilldynamicallyexpandwhen youentera largeSpELexpression.This will improvethe readabilityof your solution andwillmakeiteasiertoenter andvalidateyourSpELexpressions.45 +//__Addition and deletion of internal recipients__// 46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 42 42 43 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 44 44 45 -//__Keep Create and the Create Phase release in sync__// 46 -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. 49 +== **Feedback Items** == 47 47 48 -//__ Maskpasswordvalues intheunused properties overview__//49 - Allproperty values ofthetypepasswordcan bemaskedinthepropertiesoverviewcreen.However, this behaviorwasdifferentwhen pressingtheunusedpropertiesoverview. With thisrelease,we havecorrected thisbehavior to ensurethatpasswordsarealsomaskedin thisoverview.51 +//__Update flows__// 52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 50 50 51 -//__ PressEnterto Searchfor properties__//52 - Withthis release,we have added functionalitythatmakesitpossibleto press**Enter**whensearchingfor propertiesinthepropertyoverview.54 +//__Q&A forum search__// 55 +The option to search by pressing the Enter key has been added to the Q&A forum. 53 53 54 -//__ Styling updatentagselection on integrationlevel__//55 - Withthisrelease,wehaveimprovedthe styling oftagsdisplayedonheintegrationandsystemlevel.This way, thetag isbetterreadable,andtheicontoremoveaselectedtag iscompletelyshowntotheuser insteadofpartly.57 +//__Memory settings__// 58 +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. 56 56 57 -//__ Enterto closeautomated flow testing pop-up__//58 - Uponyour requests, we havemade the pop-up detailingyourautomated flow testresults tobe closablebypressingtheEnterkeyon yourkeyboard.Thissavesyou the hassleof grabbingyourmouseandclicking the button.60 +//__Runtime validation__// 61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 59 59 60 -//__Improved naming of downloaded Event Streaming keystore__// 61 -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. 62 62 63 -//__Pop out on the Traces tab within Flow Testing__// 64 -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. 65 - 66 -//__Sorting User Management__// 67 -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. 68 - 69 -//__Improved warning on passthrough API operation__// 70 -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. 71 - 72 -//__Improved update functionality of Swagger file when changing data model__// 73 -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. 74 - 75 -{{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}} 76 - 77 -//__"Disapprove and go to environment"__// 78 -Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. 79 - 80 -//__Improve readability of API Gateway operations in Create and Deploy__// 81 -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. 82 - 83 -//__Add Topic Storage information to License Tracker__// 84 -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. 85 - 86 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] 87 - 88 -//__Add Compatibility check when importing store items__// 89 -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. 90 - 91 -//__Show dependencies between support objects__// 92 -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. 93 - 94 -//__Improve rendering of validation definition when using multiple namespaces__// 95 -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. 96 - 97 -//__Improved help texts on next-generation runtime functionality across the portal__// 98 -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. 99 - 100 100 == **Bug Fixes** == 101 101 102 -//__ Providecorrectfeedbackwhen a flow is transferred to Deploy for the first time__//103 -W iththis release,wehavemadeseveralimprovementstowhat feedback isgiventoheuser when moving a flow from CreatetoDeployforthefirst(uponcreatingyour first definitiveversion).This will ensure thatno confusingpop-ups will beshown that areincorrectandonly confusehe user further.66 +//__Removal of onramp__// 67 +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). 104 104 105 -//__ Show information in theException of error messagesoverview__//106 -W iththis release,wehavesolvedthebugplaguing thispage.Asaresult,youwillagainsee information on this pagewhenhereisinformationtoshow.69 +//__Runtime statistics details__// 70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 107 107 108 -//__ Improvestylingof cron trigger configurationpop-up__//109 - The styling ofthis pop-up made itveryhardtoconfigurea crontrigger.Wehaveredesignedthestyling tomakethep-upreadable again.72 +//__Deployment prechecks__// 73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 110 110 111 -//__Prevent flow editing locks in specific situations__// 112 -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. 113 113 114 -//__Generate property value empties the runtime selection__// 115 -With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password). 116 - 117 -//__Make sure nothing of a system message is editable from your exit__// 118 -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. 119 - 120 -//__Prevent users without view rights from seeing a weird screen in those phases__// 121 -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. 122 - 123 -//__Name of starting point of the flow test is incorrect__// 124 -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. 125 - 126 -//__Audit Trail on User Management could break__// 127 -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. 128 - 129 -//__Progress bar in the license tracker is shown twice__// 130 -With this release, we have fixed a bug that showed the progress bar twice in the license tracker. 131 - 132 -//__Compare flows with support objects in the new flow designer__// 133 -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. 134 - 135 135 == **Fancy Forum Answers** == 136 136 137 137 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: 138 138 139 -* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]] 140 -* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]] 80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 141 141 142 -== **Key takeaways** ==84 +== **Key Takeaways** == 143 143 144 -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:86 +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: 145 145 146 146 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 * If you have feedback or ideas for us, talk to the Platypus 148 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 90 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 149 149 * Clear your browser cache (Ctrl + Shift + Del) 150 150 * Check out the release notes [here] 151 151 * Start thinking about how the license tracker can aid your development 152 152 * Start thinking about major, minor, and patch 153 -* Upgrade to the latest build number 154 154 * Keep making great integrations 155 155 156 156 Let's stay in touch and till next time! ... ... @@ -158,6 +158,11 @@ 158 158 {{info}} 159 159 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 160 160 161 -~*~* Indicates a GEN3-only feature. 162 -{{/info}})))((({{toc/}}))){{/container}} 102 +{{/info}} 103 +))) 104 + 105 +((( 106 +{{toc/}} 107 +))) 163 163 {{/container}} 109 +{{/container}}