Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
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 551.1
edited by CarlijnKokkeler
on 2024/06/17 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +223 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,85 +1,59 @@
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!**
7 +
8 +== **Feedback Items** ==
9 +//__SwaggerUI default__//
10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
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).
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
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}}
14 +== **Bug Fixes** ==
15 +//__Cron triggers__//
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
11 11  
12 -== **3rd generation runtime bolstering** ==
18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.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.
20 +//__Trigger activation__//
21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
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.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
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.
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
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.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
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 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
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 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
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.
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
32 32  
33 -== **Feedback items ** ==
34 -
35 -We have also solved other feedback items besides the flow designer's critical updates.
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"]]
43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
70 70  
71 -== **Key takeaways** ==
46 +== **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:
48 +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.
52 +* 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 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
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}}
64 +{{/info}}
65 +)))
66 +
67 +(((
68 +{{toc/}}
69 +)))
92 92  {{/container}}
71 +{{/container}}