Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 55.1
edited by Erik Bakker
on 2022/11/24 11:53
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +192 - Small Step
Content
... ... @@ -2,76 +2,56 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. 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 worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6 6  
7 -== **3rd generation runtime bolstering** ==
7 +== **Start/Stop Flows** ~*~* ==
8 8  
9 -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.
9 +{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -//__Migration of JMS backup configuration improved__//
12 -With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
11 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
13 13  
14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
16 16  
17 -//__Autogenerated exits can be deployed at once__//
18 -This release has fixed a bug that prevented you from deploying an exit flow correctly.
15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
19 19  
20 -//__Code mapping functionality available on 3rd generation runtime__//
21 -As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -//__Failing runtimes won't be restarted indefinitely anymore__//
24 -We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
25 25  
26 -== **Exportable Release Audit** ~* ==
21 +== **Manage overview Event Streaming** ~*~* ==
27 27  
28 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
31 31  
32 -{{warning}}Note that the following restrictions apply when exporting an audit document:
33 - * Works **only** for releases that are promoted and made active on **Production**
34 - * You will **only** see changes made during the **current** calendar year
35 - * On the first of April all objects of the **last** calendar year will be **removed**.
36 - ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
37 -
38 38  == **Feedback items ** ==
39 39  
40 40  We have also solved other feedback items besides the flow designer's critical updates.
41 41  
42 -//__Improved naming convention on Store related pages__//
43 -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.
31 +//__Topic configuration calculation__//
32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
44 44  
45 -//__Press "Enter" to search on multiple pages__//
46 -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.
34 +//__Make preparation step in deployment plan visible__//
35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
47 47  
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
62 62  
63 -== **Bug fixes ** ==
39 +//__3rd generation runtime debugger feedback__//
40 +We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
64 64  
65 -//__Loading problems of Deployment plan execution overview__//
66 -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.
42 +//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 +As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
67 67  
45 +//__User Management synchronization now happens in one step__//
46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
47 +
68 68  == **Fancy Forum Answers** ==
69 69  
70 70  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:
71 71  
72 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
52 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 +* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 +* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
75 75  
76 76  == **Key takeaways** ==
77 77