Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 438.1
edited by CarlijnKokkeler
on 2024/04/08 11:22
Change comment: There is no comment for this version
To version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +189 - Private Eye
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,79 +1,85 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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.
7 7  
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 8  
9 -== **Spring 6 Migration** ==
10 -As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release.
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}}
11 11  
12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 -* JDBC BoneCP data source
14 -* SSL web service message sender
15 -* Web service outbound gateway
16 -* SFTP session factory
17 -* HTTP components message sender
18 -* Job manager
19 -* Credentials
20 -* Simple job launcher
21 -* Default SFTP session factory
12 +== **3rd generation runtime bolstering** ==
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
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.
24 24  
25 -In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
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.
26 26  
27 -== **Feedback Items** ==
28 -//__Dynamic trigger__//
29 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
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.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
32 32  
33 -//__Copy to clipboard buttons__//
34 -Copy to clipboard buttons have been added to various pages:
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}}
35 35  
36 - * Deploy agent pop-up
37 - * Create - Flow designer: Properties
38 - * Deploy - Property releases: Property details
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.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
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.
41 41  
42 -//__Reset H2 database__//
43 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.
33 +== **Feedback items ** ==
44 44  
45 -{{info}}Please note the following:
35 +We have also solved other feedback items besides the flow designer's critical updates.
46 46  
47 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
48 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
49 -* For on-premise runtimes, only a reset of the runtime is needed.
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.
50 50  
51 -For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}}
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.
52 52  
53 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
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
54 54  
55 -== **Bug Fixes** ==
56 -//__Runtime overview improvements__//
57 -The runtime overview has been improved regarding checks on the runtime version.
58 +== **Bug fixes ** ==
58 58  
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 +
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
64 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
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"]]
65 65  
66 -== **Key Takeaways** ==
71 +== **Key takeaways** ==
67 67  
68 -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:
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:
69 69  
70 70  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 74  * Check out the release notes [here]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
82 +* Upgrade to the latest build number
77 77  * Keep making great integrations
78 78  
79 79  Let's stay in touch and till next time!
... ... @@ -81,11 +81,6 @@
81 81  {{info}}
82 82  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 83  
84 -{{/info}}
85 -)))
86 -
87 -(((
88 -{{toc/}}
89 -)))
90 +~*~* Indicates a GEN3-only feature.
91 +{{/info}})))((({{toc/}}))){{/container}}
90 90  {{/container}}
91 -{{/container}}