Skip to Content

Changes for page 183 - Rainbow World

Last modified by Carlijn Kokkeler on 2024/04/18 13:24
From version 3.1
edited by Erik Bakker
on 2022/08/29 13:59
Change comment: There is no comment for this version
To version 1.1
edited by Erik Bakker
on 2022/08/29 13:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,58 +2,29 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. We will release part of the Manage phase for this new architecture stack with this release. In this release, all-new graphs and dashboards are released to the community. To use them (part of), your solution needs to run on the new architecture stack. On top of that, we have released a new cloud template for our single-lane environments that will unlock technical improvements in the future. Furthermore, we have several smaller feedback items to tell you!
5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Unfortunately, as most of them are not yet ready to be shown to the public, we will keep the details under wrap for now. So for now, the surface is tranquil but soon waves of new features and functionality will arrive on shore!
6 6  
7 -==**Manage Statistics Reimagined**==
8 -As of now, how you manage your environment on the new architecture stack will change drastically. For each segment of statistics we provide (Runtime, Queue, and HTTP), the shown dashboards and graphs have been altered to give you the option to better monitor your running solution. This means we have a "key" page for each segment that highlights the problems and critical areas to focus on.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-key.png]]
11 -
12 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-key.png]]
13 -
14 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-key.png]]
15 -
16 -Once you click on a runtime, queue, or resource, you will navigate to a "detail" page containing the key graphs and various other graphs that will help you monitor your solution.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-detail.png]]
19 -
20 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-detail.png]]
21 -
22 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-detail.png]]
23 -
24 -{{info}}In future releases, we will unlock additional Manage capabilities within the platform, such as alerting and notifications based on the information shown in the graphs.{{/info}}
25 -
26 -==**Cloud Template R22 - Single Lane** ==
27 -This release introduces a new cloud template for all our customers running in a single-lane setup. This cloud template will allow these customers to be migrated in the future to our latest cloud infrastructure advancements. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Release Blogs.Rainbow World.WebHome||target="blank"]]
28 -
7 +==**Build 62** ==
8 +This release introduces build number 62 to our platform. This build number fixes the REST Template model component so that the option "Trust All" (in the advanced tab) can be used as expected. Now that this option works is operational, there is no need to upload a custom trust store anymore.
9 +
29 29  == **Feedback items ** ==
30 30  
31 -We have also solved other feedback items besides the key updates around functionality.
12 +Apart from the key updates around functionality, we have also solved other feedback items.
32 32  
33 -//__Prevent creation of deploy package on auto-saved version__//
34 -With the launch of our new flow designer and due to possible issues when doing a complete model upgrade, we will now make sure that flows that have no definitive version, as the last version can never become a deploy package. On top of that, we provide you with the necessary feedback to take action when such an event occurs.
14 +//__Deletion prevention releases (GEN3)__//
15 +With this release, we have made several improvements on the deletion prevention of releases when running your GEN3 setup.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--prevent-deploy-package-auto-saved-version.png]]
37 -
38 38  == **Bug Fixes** ==
39 39  
40 -//__Various updates when importing store items in Design, including a transformation__//
41 -With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
19 +//__Making sure that the user always ends up in the flow designer overview when opening a flow__//
20 +With this release, we have fixed a bug that caused you to end up in the wrong place when opening a flow in Create.
42 42  
43 -//__Unlock the capability to remove an event processor from Create of which an input or output topic is still used//
44 -With this release, we have unlocked additional functionality under Create -> Settings that allows you to remove event processors of which an input or output topic is still used. This is on top of the standard delete behavior for event processors when both input and output topics can be removed.
45 -
46 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--remove-event-processor-create-settings.png]]
47 -
48 -{{warning}}The same checks and balances apply when you try to remove such an event processor as before. This means that you first need to properly clean up, Manage and Deploy before being able to remove them correctly.{{/warning}}
49 -
50 50  == **Fancy Forum Answers** ==
51 51  
52 52  As always, a gentle reminder to all 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:
53 53  
54 -* [[Can't retrieve message #1 in POP3Message.getContentStream>>https://my.emagiz.com/p/question/172825635703095096||target="blank"]]
55 -* [[html decoding>>https://my.emagiz.com/p/question/172825635703095028||target="blank"]]
56 -* [[pick a file on event>>https://my.emagiz.com/p/question/172825635703107755||target="blank"]]
26 +* [[Max messages per poll SFTP inbound channel remote directory>>https://my.emagiz.com/p/question/172825635700363987||target="blank"]]
27 +* [[Duplicate queues on Production environment>>https://my.emagiz.com/p/question/172825635700364085||target="blank"]]
57 57  
58 58  == **Key takeaways** ==
59 59