Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
Change comment: There is no comment for this version
To version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +213 - Joyful Journeys
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,91 +1,94 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 +**Hi there, eMagiz developers!** This release ....
6 6  
7 -== **3rd generation runtime bolstering** ==
8 +== **Pop-up Improvements** ==
9 +//__Property releases__//
10 +When a new property release is created, this property release can now be viewed and deleted.
8 8  
9 -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.
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
10 10  
11 -//__Migration of JMS backup configuration improved__//
12 -With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
14 +//__Runtime deletion__//
15 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
13 13  
14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
17 +//__Wiretap & debug error messages__//
18 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
16 16  
17 -//__Autogenerated exits can be deployed at once__//
18 -This release has fixed a bug that prevented you from deploying an exit flow correctly.
20 +//__Action messages__//
21 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
19 19  
20 -//__Code mapping functionality available on 3rd generation runtime__//
21 -As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
23 +== **Formatting & Alignments** ==
22 22  
23 -//__Improved the performance when activating a release__//
24 -With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
25 +//__Input fields__//
26 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
25 25  
26 -//__Failing runtimes won't be restarted indefinitely anymore__//
27 -We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
28 +//__UI improvements__//
29 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
28 28  
29 -== **Exportable Release Audit** ~* ==
31 +//__Runtime overview image versions__//
32 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
30 30  
31 -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.
34 +//__Component changes reversion__//
35 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
37 +//__State generation statistics__//
38 +The state generation graphs will now show the correct number of cache hits and misses.
34 34  
35 -{{warning}}Note that the following restrictions apply when exporting an audit document:
36 - * Changes made on definition and transformation level are **not** restored
37 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 - * 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
39 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40 +//__Queue browser timestamps__//
41 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
40 40  
41 -== **Feedback items ** ==
43 +//__Addition and deletion of internal recipients__//
44 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
42 42  
43 -We have also solved other feedback items besides the flow designer's critical updates.
46 +== **Feedback Items** ==
44 44  
45 -//__Data Sink Refactor__//
46 -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 you separately.
48 +//__Update flows__//
49 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
47 47  
48 -//__Improved naming convention on Store related pages__//
49 -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.
51 +//__Q&A forum search__//
52 +The option to search by pressing the Enter key has been added to the Q&A forum.
50 50  
51 -//__Press "Enter" to search on multiple pages__//
52 -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.
54 +//__Memory settings__//
55 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
53 53  
54 -* Deploy → Deployment Plan
55 -* Deploy → Properties → History
56 -* Deploy → User Management → Roles
57 -* Manage → Error Messages → Error Messages
58 -* Manage → Error Messages → Flows with Error Messages
59 -* Manage → Error Messages → Exceptions of Error Messages
60 -* Manage → Log Entries
61 -* Manage → Alerts
62 -* Manage → Triggers
63 -* Manage → Tags – Cant find (only Gen2)
64 -* Manage → Notifications
65 -* Manage → Notification Settings
66 -* Manage → Data Usage → History
67 -* Manage → Code mappings → All tabs
57 +//__Runtime validation__//
58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
68 68  
60 +
61 +== **Bug Fixes** ==
62 +
63 +//__Removal of onramp__//
64 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
65 +
66 +//__Runtime statistics details__//
67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
68 +
69 +//__Deployment prechecks__//
70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
71 +
72 +
69 69  == **Fancy Forum Answers** ==
70 70  
71 71  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:
72 72  
73 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
77 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
78 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
79 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
76 76  
77 -== **Key takeaways** ==
81 +== **Key Takeaways** ==
78 78  
79 -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:
83 +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:
80 80  
81 81  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82 82  * If you have feedback or ideas for us, talk to the Platypus
83 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
87 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84 84  * Clear your browser cache (Ctrl + Shift + Del)
85 85  * Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
87 87  * Start thinking about major, minor, and patch
88 -* Upgrade to the latest build number
89 89  * Keep making great integrations
90 90  
91 91  Let's stay in touch and till next time!
... ... @@ -93,6 +93,11 @@
93 93  {{info}}
94 94  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95 95  
96 -~*~* Indicates a GEN3-only feature.
97 -{{/info}})))((({{toc/}}))){{/container}}
99 +{{/info}}
100 +)))
101 +
102 +(((
103 +{{toc/}}
104 +)))
98 98  {{/container}}
106 +{{/container}}