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 138.1
edited by Erik Bakker
on 2023/08/01 14:28
on 2023/08/01 14:28
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 - 187-IntegrationSponsor1 +202 - New Equilibrium - Content
-
... ... @@ -2,142 +2,65 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Withthis releaseweillreleaseseveralimpactful features and enablerstoourcommunity.Amongothersthenext phase of theeMagiz Store will becomepublicly available. Thismeansthatyou can now import datamodelsandtransformationon top ofsystem messagesinDesignand acceleratorsin Create.Furthermore, we willlaunchanewBetafunctionalitythroughsome ofour clients that willenableyouto restoreyourflowto apreviousversion.5 +**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you. 6 6 7 -== **Store - Next phase** == 7 +== **Release Properties** == 8 +As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are: 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. 10 +* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 +* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration. 12 +* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers. 13 +* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment. 10 10 11 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--current-store-offering.png]]15 +{{info}}For more information, please check out the following microlearnings: 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}} 17 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 18 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 +* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 14 14 15 -== **New eMagiz Mendix Connector** == 21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 +{{/info}} 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. 24 +== ** Manage - Next generation graphs improvements ** == 25 +As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out. 18 18 19 - {{info}}Migratingtheruntime from the eMagiz portal works theamefor any otherruntime. The migration path to migratecanbe found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 20 20 21 -== **F low version restore**~*==29 +== **Feedback Items** == 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. 31 +//__Improved editability when testing in eMagiz without Edit rights in Create__// 32 +Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 +//__Improved auditability on Deploy Architecture__// 35 +To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP). 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}} 37 +//__Test your own exported store content__// 38 +We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store. 32 32 33 - ==**Feedback items**==40 +{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-magic-store.WebHome||target="blank"]]{{/info}} 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 42 +//__Improved comparison of flows in the releases overview__// 43 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns. 36 36 37 -//__Redirect to the Manage Dashboard from your model home page__// 38 -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. 39 - 40 -//__Readable entry of a SpEL expression in a flow component__// 41 -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. 42 - 43 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 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. 47 - 48 -//__Mask password values in the unused properties overview__// 49 -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. 50 - 51 -//__Press Enter to Search for properties__// 52 -With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview. 53 - 54 -//__Styling update on tag selection on integration level__// 55 -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. 56 - 57 -//__Enter to close automated flow testing pop-up__// 58 -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. 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 - 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 -//__ Providecorrect feedbackwhenaflowis transferredDeployforthefirsttime__//103 - Withthis release, we have madeseveral improvements to what feedback is given tothe user whenmovingaflow from Create toDeploy for thefirst (upon creating your firstdefinitiveversion). This willensurethat noconfusingpop-upswill beshown that are incorrect andlyconfusethe userfurther.47 +//__Improved validation on XPath header enricher__// 48 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component. 104 104 105 -//__ ShowinformationintheException oferrormessagesoverview__//106 -W ith this release,wehaveresolved thebugplaguingthispage.Asa result,youwill againsee informationonthis pagewhenthereisinformationtoshow.50 +//__Cancel behavior on flow testing property overview fixed__// 51 +We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list. 107 107 108 -//__ Improvestylingofcronger configurationpop-up__//109 - Thestylingofthispop-upmadeitvery hardto configureacrontrigger.Wehave redesignedthestylingtomake thepop-up readable again.53 +//__Cancel behavior on flow fragment level when exporting store content__// 54 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list. 110 110 111 -//__ Prevent flow editinglocks inspecificsituations__//112 - There werespecificsituationswhenswitchingbetweenDesignandCreatethatcould leadtounexpectedbehaviorin theCreate phase. Thisled to afloweditinglock warningto theuser.We have solvedthisproblemin thisrelease.56 +//__Adding numbers on containers in Deploy Architecture__// 57 +With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active 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"]] 63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 141 141 142 142 == **Key takeaways** == 143 143