Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 279.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,64 +1,81 @@
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!** We have...
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.
7 7  
8 -== **Release Maintenance** ==
7 +== **3rd generation runtime bolstering** ==
9 9  
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 10  
11 +//__Migration of JMS backup configuration improved__//
11 11  
13 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
12 12  
15 +//__Autogenerated exits can be deployed at once__//
13 13  
14 -== **Feedback Items** ==
17 +//__Code mapping functionality available on 3rd generation runtime__//
15 15  
16 -//__Container version overview__//
17 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
19 +//__Improved the performance of deploying or activating a release__//
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
21 +//__Failing runtimes won't be restarted indefinetly anymore__//
20 20  
21 -//__Unchanged containers__//
22 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 +== **Exportable Release Audit** ~* ==
23 23  
24 -//__Rebuilding of images__//
25 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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.
26 26  
27 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
27 27  
28 -== **Bug Fixes** ==
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}}
29 29  
30 -//__Runtime metrics processing__//
31 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
35 +== **Feedback items ** ==
32 32  
33 -//__Deployment plan__//
34 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37 +We have also solved other feedback items besides the flow designer's critical updates.
35 35  
36 -//__Store message merging__//
37 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
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.
38 38  
39 -//__View all store items__//
40 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
42 +//__Improved naming convention on Store related pages__//
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.
41 41  
42 -//__Out of memory behavior__//
43 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
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
44 44  
45 -//__Max fetch size__//
46 -We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
47 -
48 +* Deploy → Deployment Plan
49 +* Deploy → Properties → History
50 +* Deploy → User Management → Roles
51 +* Manage → Error Messages → Error Messages
52 +* Manage → Error Messages → Flows with Error Messages
53 +* Manage → Error Messages → Exceptions of Error Messages
54 +* Manage → Log Entries
55 +* Manage → Alerts
56 +* Manage → Triggers
57 +* Manage → Tags – Cant find (only Gen2)
58 +* Manage → Notifications
59 +* Manage → Notification Settings
60 +* Manage → Data Usage → History
61 +* Manage → Code mappings → All tabs
48 48  
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
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"]]
54 54  
55 55  == **Key takeaways** ==
56 56  
57 -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 +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:
58 58  
59 59  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 63  * Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
... ... @@ -71,12 +71,6 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 -~*~* Indicates a next-generation-architecture only feature.
75 -{{/info}}
76 -)))
77 -
78 -(((
79 -{{toc/}}
80 -)))
91 +~*~* Indicates a GEN3-only feature.
92 +{{/info}})))((({{toc/}}))){{/container}}
81 81  {{/container}}
82 -{{/container}}