Wiki source code of 222 - Flee Frustration
Version 548.1 by CarlijnKokkeler on 2024/06/03 16:00
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| |
254.1 | 2 | {{container layoutStyle="columns"}} |
| 3 | ((( | ||
| |
401.1 | 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] |
| |
1.1 | 5 | |
| |
544.1 | 6 | **Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes! |
| |
410.1 | 7 | |
| |
464.1 | 8 | == **Feedback Items** == |
| |
538.1 | 9 | //__Cron triggers__// |
| |
548.1 | 10 | Cron triggers now allow for hours, days and months prepended by a 0, for example 05. |
| |
435.1 | 11 | |
| |
537.1 | 12 | [[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] |
| |
492.1 | 13 | |
| |
538.1 | 14 | //__Design changes__// |
| 15 | If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture. | ||
| 16 | |||
| |
539.1 | 17 | [[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] |
| 18 | |||
| |
464.1 | 19 | == **Bug Fixes** == |
| |
535.1 | 20 | //__Trigger activation__// |
| |
546.1 | 21 | Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. |
| |
520.1 | 22 | |
| |
538.1 | 23 | //__Multiple users deploying__// |
| |
535.1 | 24 | Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. |
| |
361.1 | 25 | |
| |
537.1 | 26 | [[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] |
| |
522.1 | 27 | |
| |
540.1 | 28 | //__Invalid memory configurations__// |
| 29 | We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. | ||
| |
538.1 | 30 | |
| |
543.1 | 31 | //__Property value synchronization__// |
| |
541.1 | 32 | Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. |
| 33 | |||
| 34 | //__JMS number__// | ||
| 35 | The number on the JMS container correctly displays the amount of queues present in Design. | ||
| 36 | |||
| 37 | [[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] | ||
| 38 | |||
| |
1.1 | 39 | == **Fancy Forum Answers** == |
| 40 | |||
| |
30.1 | 41 | As always, this is a gentle reminder 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: |
| |
1.1 | 42 | |
| |
542.1 | 43 | * [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] |
| 44 | * [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] | ||
| |
1.1 | 45 | |
| |
348.1 | 46 | == **Key Takeaways** == |
| |
1.1 | 47 | |
| |
149.1 | 48 | Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: |
| |
1.1 | 49 | |
| |
30.1 | 50 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 51 | * If you have feedback or ideas for us, talk to the Platypus |
| |
151.1 | 52 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. |
| |
1.1 | 53 | * Clear your browser cache (Ctrl + Shift + Del) |
| |
545.1 | 54 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] |
| |
1.1 | 55 | * Start thinking about how the license tracker can aid your development |
| 56 | * Start thinking about major, minor, and patch | ||
| 57 | * Keep making great integrations | ||
| 58 | |||
| 59 | Let's stay in touch and till next time! | ||
| 60 | |||
| 61 | {{info}} | ||
| |
30.1 | 62 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 63 | |
| |
254.1 | 64 | {{/info}} |
| 65 | ))) | ||
| 66 | |||
| 67 | ((( | ||
| 68 | {{toc/}} | ||
| 69 | ))) | ||
| |
1.1 | 70 | {{/container}} |
| |
254.1 | 71 | {{/container}} |