Changes for page 180 - Deck Paint

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,130 +2,55 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have looked back and ahead to the upcoming Q within the IP week and through our PI planning in the last several weeks. Apart from planning new functionalities and improvements, we have also finished up loads of smaller items available with this release. Among these are transformation improvements, flow testing improvements, and consistency improvements. On top of that, we have also updated our cloud template to bring the latest infrastructural updates to you. So let us dive into all we have to offer this time!
	5	+**Hi there, eMagiz developers!** We have started on various features we planned for this Q. Unfortunately, as most of them are not yet ready to be shown to the public, we will keep the details under wrap for now. But do not despair, as there is still enough released today to sink your teeth in. Among others, we have revamped our documentation portal by improving the look and feel and expanding the capabilities. On top of that, we have made UI updates across the portal and fixed several feedback points!
6	6
7		-== **New cloud template** ==
	7	+== **Revamped Documentation Portal** ==
8	8
9		-This release will introduce a new cloud template suited for your cloud slot. With this new cloud template, we will deliver several security patches and improve the way unattended updates are controlled. For specific information, please check out the release notes.
	9	+//__New Location and UI__//
	10	+With this release we will make the revamped documentation portal available to our community. You can access the documentation portal via the eMagiz portal under community or you can directly access the documentation portal at https://docs.emagiz.com/
10	10
11		-Note that the new cloud template will be automatically applied to your environment if you have configured this functionality on your cloud slot.
	12	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--documentation-portal-access-from-the-emagiz-portal.png]]
12	12
13		-== **Transformation Improvements** ==
	14	+On the documentation portal we have updated the look and feel of the portal slightly based on feedback gathered from the community. When you navigate to the documentation portal the first time you will be prompted with a Tour which you can take to learn about the portal.
14	14
15		-//__Toggle between Design and Create__//
16		-This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design.
	16	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--tour-doc-portal-ui-sneak-peek.png]]
17	17
18		-//__Improved Transformation options for booleans__//
19		-On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks.
	18	+//__Store Documentation__//
	19	+New to the documentation portal is a segment on all our store content. In here we define all relevant documentation for each of the store items that are currently available within the eMagiz Store.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
	21	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--store-documentation.png]]
22	22
	23	+//__Release Information__//
	24	+New to the documentation portal is a segment on our release information. In here we define all relevant release information for all components of the eMagiz product.
	25	+
	26	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--release-information.png]]
	27	+
23	23	== **Feedback items ** ==
24	24
25	25	Apart from the key updates around functionality, we have also solved other feedback items.
26	26
27		-//__Correctly define the size of a cloud slot when creating it for the first time__//
28		-Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted.
	32	+//__Update the UI__//
	33	+The underlying version of our UI engine has been updated. This will unlock additional capabilities towards the future. For now, we have kept the changes minimal based on feedback received on the current UI.
29	29
30		-//__Updated infographic Capture__//
31		-As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
	35	+//__Various updates on the Store functionality__//
	36	+With this release, we have made several improvements for importing store items. This will further bolster our offering on the Store.
32	32
33		-//__Updated error feedback in Design__//
34		-Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown.
35		-
36		-//__Improved styling of Topic Storage in Design Architecture__//
37		-When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone.
38		-
39		-//__Improved styling of error feedback on User Management in Deploy__//
40		-With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
41		-
42		-//__Show only the ten latest flow versions when selecting a flow version in a Release__//
43		-To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
44		-
45		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
46		-
47		-//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__//
48		-Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification.
49		-
50		-//__Clear API Gateway System message__//
51		-With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level.
52		-
53		-//__Additional information in Property History__//
54		-To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes.
55		-
56		-//__Save Tag when ready__//
57		-With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model.
58		-
59		-//__View deployment step information when having view rights__//
60		-With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment.
61		-
62		-//__Validating external recipients in notification settings__//
63		-Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values.
64		-
65		-//__Automatically link enumeration list to attribute__//
66		-When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually.
67		-
68		-//__Approve and go to environment__//
69		-With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment.
70		-
71		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
72		-
73		-//__Remove irrelevant information on a runtime in Design Architecture__//
74		-We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below.
75		-
76		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
77		-
78		-//__Add question about message redelivery in Capture__//
79		-When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution.
80		-
81		-//__Prevent pressing “Apply to environment” multiple times leading to conflicts__//
82		-With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period.
83		-
84		-//__Add “State” to the topic details in Deploy Architecture__//
85		-Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched.
86		-
87		-//__Improved stability of logging on the Gen3 Architecture__//
88		-With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally.
89		-
90	90	== **Bug Fixes** ==
91	91
92	92	//__Various updates when importing store items in Design including a transformation__//
93	93	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.
94	94
95		-//__Opening flow testing widget in specific circumstances was not working__//
96		-With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.”
97		-
98		-//__Improved styling when adding a large message to a flow test__//
99		-With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message.
100		-
101		-//__Errors on the UI do not keep following me__//
102		-Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete.
103		-
104		-//__Navigating back to the transformation in Create works again__//
105		-With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see.
106		-
107		-//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__//
108		-With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz.
109		-
110		-//__Selecting tags when drawing a line in Capture__//
111		-We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture.
112		-
113		-//__Remove invalid selection when configuring a cron trigger via the tooling__//
114		-With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution.
115		-
116	116	== **Fancy Forum Answers** ==
117	117
118	118	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:
119	119
120		-* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
121		-* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
122		-* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
	47	+* [[Model Attribute not parsed as XSD attribute>>https://my.emagiz.com/p/question/172825635700363785||target="blank"]]
123	123
124	124	== **Key takeaways** ==
125	125
126	126	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:
127	127
128		-* If you have questions surrounding our Program Increment Planning, please get in touch with
	53	+* If you have questions surrounding our Program Increment Planning, please get in touch with
129	129	* If you have feedback or ideas for us, talk to the Platypus
130	130	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
131	131	* Clear your browser cache (Ctrl + Shift + Del)
...	...	@@ -134,6 +134,7 @@
134	134	* Start thinking about major, minor, and patch
135	135	* Upgrade to the latest build number
136	136	* Keep making great integrations
	62	+* Check out the new documentation portal.
137	137
138	138	Let's stay in touch and till next time!
139	139