Wiki source code of 278 - Look Look
Last modified by Erik Bakker on 2026/10/09 13:17
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** This release includes many smaller improvements across the platform’s various phases. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target=“blank”]]** are released. We also have two pre-announcements regarding the next release, scheduled for **October 22nd, 2026**. | ||
| 7 | |||
| 8 | == New Environment Template == | ||
| 9 | |||
| 10 | As of this release, we have prepared to update our databases under the authorization server. This is released as part of a new [[environment template>>doc:Main.Release Information.Cloud Templates.WebHome||target=“blank”]]. | ||
| 11 | |||
| 12 | {{info}}The following applies to this functionality: | ||
| 13 | |||
| 14 | * This is only released for models running in our **current-generation architecture**. This includes the following: | ||
| 15 | ** Prepared for updating our databases underneath the authorization server | ||
| 16 | * The functionality will be made available as part of a new cloud template and can be updated via the default [[upgrade>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained||target=“blank”]] functionality. | ||
| 17 | * You need to update to this version of our cloud template before **November, 18th 2026**.{{/info}} | ||
| 18 | |||
| 19 | == Pre-Announcements == | ||
| 20 | |||
| 21 | === eMagiz IP Address whitelisting === | ||
| 22 | |||
| 23 | {{info}} | ||
| 24 | As communicated earlier this year on **April 24th, 2026** via [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]], we will start using new IP addresses for our internal infrastructure. Consequently, this meant and still means that you need to ensure that any server under your control that connects to our infrastructure can communicate with the IP addresses communicated in that message (and shown below): | ||
| 25 | |||
| 26 | * 3.66.44.69 | ||
| 27 | * 52.57.64.170 | ||
| 28 | * 63.182.102.95 | ||
| 29 | {{/info}} | ||
| 30 | |||
| 31 | === CAPE eMail Migration === | ||
| 32 | |||
| 33 | {{info}}To help our partner CAPE align the email addresses used for notifications and logins with the new email addresses they have been using for a while, we will migrate our CAPE user information to reflect this change. As a result, on **October 22nd, 2026**, all users who log in with an old email address will need to use their new email address.{{/info}} | ||
| 34 | |||
| 35 | == Minor Changes == | ||
| 36 | |||
| 37 | //Create - Platform// | ||
| 38 | Some UI elements have been replaced with newer versions, which should improve User experience. | ||
| 39 | |||
| 40 | //Manage - Queue Browser// | ||
| 41 | Added basic sort options for queues. | ||
| 42 | |||
| 43 | [[image:Main.Images.Release Blog.WebHome@release-278-queue-browser-sorting.png]] | ||
| 44 | |||
| 45 | == Bug Fixes == | ||
| 46 | |||
| 47 | //Create - Flow Designer// | ||
| 48 | The following bugs have been fixed in Flow Designer. | ||
| 49 | |||
| 50 | * Added the missing help text when viewing the Error Handler Type of a Rest object. | ||
| 51 | * Fixed a bug that prevented the widget from comparing flow versions; comparisons now work again. | ||
| 52 | * Improved the internal mechanism through which we ensure data validity when a user creates a new version in the flow designer. Added a fallback option for support to assist in case a user gets stuck in this process. | ||
| 53 | |||
| 54 | //Deploy - Certificate Management// | ||
| 55 | We fixed an issue where you might have received expiration notifications for certificates that are no longer in use, causing confusion and unnecessary support efforts. | ||
| 56 | |||
| 57 | == Fancy Forum Answers == | ||
| 58 | |||
| 59 | As always, this is a gentle reminder to ask questions via the Q&A forum in the eMagiz iPaaS portal. This way, we can all benefit from the community’s knowledge. For some inspiration, take a look at these forum answers: | ||
| 60 | |||
| 61 | * [[SMB Outbound Gateway Move Operation Fails with “The system cannot find the file specified”>>https://my.emagiz.com/p/question/172825635704477334||target=“blank”]] | ||
| 62 | |||
| 63 | == Key Takeaways == | ||
| 64 | |||
| 65 | Thanks to everyone who helped build the product and tested it and provided feedback to improve it. To end this post, here are some key takeaways for you: | ||
| 66 | |||
| 67 | * If you have questions surrounding our roadmap, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 68 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 69 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 70 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 71 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.278 - Look Look.WebHome||target=“blank”]] | ||
| 72 | * Don’t forget to update your environment template before the deadline | ||
| 73 | * Keep making great integrations | ||
| 74 | |||
| 75 | Let’s stay in touch and till next time! | ||
| 76 | |||
| 77 | {{info}} | ||
| 78 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 79 | |||
| 80 | {{/info}} | ||
| 81 | ))) | ||
| 82 | |||
| 83 | ((( | ||
| 84 | {{toc/}} | ||
| 85 | ))) | ||
| 86 | {{/container}} | ||
| 87 | {{/container}} |