Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
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 392.1
edited by CarlijnKokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +214 - System Symphony
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,85 +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!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
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 +== **Feedback Items** ==
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}}
10 +//__On premise Windows machines__//
11 +We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
11 11  
12 -== **3rd generation runtime bolstering** ==
13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
14 + [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]]
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.
16 +//__Adding multiple attributes__//
17 +It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity.
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.
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
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 +//__Monitoring graphs__//
22 +The monitoring graphs can now show data up to the last thirty days.
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 +== **Bug Fixes** ==
25 +//__Image versions__//
26 +To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way:
27 +* The deletion of releases with deployed container versions will not be blocked anymore.
28 +* Automated release clean up behaviour will also not exclude these releases from deletion.
29 +* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
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}}
31 +//__Failover group helptext__//
32 +The helptext of the Group attribute has been improved.
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.
34 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
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.
36 +//__Failover group refresh__//
37 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
32 32  
33 -== **Feedback items ** ==
39 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
41 +//__Resource paths__//
42 +After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed.
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.
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.
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
57 -
58 -== **Bug fixes ** ==
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 -
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"]]
48 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
49 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
50 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
51 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
70 70  
71 -== **Key takeaways** ==
53 +== **Key Takeaways** ==
72 72  
73 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
55 +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.
59 +* 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
81 81  * Start thinking about major, minor, and patch
82 -* Upgrade to the latest build number
83 83  * Keep making great integrations
84 84  
85 85  Let's stay in touch and till next time!
... ... @@ -87,6 +87,11 @@
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}}
71 +{{/info}}
72 +)))
73 +
74 +(((
75 +{{toc/}}
76 +)))
92 92  {{/container}}
78 +{{/container}}