Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
Change comment:
There is no comment for this version
To version 303.1
edited by Carlijn Kokkeler
on 2023/12/21 13:37
on 2023/12/21 13:37
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 89-Private Eye1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,80 +1,66 @@ 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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Private Store** == 8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 8 +== **TBD** == 9 9 10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 11 11 12 -== **3rd generation runtime bolstering** == 13 13 14 - Thisrelease will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancementswe madeto the3rd generation runtime and itsinteraction with the portal.12 +== **Feedback Items** == 15 15 16 -//__ SOAP andREST webservices migration including splitting them__//17 -W ith this release,wehaveleasedthemigrationprocessthatwillallowyouo migrateSOAP and REST web servicesto the3rd generation runtimeand at thesametime you candirectly split the all-entry to get rid of that constructionalltogether.A specificmigration pathfor this will bepublishedinthe documentationportal.14 +//__Runtime overview__// 15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 18 18 19 -//__Changing SSL settings for 3rd generation runtime models works__// 20 -As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime. 17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 21 21 22 -//__ Improved migrationforJMS flows__//23 -This re leasewillimprove themigrationofJMS flowswhen migratingtothe3rd generationruntime.19 +//__Missing properties overview__// 20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 24 24 25 -{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 26 26 27 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 -As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 29 29 30 -//__ Deployment planis updatedcorrectly whencompletly migratedtothe 3rd generation runtime architecture__//31 - We havefixed a bugthatgeneratedanincorrectdefault deployment plan onceyouwerefullymigratedto the3rd generationruntime.24 +//__Breaking changes pop-up__// 25 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 32 32 33 - ==**Feedbacktems** ==27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 29 +//__Broker queue metrics dashboards__// 30 +It is now possible to select the MQTT broker in the queue metrics dashboards. 36 36 37 -//__Improved naming convention on Store related pages__// 38 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 32 +== **Bug Fixes** == 39 39 40 -//__ Press "Enter"tosearchonmultiplepages__//41 -In o ur DaemonSwitch release,we addedfunctionality that allowedyoutopress **Enter**to searchon the propertyoverviewpage. Thisrelease hasaddedthisfunctionalitytomanymore pagesacrossthe portal. Thecompletelist is as follows.34 +//__Deployment execution error message__// 35 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 42 42 43 -* Deploy → Deployment Plan 44 -* Deploy → Properties → History 45 -* Deploy → User Management → Roles 46 -* Manage → Error Messages → Error Messages 47 -* Manage → Error Messages → Flows with Error Messages 48 -* Manage → Error Messages → Exceptions of Error Messages 49 -* Manage → Log Entries 50 -* Manage → Alerts 51 -* Manage → Triggers 52 -* Manage → Tags – Cant find (only Gen2) 53 -* Manage → Notifications 54 -* Manage → Notification Settings 55 -* Manage → Data Usage → History 56 -* Manage → Code mappings → All tabs 37 +//__Cloud template upgrade unjust rollback__// 38 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 57 57 58 -== **Bug fixes ** == 40 +//__Missing log entries__// 41 +We improved crash handling so that log messages clearly show when and why a container failed to start. 59 59 60 -//__ Loading problems of Deploymentplan execution overview__//61 -We havefixed aproblemthatcouldcauseissues when tryingtoshowthe deploymentplanexecution overviewafter pressingtheDeploy buttonDeploy -> Releases.43 +//__Runtime logging__// 44 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 62 62 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: 66 66 67 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 68 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 69 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 70 70 56 + 71 71 == **Key takeaways** == 72 72 73 -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:59 +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: 74 74 75 75 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 76 76 * If you have feedback or ideas for us, talk to the Platypus 77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 63 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 78 * Clear your browser cache (Ctrl + Shift + Del) 79 79 * Check out the release notes [here] 80 80 * Start thinking about how the license tracker can aid your development ... ... @@ -87,6 +87,12 @@ 87 87 {{info}} 88 88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 90 -~*~* Indicates a GEN3-only feature. 91 -{{/info}})))((({{toc/}}))){{/container}} 76 +~*~* Indicates a next-generation-architecture only feature. 77 +{{/info}} 78 +))) 79 + 80 +((( 81 +{{toc/}} 82 +))) 92 92 {{/container}} 84 +{{/container}}