Wiki source code of 175 - Building Time
Last modified by Carlijn Kokkeler on 2024/04/18 13:27
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 3 | |||
| 4 | **Hi there, eMagiz developers!** e have fixed several minor feedback items in the last couple of weeks. On top of that, we have finished our work on the latest build number. This build number includes some most desired fixes for our community. Some fixes surrounding flow testing and JSON-related transformations are notable among the feedback items. So let us dive into all that we have to offer this time around! | ||
| 5 | |||
| 6 | == **Build number 61** == | ||
| 7 | |||
| 8 | This release also introduces build number .61 to our platform. With this release, some specific problems have been resolved. First, it contains a fix for high throughput in multi-threaded cases when dealing with calls to the AWS API. On top of that, it includes a fix that allows you to dynamically determine how many seconds in advance you want to refresh your access_token when calling an external endpoint secured through the OAuth2.0 protocol. This enables you to prevent errors when the external system has precise requirements on calling the token endpoint. Furthermore, it provides two other minor fixes. Please check out the release notes in the portal for all details to determine the impact on your solution. | ||
| 9 | |||
| 10 | == **Bug fixes ** == | ||
| 11 | See below for all bug fixes that are solved with this release | ||
| 12 | |||
| 13 | //__Running a flow test on a flow with the 'old' debugger__// | ||
| 14 | Previously, when you tried to run a flow test in which a reference to an H2 database was available (i.e., the ‘old’ debugger construction), your flow test would run into an exception. We have made sure that these flows can now also be tested as part of the flow testing functionality with this release. | ||
| 15 | |||
| 16 | //__Running a flow test should be possible when referencing a resource__// | ||
| 17 | Previously, it was impossible to execute a proper flow test on a flow where you defined your reference to a resource (i.e., when referencing a groovy script). We have made sure that you can test these flows as part of the flow testing functionality with this release. | ||
| 18 | |||
| 19 | |||
| 20 | == **Feedback items ** == | ||
| 21 | |||
| 22 | Apart from the key updates around functionality, we have also solved other feedback items. | ||
| 23 | |||
| 24 | //__Validate JSON String Array__// | ||
| 25 | With this release, we have made it possible to define on your system message in Create whether a particular part of the message needs to be validated as a String array. Note the help text when implementing this within eMagiz. | ||
| 26 | |||
| 27 | [[image:Main.Images.Release Blog.WebHome@175-release-blog-1.jpg]] | ||
| 28 | |||
| 29 | //__List output JSON__// | ||
| 30 | Previously, when you drew two lines to the same output list eMagiz would create two separate JSON arrays. With this release we have ensured that for each output list only one JSON array is created to prevent unexpected JSON output | ||
| 31 | |||
| 32 | //__Removal of unnecessary pages in Manage__// | ||
| 33 | With this release, we have removed several unnecessary pages in the Manage phase of eMagiz. The obsolete pages of Channel, Handler, and Cloud Statistics have been removed. | ||
| 34 | |||
| 35 | == **Fancy Forum Answers** == | ||
| 36 | |||
| 37 | 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: | ||
| 38 | |||
| 39 | * [[OverlappingFileLockException>>https://my.emagiz.com/p/question/172825635700362791||target="blank"]] | ||
| 40 | * [[Problem with synchronous exit connector without import mapping>>https://my.emagiz.com/p/question/172825635700360986||target="blank"]] | ||
| 41 | * [[XML Message with content: “É” changes in ” “>>https://my.emagiz.com/p/question/172825635700362885||target="blank"]] | ||
| 42 | * [[New Line in FTP File Placement>>https://my.emagiz.com/p/question/172825635700362886||target="blank"]] | ||
| 43 | |||
| 44 | == **Key takeaways** == | ||
| 45 | |||
| 46 | 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: | ||
| 47 | |||
| 48 | * If you have questions surrounding our Program Increment Planning, please get in touch with | ||
| 49 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 50 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 51 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 52 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.Building Time.WebHome||target="blank"]] | ||
| 53 | * Start thinking about how the license tracker can aid your development | ||
| 54 | * Start thinking about major, minor, and patch | ||
| 55 | * Upgrade to the latest build number | ||
| 56 | * Keep making great integrations | ||
| 57 | |||
| 58 | Let's stay in touch and till next time! | ||
| 59 | |||
| 60 | {{info}} | ||
| 61 | ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 62 | |||
| 63 | ~*~* Indicates a GEN3-only feature. | ||
| 64 | {{/info}})))((({{toc/}}))){{/container}}{{/container}} |