Skip to Content

Changes for page 184 - New Beginnings

Last modified by Carlijn Kokkeler on 2024/04/18 13:23
From version 10.1
edited by eMagiz
on 2022/09/13 14:24
Change comment: There is no comment for this version
To version 11.1
edited by eMagiz
on 2022/09/13 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,35 +41,19 @@
41 41  
42 42  We have also solved other feedback items besides the key updates around functionality.
43 43  
44 -//__Prevent creation of deploy package on auto-saved version__//
45 -With the launch of our new flow designer and due to possible issues when doing a complete model upgrade, we will now make sure that flows that have no definitive version, as the last version can never become a deploy package. On top of that, we provide you with the necessary feedback to take action when such an event occurs. Effectively it means that a new version needs to be pushed to Deploy including the updates made to the flow.
44 +//__Set runtime field as first selected field on property level__//
45 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--prevent-deploy-package-auto-saved-version.png]]
47 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
48 +
48 48  
49 -== **Bug Fixes** ==
50 -
51 -//__Various updates when importing store items in Design, including a transformation__//
52 -With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
53 -
54 -//__Unlock the capability to remove an event processor from Create of which an input or output topic is still used__//
55 -With this release, we have unlocked additional functionality under Create -> Settings that allows you to remove event processors of which an input or output topic is still used. This is on top of the standard delete behavior for event processors when both input and output topics can be removed.
56 -
57 -[[image:Main.Images.Release Blog.WebHome@183-release-blog--remove-event-processor-create-settings.png]]
58 -
59 -{{warning}}The same checks and balances apply when you try to remove such an event processor as before. This means that you first need to properly clean up, Manage and Deploy before being able to remove them correctly.{{/warning}}
60 -
61 61  == **Fancy Forum Answers** ==
62 62  
63 63  As always, a gentle reminder to all 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:
64 64  
65 -* [[Can't retrieve message #1 in POP3Message.getContentStream>>https://my.emagiz.com/p/question/172825635703095096||target="blank"]]
66 -* [[html decoding>>https://my.emagiz.com/p/question/172825635703095028||target="blank"]]
67 -* [[pick a file on event>>https://my.emagiz.com/p/question/172825635703107755||target="blank"]]
54 +* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]]
55 +* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]]
68 68  
69 -== **Special Announcement** ==
70 -
71 -{{info}}In the upcoming release, a new version of the flow designer will be released to the community, so keep your eyes open.{{/info}}
72 -
73 73  == **Key takeaways** ==
74 74  
75 75  Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: