Changes for page 182 - Tranquil Surface

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-#178 - Foundational Work
	1	+180 - Deck Paint

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Content

...	...	@@ -1,49 +1,57 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}(((
2	2	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
3	3
4		-**Hi there, eMagiz developers!** In the last couple of weeks, we have worked on various main platform features. Sadly they are not yet ready enough to release to you guys. We did, however, improve the platform in different more minor ways. Among these improvements, we have improved the speed of handling error messages and creating models by hand. Furthermore, we have several more minor improvements and bug fixes for you. So let us dive into all that we have to offer this time around!
	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!
5	5
6		-== **Save and Add Attributes** ==
	7	+== **Revamped Documentation Portal** ==
7	7
8		-When adding multiple attributes by hand to a data model, you need to access the context menu, select the option Add attribute, add the attribute, Save the attribute and repeat that process for every single attribute. We have now introduced a new option when adding attributes to your data models and system messages to speed up this process. This way, you can save and add another attribute by pressing the “Save and add new” button. This way, you don't have to navigate via the context menu for every attribute you want to save.
	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/
9	9
10		-[[image:Main.Images.Release Blog.WebHome@time-saver--save-and-add-attributes.png]]
	12	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--documentation-portal-access-from-the-emagiz-portal.png]]
11	11
12		-== **Other Feedback items ** ==
	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.
13	13
14		-Apart from the hide/show tasks functionality, we have also solved other feedback items.
	16	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--tour-doc-portal-ui-sneak-peek.png]]
15	15
16		-//__Make Flow Testing available for the new generation runtime__//
17		-As of this release, the flow testing functionality is also made available for all processes that already run the new generation runtime (GEN3).
	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.
18	18
19		-== **Bug Fixes** ==
	21	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--store-documentation.png]]
20	20
21		-//__Being able to delete data model entities that are in use__//
	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.
22	22
23		-Previously, it was possible to delete an entity on the data model level that was still in use in a transformation. This could lead to catastrophic problems when someone unintentionally deleted an essential entity for many transformations. As of this release, we have implemented a check that prevents you from deleting any entity still in use in a message or transformation.
	26	+[[image:Main.Images.Release Blog.WebHome@180-release-blog--release-information.png]]
24	24
25		-//__Reserved property names__//
	28	+== **Feedback items ** ==
26	26
27		-As of this release, we have defined various forbidden names for properties. One example is creating any property that starts with emagiz. This way, we prevent problems when starting up your solution.
	30	+Apart from the key updates around functionality, we have also solved other feedback items.
28	28
29		-//__When importing Store items the associated resource is not always provided to the user__//
	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.
30	30
31		-Previously, you could import items from the store without receiving the associated resource rendering the import useless. With this release, we made sure that you also get the resource with it when importing the store item.
	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
	38	+== **Bug Fixes** ==
	39	+
	40	+//__Various updates when importing store items in Design including a transformation__//
	41	+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.
	42	+
33	33	== **Fancy Forum Answers** ==
34	34
35	35	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:
36	36
37		-* [[Is it possible to split a JSON message into multiple smaller messages and how is this possible?>>https://my.emagiz.com/p/question/172825635700362585||target="blank"]]
38		-* [[URI is not absolute>>https://my.emagiz.com/p/question/172825635700362186||target="blank"]]
39		-* [[JSON array is null>>https://my.emagiz.com/p/question/172825635700362586||target="blank"]]
	47	+* [[Model Attribute not parsed as XSD attribute>>https://my.emagiz.com/p/question/172825635700363785||target="blank"]]
40	40
41	41	== **Key takeaways** ==
42	42
43	43	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:
44	44
45		-* If you have questions surrounding our Program Increment Planning, please get in touch with
46		-* If you have feedback or ideas for us, talk to the platypus
	53	+* If you have questions surrounding our Program Increment Planning, please get in touch with
	54	+* If you have feedback or ideas for us, talk to the Platypus
47	47	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48	48	* Clear your browser cache (Ctrl + Shift + Del)
49	49	* Check out the release notes [here]
...	...	@@ -51,6 +51,7 @@
51	51	* Start thinking about major, minor, and patch
52	52	* Upgrade to the latest build number
53	53	* Keep making great integrations
	62	+* Check out the new documentation portal.
54	54
55	55	Let's stay in touch and till next time!
56	56
...	...	@@ -58,4 +58,5 @@
58	58	~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59	59
60	60	~*~* Indicates a GEN3-only feature.
61		-{{/info}})))((({{toc/}}))){{/container}}{{/container}}
	70	+{{/info}})))((({{toc/}}))){{/container}}
	71	+{{/container}}