|
| 1 | +--- |
| 2 | +id: v13.0.3 |
| 3 | +title: Version 13.0.3 Release Notes |
| 4 | +sidebar_label: v13.0.3 |
| 5 | +image: "img/release-note-link-preview.png" |
| 6 | +--- |
| 7 | + |
| 8 | +_June 21st, 2024_ |
| 9 | + |
| 10 | +:::info |
| 11 | +Mia-Platform Console v13.0.3 is **now in Preview** and will be generally available on July 04th. |
| 12 | + |
| 13 | +Console SaaS users can try out v13.0.3 latest improvements in Preview! Open a Service Request to ask for the creation of a sandbox Company in case you do not have access to any Company. |
| 14 | + |
| 15 | +For self-hosted installations, please read the [following guidelines](#how-to-update-your-console). |
| 16 | +::: |
| 17 | + |
| 18 | +## Console |
| 19 | + |
| 20 | +### Compare changes at Deploy on Projects with the enhanced workflow |
| 21 | + |
| 22 | +In all the Projects using the enhanced workflow, it is now possible to compare all changes made in the configuration to be deployed with respect to the previous deployed configuration. Users will then be able to view all configuration files and their respective changes and easily search among them. |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +### Restore previous configuration saves on Projects with the enhanced workflow |
| 27 | + |
| 28 | +On Projects with enhanced workflow you can now restore a previous configuration save from the revision history modal. |
| 29 | +All you have to do is to open the revision action popover, click on the `History` button and select the menu item "Restore these changes" on the configuration save you want to restore. |
| 30 | + |
| 31 | + |
| 32 | + |
| 33 | +### Vote the answers provided by Mia-Assistant |
| 34 | + |
| 35 | +From now on, you can send positive or negative feedback to the answers generated by Mia-Assistant by simply clicking the thumbs up or down at the end of each answer. |
| 36 | +This feedback will then be gathered and analyzed to improve the overall performance of the chatbot. |
| 37 | + |
| 38 | +### Configure Metrics gathering for all the containers of a Microservice |
| 39 | + |
| 40 | +Once you have configured the Runtime Monitoring system for your Project, you can now define the scraping rules for each of your Microservice containers. You can perform such action in the `Monitoring` tab of each Microservice's details page. |
| 41 | +For more information, visit the related [documentation page](/development_suite/api-console/api-design/microservice-monitoring.md). |
| 42 | + |
| 43 | +### Bug Fix |
| 44 | + |
| 45 | +This version addressed the following bugs: |
| 46 | + |
| 47 | +* fixed a bug that prevented the correct view of an iFrame extension when switching among two different iFrame extensions; |
| 48 | +* fixed a bug that caused a malfunction in the display of the Deploy area when rapidly switching among two different Projects. |
| 49 | + |
| 50 | +## Microfrontend Composer |
| 51 | + |
| 52 | +### Back-Kit Library |
| 53 | + |
| 54 | +The new version `v1.5.4` of the back-kit library is available! |
| 55 | + |
| 56 | +Refer to back-kit [changelog](/microfrontend-composer/back-kit/changelog.md) for finer-grained details of new versions. |
| 57 | + |
| 58 | +#### Improvements |
| 59 | + |
| 60 | +##### Exposed `customEvents` property of form modal and form drawer components |
| 61 | + |
| 62 | +It is now possible to add a new prop to the components `bk-dynamic-form-modal` and `bk-dynamic-form-drawer` called `customEvents` which takes the name of the event that the component will listen to and the mode which can be 'insert' or 'selected'. |
| 63 | + |
| 64 | +## Marketplace |
| 65 | + |
| 66 | +### Marketplace Updates |
| 67 | + |
| 68 | +#### API Portal |
| 69 | + |
| 70 | +We are excited to announce the release of API Portal version `2.0.0`! |
| 71 | + |
| 72 | + |
| 73 | +This new version features an upgraded interface based on Swagger UI, providing enhanced support for all functionalities of the OpenAPI 3.1 specification. Please note that there are a few breaking changes in this release. We strongly recommend reviewing the [updated documentation](/runtime_suite/api-portal/20_configuration.md#how-to-migrate-to-v2) to understand these changes. |
| 74 | + |
| 75 | +:::caution |
| 76 | +Anyone wishing to use API Portal version `2.0.0` to visualize CRUD Service documentation should update the latter to the latest patch of major 6 (`6.10.2` at the time of writing) or to the latest patch of major 7 (`7.0.3` at the time of writing), given the new, improved way of handling OpenAPI specification errors in the API Portal. |
| 77 | +::: |
| 78 | + |
| 79 | +#### CRUD Service |
| 80 | + |
| 81 | +The new version `7.0.3` of the CRUD Service is available! |
| 82 | + |
| 83 | +##### Bug Fix |
| 84 | + |
| 85 | +* Fixed projection example in json schema generator |
| 86 | +* `serializerCompiler` has been added to use explicitly fastifiy-fast-json, along with `AdditionalCaster` |
| 87 | +* `$eq` operator can now be used also for array fields |
| 88 | +* `/-/schemas` accept header defaults to `application/json` |
| 89 | +* `/schemas` and `/-/schemas` endpoints now return also `required` property |
| 90 | + |
| 91 | +## How to update your Console |
| 92 | + |
| 93 | +For self-hosted installations, please head to the [self hosted upgrade guide](/infrastructure/self-hosted/installation-chart/100_how-to-upgrade.md) or contact your Mia-Platform referent and upgrade to _Console Helm Chart_ `v13.4.0-beta.0`. |
0 commit comments