Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 51.1
edited by Erik Bakker
on 2022/11/21 13:40
on 2022/11/21 13:40
Change comment:
There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
on 2022/11/21 13:09
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -30,16 +30,21 @@ 30 30 31 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. 32 32 33 -[[image:Main.Images.Release Blog.WebHome@18 8-release-blog--exportable-release-audit.png]]33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 34 35 35 {{warning}}Note that the following restrictions apply when exporting an audit document: 36 - * Works **only** for releases that are promoted and made active on Production 37 - * You will **only** see changes made during the **current** calendar year{{/warning}} 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}} 38 38 39 39 == **Feedback items ** == 40 40 41 41 We have also solved other feedback items besides the flow designer's critical updates. 42 42 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. 47 + 43 43 //__Improved naming convention on Store related pages__// 44 44 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. 45 45