Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
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 72.1
edited by Erik Bakker
on 2023/01/19 09:02
on 2023/01/19 09:02
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 87-IntegrationSponsor1 +190 - Fast Forward - Content
-
... ... @@ -2,142 +2,123 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Withthisreleasewe will releaseseveralimpactful featuresandenablers toour community.Amongothersthenext phaseoftheMagizStorewillbecomepubliclyavailable.This meansthatyoucannow importdatamodelsandtransformationonopofsystemmessagesinDesignand accelerators inCreate.Furthermore,wewill launchawBetafunctionalitythroughsome of ourclients thatwillenableyou torestoreyourflowtoapreviousversion.5 +**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result, we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality. 6 6 7 -== ** Store- Nextphase** ==7 +== **Queue Browser** ~*~* == 8 8 9 - This releasewill introducethenextphase oftheStore to our whole community. With thisnewfunctionalityyou cannowimport data model messages(i.e.CDM, API GatewayData model orEventStreamingdata model) and transformations.Thisway connectingtostandardizedsystems suchas Exact Online,MicrosoftGraph, Salesforce and others will become eveneasier.9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}} 10 10 11 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--current-store-offering.png]]11 +To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests. 12 12 13 - {{info}}Formoreinformationon theStorepleasecheckout this[[course>>doc:Main.eMagizAcademy.Microlearnings.Novice.eMagizStore.WebHome||target="blank"]].Asareminderyoucanfindalldocumentation onallavailableStorecontentpublishedbyeMagiz[[here>>doc:Main.eMagizStore.WebHome||target="blank"]].{{/info}}13 +To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button. 14 14 15 - == **New eMagiz MendixConnector** ==15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]] 16 16 17 - Withthisrelease weintroduce aewversionofthe eMagizMendixConnector.Thisversion(6.0.0) will work bothwiththe currentruntimearchitectureandthenewruntimearchitecturemakingthe migration fromthecurrentruntimearchitectureto thenew runtimearchitectureeasier.The new version ofthe eMagiz MendixConnectorcan befoundin theMendix Marketplaceandn the eMagizportal.17 +After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently 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. 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}} 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 inadvertently put many messages on a queue. 21 +* Clear message from the wiretap queue (Wiretap option) 22 + ** Once you are done with the analysis of a specific 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 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. 20 20 21 - ==**Flow version restore** ~* ==30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] 22 22 23 - On top of that wewillalso launchanew Beta featuretothecommunity that allows you to restoreyour flow toaprevious version. Thisay you can quickly undo changes madethat wereincorrect.32 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]] 24 24 25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 +{{info}}The following restrictions apply to this functionality: 35 + * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message" 36 + * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in. 37 + ** After five minutes the wiretap functionality will be shutdown automatically under water. 38 + ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}} 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}} 40 +== **Message Redelivery ** ~*~* == 32 32 33 - == **Feedback items**==42 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}} 34 34 35 - We haveosolvedotherfeedback itemsidestheflowdesigner's critical updates.44 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]] 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. 46 +As with our current offering, we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience, we have placed this functionality under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred). 39 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. 48 +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. 42 42 43 - [[image:Main.Images.ReleaseBlog.WebHome@186-release-blog--spel-expression-readible.png]]50 +On top of that, we have added some additional functionality. 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. 52 +* Search option 53 + ** Original queue name 54 + ** Original message ID (which can be found as a header called jms_messageid in the error message view) 55 +* Save as test message 56 + ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. 57 +* Download 58 + ** By pressing this button, you can download the message and use it outside of the tooling should that be needed. 47 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. 60 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 50 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. 62 +== **3rd generation runtime bolstering** == 53 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. 64 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 56 56 57 -//__ Enter tocloseautomatedflowtesting pop-up__//58 - Uponyourrequests,wehavemade thepop-updetailingyourautomatedflowtestresults tobe closablebypressingtheEnterkeyonyourkeyboard.Thissavesyouthehassleofgrabbingyourmouse andclickingthebutton.66 +//__Define memory settings for on-premise runtimes from Deploy Architecture__// 67 +With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise. 59 59 60 -//__ Improved namingofdownloadedEventStreamingkeystore__//61 - Whendownloading aKeystorethatanEventStreamingclientneedstoaccessatopic,thename nowincludestheclientname**and**theenvironmentoyoucaneasily discern thedifferencebetweenthe keystoreswhendistributingthem toourclient.69 +//__Empty runtime feedback when deploying a release (or setting the release as active)__// 70 +To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture. 62 62 63 -//__ Pop outntheTracestabwithinFlowTesting__//64 - In linewith the improvementswe made beforewithintheFlow Testingfunctionality,wehavenow addedthe pop-outfunctionalitytoall resultsshowninthetraces tab. Thiswill makeit easiertoanalyzewhat happensbetweenthe startandthend of your flow.72 +//__Auto-fill namespaces for SOAP hosted webservices__// 73 +Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages. 65 65 66 -//__ SortingUserManagement__//67 -As of this release, theuser managementoverviewin Deployforusersandroleswill be sortedalphabeticallyto make it easierto findaspecificuser orrolewithin this overview.75 +//__Updated H2 database setting__// 76 +As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down. 68 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. 78 +{{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}} 71 71 72 -//__ ImprovedupdatefunctionalityofSwaggerfilewhenchanging data model__//73 - Before,therewere specificscenariosin which theSwaggerfilewasnotupdatedaccording tochangesmade to yourAPIdata model. Withthisrelease,wehavemadea firststepinimprovingthis behavior. Then,whenyou change theorderof attributesinyourdatamodel,the Swagger filewillbeupdated accordingly.80 +//__Runtime settings option added to context menu on runtime level Deploy Architecture__// 81 +As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime. 74 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}} 83 +//__Deploy Agent option added to context menu on machine level Deploy Architecture__// 84 +With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]] 76 76 77 -//__ "Disapprove andgotoenvironment"__//78 - Followingthe"Approve and goto environment" functionality, wehavenowxpandedthat by adding the"Disapproveandgotoenvironment"functionality.86 +//__Performance improvement creating a release__// 87 +With this release, we have improved the performance of creating a release. 79 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. 89 +== **Feedback items ** == 82 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. 91 +We have also solved other feedback items besides the flow designer's critical updates. 85 85 86 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] 93 +//__Sensitive information stored in properties is masked __// 94 +We have made how we display sensitive information across the portal similar for various parts of the portal. 87 87 88 -//__ Add Compatibility checkwhenimportingstoreitems__//89 -We have addeda compatibility checktotheplatformtopreventyoufromimportingstore itemsthat do not work on a specific runtimearchitecturetopreventthisfrom happening.96 +//__Importing "Private" store content to which you do not have access__// 97 +We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user. 90 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 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. 100 +== **Bug fixes ** == 96 96 97 -//__ Improvedhelp textsonnext-generationruntime functionalityacross the portal__//98 -W iththis release,we haveimprovedseveral helptextson functionalityrelatedto thenext-generationruntimethathelpyouwhilemigrating to thenext-generationruntime.102 +//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__// 103 +We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality. 99 99 100 -== **Bug Fixes** == 105 +//__Synchronization of Event Streaming topic states__// 106 +We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics. 101 101 102 -//__ Providecorrect feedback when aflow isransferredtoDeploy forhefirst time__//103 -With this release, wehavemadeseveralimprovementstowhat feedbackis giventoheuserwhen moving aflow from Create toDeployfor the first (uponcreatingyourfirstdefinitiveversion).This will ensurethatno confusing pop-ups will be shownthat areincorrectand onlyconfusetheuserfurther.108 +//__Copy and paste default support objects__// 109 +With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow. 104 104 105 -//__ Showinformationin theException of error messagesoverview__//106 -With this release, wehaveresolvedthe bug plaguingthis page.As aresult,youwill againseeinformationon this pagewhenthere is information to show.111 +//__Fix editability of properties when importing store items__// 112 +With this release, you can once again change property names upon importing a store item. 107 107 108 -//__Improve styling of cron trigger configuration pop-up__// 109 -The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again. 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 - 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"]] 118 +* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]] 119 +* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]] 120 +* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]] 121 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 141 141 142 142 == **Key takeaways** == 143 143