Skip to Content

Changes for page 190 - Fast Forward

Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
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 -188 - Close Encounters
1 +189 - Private Eye
Content
... ... @@ -2,48 +2,43 @@
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 the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
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 6  
7 -== **3rd generation runtime bolstering** ==
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 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
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 10  
11 -//__Migration of JMS backup configuration improved__//
12 +== **3rd generation runtime bolstering** ==
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
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.
14 14  
15 -//__Autogenerated exits can be deployed at once__//
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.
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
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.
18 18  
19 -//__Improved the performance of deploying or activating a release__//
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
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}}
22 22  
23 -== **Exportable Release Audit** ~* ==
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.
24 24  
25 -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.
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
28 -
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34 -
35 35  == **Feedback items ** ==
36 36  
37 37  We have also solved other feedback items besides the flow designer's critical updates.
38 38  
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
41 -
42 42  //__Improved naming convention on Store related pages__//
43 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.
44 44  
45 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. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
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.
47 47  
48 48  * Deploy → Deployment Plan
49 49  * Deploy → Properties → History
... ... @@ -60,14 +60,18 @@
60 60  * Manage → Data Usage → History
61 61  * Manage → Code mappings → All tabs
62 62  
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 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||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"]]
71 71  
72 72  == **Key takeaways** ==
73 73