Wiki source code of 183 - Rainbow World
Last modified by Carlijn Kokkeler on 2024/04/18 13:24
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 4 | |||
| |
6.1 | 5 | **Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. We will release an important part of the Manage phase for this new architecture stack. In this release, all-new graphs and dashboards are released to the community. To use them (part of), your solution needs to run on the new architecture stack. On top of that, we have released a new cloud template for our single-lane environments that will unlock technical improvements in the future. Furthermore, we have several smaller feedback items to share! |
| |
1.1 | 6 | |
| |
6.1 | 7 | ==**Manage Statistics revamped**== |
| 8 | |||
| 9 | As of now, how you manage your environment on the new architecture stack will change drastically. For each segment of statistics we provide (Runtime, Queue, and HTTP), the dashboards and graphs as shown below have been altered to give you the option to better monitor your working solution. This means we have a "key" page for each segment that highlights the problems and critical areas to focus on. | ||
| |
3.1 | 10 | |
| 11 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-key.png]] | ||
| 12 | |||
| 13 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-key.png]] | ||
| 14 | |||
| 15 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-key.png]] | ||
| 16 | |||
| |
7.1 | 17 | Once you click on a runtime, queue, or resource, you will navigate to a detailed page containing the key graphs & metrics and various other graphs that will help you monitor your solution. |
| |
3.1 | 18 | |
| 19 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-detail.png]] | ||
| 20 | |||
| 21 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-detail.png]] | ||
| 22 | |||
| 23 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-detail.png]] | ||
| 24 | |||
| 25 | {{info}}In future releases, we will unlock additional Manage capabilities within the platform, such as alerting and notifications based on the information shown in the graphs.{{/info}} | ||
| 26 | |||
| 27 | ==**Cloud Template R22 - Single Lane** == | ||
| |
7.1 | 28 | |
| |
11.1 | 29 | This release introduces a new cloud template for all our customers running in a single-lane setup. This cloud template will allow these customers to be migrated in the future to our latest cloud infrastructure advancements. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] |
| |
3.1 | 30 | |
| |
1.1 | 31 | == **Feedback items ** == |
| 32 | |||
| |
3.1 | 33 | We have also solved other feedback items besides the key updates around functionality. |
| |
1.1 | 34 | |
| |
3.1 | 35 | //__Prevent creation of deploy package on auto-saved version__// |
| |
10.1 | 36 | 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. |
| |
1.1 | 37 | |
| |
3.1 | 38 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--prevent-deploy-package-auto-saved-version.png]] |
| 39 | |||
| |
1.1 | 40 | == **Bug Fixes** == |
| 41 | |||
| |
3.1 | 42 | //__Various updates when importing store items in Design, including a transformation__// |
| 43 | 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. | ||
| |
1.1 | 44 | |
| |
4.1 | 45 | //__Unlock the capability to remove an event processor from Create of which an input or output topic is still used__// |
| |
3.1 | 46 | 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. |
| 47 | |||
| 48 | [[image:Main.Images.Release Blog.WebHome@183-release-blog--remove-event-processor-create-settings.png]] | ||
| 49 | |||
| 50 | {{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}} | ||
| 51 | |||
| |
1.1 | 52 | == **Fancy Forum Answers** == |
| 53 | |||
| 54 | 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: | ||
| 55 | |||
| |
3.1 | 56 | * [[Can't retrieve message #1 in POP3Message.getContentStream>>https://my.emagiz.com/p/question/172825635703095096||target="blank"]] |
| 57 | * [[html decoding>>https://my.emagiz.com/p/question/172825635703095028||target="blank"]] | ||
| 58 | * [[pick a file on event>>https://my.emagiz.com/p/question/172825635703107755||target="blank"]] | ||
| |
1.1 | 59 | |
| |
5.1 | 60 | == **Special Announcement** == |
| 61 | |||
| |
10.1 | 62 | {{info}}In the upcoming release, a new version of the flow designer will be released to the community, so keep your eyes open.{{/info}} |
| |
5.1 | 63 | |
| |
1.1 | 64 | == **Key takeaways** == |
| 65 | |||
| 66 | 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: | ||
| 67 | |||
| 68 | * If you have questions surrounding our Program Increment Planning, please get in touch with | ||
| 69 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 70 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 71 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| |
13.1 | 72 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.Rainbow World.WebHome||target="blank"]] |
| |
1.1 | 73 | * Start thinking about how the license tracker can aid your development |
| 74 | * Start thinking about major, minor, and patch | ||
| 75 | * Upgrade to the latest build number | ||
| 76 | * Keep making great integrations | ||
| 77 | * Check out the new documentation portal. | ||
| 78 | |||
| 79 | Let's stay in touch and till next time! | ||
| 80 | |||
| 81 | {{info}} | ||
| 82 | ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 83 | |||
| 84 | ~*~* Indicates a GEN3-only feature. | ||
| 85 | {{/info}})))((({{toc/}}))){{/container}} | ||
| 86 | {{/container}} |