Wiki source code of 187 - Integration Sponsor
Version 41.1 by Erik Bakker on 2022/11/07 16:35
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 | |||
| |
36.1 | 5 | **Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version. |
| |
1.1 | 6 | |
| |
36.1 | 7 | == **Store - Next phase** == |
| |
1.1 | 8 | |
| |
39.1 | 9 | This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier. |
| |
18.1 | 10 | |
| |
39.1 | 11 | [[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] |
| 12 | |||
| 13 | {{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}} | ||
| 14 | |||
| |
40.1 | 15 | == **New eMagiz Mendix Connector** == |
| |
39.1 | 16 | |
| |
40.1 | 17 | With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal. |
| |
39.1 | 18 | |
| |
40.1 | 19 | {{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} |
| |
39.1 | 20 | |
| |
37.1 | 21 | == **Flow version restore** ~* == |
| |
18.1 | 22 | |
| |
36.1 | 23 | On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect. |
| |
18.1 | 24 | |
| |
39.1 | 25 | [[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] |
| 26 | |||
| |
36.1 | 27 | {{warning}}Note, that the following restrictions apply when restoring to a previous version: |
| 28 | * Changes made on definition and transformation level are **not** restored | ||
| |
39.1 | 29 | * You will **not** be able to restore to any flow version that was created before October 17th, 2022 |
| 30 | * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back | ||
| 31 | * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} | ||
| |
36.1 | 32 | |
| |
30.1 | 33 | == **Feedback items ** == |
| |
18.1 | 34 | |
| |
30.1 | 35 | We have also solved other feedback items besides the flow designer's critical updates. |
| |
18.1 | 36 | |
| |
30.1 | 37 | //__Redirect to the Manage Dashboard from your model home page__// |
| 38 | Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase. | ||
| |
18.1 | 39 | |
| |
30.1 | 40 | //__Readable entry of a SpEL expression in a flow component__// |
| 41 | As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions. | ||
| |
18.1 | 42 | |
| |
30.1 | 43 | [[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] |
| |
18.1 | 44 | |
| |
30.1 | 45 | //__Keep Create and the Create Phase release in sync__// |
| 46 | Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening. | ||
| |
18.1 | 47 | |
| |
30.1 | 48 | //__Mask password values in the unused properties overview__// |
| 49 | All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview. | ||
| |
18.1 | 50 | |
| |
30.1 | 51 | //__Press Enter to Search for properties__// |
| 52 | With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview. | ||
| |
18.1 | 53 | |
| |
30.1 | 54 | //__Styling update on tag selection on integration level__// |
| 55 | With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly. | ||
| |
18.1 | 56 | |
| |
30.1 | 57 | //__Enter to close automated flow testing pop-up__// |
| 58 | Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button. | ||
| |
18.1 | 59 | |
| |
30.1 | 60 | //__Improved naming of downloaded Event Streaming keystore__// |
| 61 | When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client. | ||
| |
18.1 | 62 | |
| |
30.1 | 63 | //__Pop out on the Traces tab within Flow Testing__// |
| 64 | In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow. | ||
| |
18.1 | 65 | |
| |
30.1 | 66 | //__Sorting User Management__// |
| 67 | As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview. | ||
| |
18.1 | 68 | |
| |
30.1 | 69 | //__Improved warning on passthrough API operation__// |
| 70 | Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create. | ||
| |
18.1 | 71 | |
| |
30.1 | 72 | //__Improved update functionality of Swagger file when changing data model__// |
| 73 | Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly. | ||
| |
18.1 | 74 | |
| |
30.1 | 75 | {{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}} |
| |
18.1 | 76 | |
| |
30.1 | 77 | //__"Disapprove and go to environment"__// |
| 78 | Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. | ||
| |
18.1 | 79 | |
| |
30.1 | 80 | //__Improve readability of API Gateway operations in Create and Deploy__// |
| 81 | When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation. | ||
| |
18.1 | 82 | |
| |
30.1 | 83 | //__Add Topic Storage information to License Tracker__// |
| 84 | On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz. | ||
| |
18.1 | 85 | |
| |
33.1 | 86 | [[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] |
| 87 | |||
| |
30.1 | 88 | //__Add Compatibility check when importing store items__// |
| 89 | We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening. | ||
| 90 | |||
| 91 | //__Show dependencies between support objects__// | ||
| 92 | As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects. | ||
| 93 | |||
| 94 | //__Improve rendering of validation definition when using multiple namespaces__// | ||
| 95 | With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end. | ||
| 96 | |||
| |
31.1 | 97 | //__Improved help texts on next-generation runtime functionality across the portal__// |
| 98 | With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime. | ||
| 99 | |||
| |
18.1 | 100 | == **Bug Fixes** == |
| 101 | |||
| |
30.1 | 102 | //__Provide correct feedback when a flow is transferred to Deploy for the first time__// |
| 103 | With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further. | ||
| |
18.1 | 104 | |
| |
30.1 | 105 | //__Show information in the Exception of error messages overview__// |
| 106 | With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show. | ||
| |
18.1 | 107 | |
| |
30.1 | 108 | //__Improve styling of cron trigger configuration pop-up__// |
| 109 | The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again. | ||
| |
18.1 | 110 | |
| |
30.1 | 111 | //__Prevent flow editing locks in specific situations__// |
| 112 | There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release. | ||
| |
18.1 | 113 | |
| |
30.1 | 114 | //__Generate property value empties the runtime selection__// |
| 115 | With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password). | ||
| |
18.1 | 116 | |
| |
30.1 | 117 | //__Make sure nothing of a system message is editable from your exit__// |
| 118 | Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices. | ||
| |
18.1 | 119 | |
| |
30.1 | 120 | //__Prevent users without view rights from seeing a weird screen in those phases__// |
| 121 | With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently. | ||
| |
18.1 | 122 | |
| |
35.1 | 123 | //__Name of starting point of the flow test is incorrect__// |
| |
30.1 | 124 | With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct. |
| |
18.1 | 125 | |
| |
30.1 | 126 | //__Audit Trail on User Management could break__// |
| 127 | When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue. | ||
| 128 | |||
| 129 | //__Progress bar in the license tracker is shown twice__// | ||
| 130 | With this release, we have fixed a bug that showed the progress bar twice in the license tracker. | ||
| 131 | |||
| 132 | //__Compare flows with support objects in the new flow designer__// | ||
| 133 | We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer. | ||
| 134 | |||
| |
1.1 | 135 | == **Fancy Forum Answers** == |
| 136 | |||
| |
30.1 | 137 | 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 | 138 | |
| |
32.1 | 139 | * [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]] |
| 140 | * [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]] | ||
| |
1.1 | 141 | |
| 142 | == **Key takeaways** == | ||
| 143 | |||
| |
30.1 | 144 | Thanks to all that 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 | 145 | |
| |
30.1 | 146 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 147 | * If you have feedback or ideas for us, talk to the Platypus |
| 148 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 149 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 150 | * Check out the release notes [here] | ||
| 151 | * Start thinking about how the license tracker can aid your development | ||
| 152 | * Start thinking about major, minor, and patch | ||
| 153 | * Upgrade to the latest build number | ||
| 154 | * Keep making great integrations | ||
| 155 | |||
| 156 | Let's stay in touch and till next time! | ||
| 157 | |||
| 158 | {{info}} | ||
| |
30.1 | 159 | ~* 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 | 160 | |
| 161 | ~*~* Indicates a GEN3-only feature. | ||
| 162 | {{/info}})))((({{toc/}}))){{/container}} | ||
| 163 | {{/container}} |