Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
Change comment: There is no comment for this version
To version 89.1
edited by Erik Bakker
on 2023/03/14 06:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +194 - Big Leap
Content
... ... @@ -2,71 +2,78 @@
2 2  {{container layoutStyle="columns"}}(((
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.
5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
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).
7 +== **3rd generation improvements** ==
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}}
9 +//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
11 11  
12 -== **3rd generation runtime bolstering** ==
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
13 13  
14 -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.
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
15 15  
16 -//__SOAP and REST web services migration including splitting them__//
17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
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.
21 +//__Improved process of deploy preparation__//
22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
21 21  
22 -//__Improved migration for JMS flows__//
23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
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}}
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
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.
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
29 29  
30 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
33 +//__Improved help text for network volumes__//
34 +With this release we have improved the help text that explains network volumes and how to use them within our solution.
32 32  
33 -== **Feedback items ** ==
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
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.
38 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
39 39  
40 -//__Press "Enter" to search on multiple pages__//
41 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
40 +== **WS-Security on the 3rd generation runtime** ~*~* ==
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
42 +To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
57 57  
44 +== **State Generation ~*~* ==
45 +
46 +With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
47 +
48 +{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
49 +
50 +== **Feedback items ** ==
51 +
52 +//__Removed OData as option for an API Gateway operation__//
53 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
54 +
55 +//__Changes in API Gateway operation paths is automatically updated in Create__//
56 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
57 +
58 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
59 +
58 58  == **Bug fixes ** ==
59 59  
60 -//__Loading problems of Deployment plan execution overview__//
61 -We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
62 +//__Prevent endless loop in Deploy -> User Management__//
63 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
62 62  
65 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
66 +
67 +//__Update error handling during migration to the 3rd generation runtime__//
68 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
69 +
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"]]
74 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
75 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
76 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
70 70  
71 71  == **Key takeaways** ==
72 72