|
| 1 | +--- |
| 2 | +id: v13.5.0 |
| 3 | +title: Version 13.5.0 Release Notes |
| 4 | +sidebar_label: v13.5.0 |
| 5 | +image: "img/release-note-link-preview.png" |
| 6 | +--- |
| 7 | + |
| 8 | +_December 5th, 2024_ |
| 9 | + |
| 10 | +:::info |
| 11 | +Mia-Platform Console v13.5.0 is **now in Preview** and will be generally available on December 19th. |
| 12 | + |
| 13 | +Console SaaS users can try out v13.5.0 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 | +## Data Lineage |
| 19 | + |
| 20 | +Mia-Platform Data Catalog introduces the [Data Lineage](/data_catalog/frontend/data_lineage.mdx), a powerful tool for understanding, visualizing, and describing the flow and transformations of data within an organization. |
| 21 | + |
| 22 | +This feature allows users to explore data relationships at two levels: **Table Lineage** and **System of Record (SoR) Lineage**, offering both detailed insights and a high-level overview. |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +At the [Table-Level Lineage](/data_catalog/frontend/data_lineage.mdx#table-level-lineage), users can dive into the interconnections between individual tables, visualizing data flows and the transformations applied along the way. Users can also enrich the lineage with virtual assets and jobs, useful to complete relationships that have not yet been automatically retrieved, ensuring that context and purpose of data flows are thoroughly captured and properly described. |
| 27 | +The [SoR-Level Lineage](/data_catalog/frontend/data_lineage.mdx#system-of-record-level-lineage) shows an aggregated view of data flows across Systems of Records, simplifying the identification of dependencies and bottlenecks at a broader scale, and clarifying how various systems interact within the organization. |
| 28 | + |
| 29 | +If you are using [Fast Data Control Plane](/fast_data/runtime_management/overview.mdx), the aggregation processes configured in your Fast Data Projects can be automatically captured in the Data Lineage, making Fast Data jobs visible on the Lineage canvas. To know more about how to acquire information from the Fast Data pipelines, visit the [related documentation](/data_catalog/data_catalog_job_runner.mdx#fast-data-jobs-sync). |
| 30 | + |
| 31 | +## Connections Management in Data Catalog Application |
| 32 | + |
| 33 | +The [Connections Management](/data_catalog/frontend/data_catalog_connections.mdx) feature in Mia-Platform Data Catalog enables users to retrieve and leverage metadata from [various supported providers](/data_catalog/frontend/data_catalog_connections.mdx#connection-providers), supporting critical operations such as [Asset Discovery](/data_catalog/frontend/data_catalog_assets.mdx) and [Lineage Analysis](/data_catalog/frontend/data_lineage.mdx). |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +Through the Connections Panel, users can manage the lifecycle of connections, from creation to deletion, and having access to a detailed overview of all configured connections. |
| 38 | +Once a connection is established, assets can be imported directly into the Data Catalog using the Data Catalog Sync feature. To know more about the processes to update the state of the Data Catalog solution, visit the [following documentation](/data_catalog/data_catalog_job_runner.mdx#available-jobs). |
| 39 | + |
| 40 | +## Centralized management of the Container Registries |
| 41 | + |
| 42 | +Gain more control over your container registries in your Projects! You can now easily manage and monitor them directly within your Project settings, where you can view, create, and delete them according to your purposes. |
| 43 | +This update enables centralized monitoring and control of your registries, and allows you to specify the desired registry at the service level in the Design area. |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +For more details, please refer to [the documentation](/console/project-configuration/project-settings.md#container-registries) |
| 48 | + |
| 49 | +## Enhanced Item Management: Edit Items in Mia-Platform Software Catalog |
| 50 | + |
| 51 | +In this release, we’ve introduced the ability to edit items in the Software Catalog, providing more flexibility in resource management. Non-versioned items can now be fully edited, allowing users to modify all aspects of the item. For versioned items, only the metadata can be edited, while any changes to the resources will still require creating a new version. |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | +For more details, please refer to [the documentation](/software-catalog/manage-items/software-catalog-ui/update/overview.md) |
| 56 | + |
| 57 | +## Introducing Snapshot Comparison through the history modal |
| 58 | + |
| 59 | +Easily track changes to your configurations! Now you can compare any two snapshots side-by-side with our new visual comparison tool. Just head to the history modal and select the snapshots you want to analyze. |
| 60 | + |
| 61 | +For more details, please refer to [the documentation](/development_suite/set-up-infrastructure/revisions-and-versions.md) |
| 62 | + |
| 63 | +## Console |
| 64 | + |
| 65 | +### Improvements |
| 66 | + |
| 67 | +#### Allowing Secret key interpolation during the creation of an env variable from secret |
| 68 | + |
| 69 | +It is now possible to use public variables to interpolate the "Secret key" field when creating new environment variables "From Secret" on a microservice. This enhancement provides greater flexibility and automation when working with secrets, especially for complex deployments where secret keys might vary across environments. |
| 70 | + |
| 71 | +#### Infrastructure Resource |
| 72 | + |
| 73 | +The 'resourceId' of marketplace resources can now be modified after detachment, providing increased flexibility for resource organization at Runtime level. |
| 74 | + |
| 75 | +### Bug Fix |
| 76 | + |
| 77 | +This version addressed the following bugs: |
| 78 | + |
| 79 | +* fixed an issue where service/resource management badges were unavailable after a marketplace plugin/custom resource connection failed ; |
| 80 | +* fixed an issue where release notes for the current version of an instantiated resource were not displayed initially in the change version modal. |
| 81 | + |
| 82 | +## Fast Data |
| 83 | + |
| 84 | +### Fast Data Runtime Management |
| 85 | + |
| 86 | +The Fast Data Control Plane application has been updated to support the integration with Mia-Platform Data Catalog application for the [Data Lineage](#data-lineage) feature. |
| 87 | +For more information, visit the [compatibility matrix documentation page](/fast_data/runtime_management/compatibility_matrix.md#service-latest-versions) with reported the latest service versions. |
| 88 | + |
| 89 | +## Microfrontend Composer |
| 90 | + |
| 91 | +### Back-Kit Library |
| 92 | + |
| 93 | +The new version `v1.5.11` of the back-kit library is available! |
| 94 | + |
| 95 | +Refer to back-kit [changelog](/microfrontend-composer/back-kit/changelog.md) for finer-grained details of new versions. |
| 96 | + |
| 97 | +#### Bug Fix |
| 98 | + |
| 99 | +* Fixed bk-table height when inside bk-layout-swap |
| 100 | + |
| 101 | +## Marketplace |
| 102 | + |
| 103 | +### Marketplace Updates |
| 104 | + |
| 105 | +#### Care Kit |
| 106 | + |
| 107 | +A new version `2.9.2` of Care Kit is out! |
| 108 | + |
| 109 | +The new version bring some fixes to the following components: |
| 110 | + |
| 111 | +- `ck-patient-dashboard`: Italian localization is now available |
| 112 | +- `ck-threshold-modal`: fixed a concurrency bug causing the component to show outdated thresholds |
| 113 | + |
| 114 | +#### Chat Service Backend |
| 115 | + |
| 116 | +A new version `1.0.2` of Chat Service Backend is available! |
| 117 | + |
| 118 | +This version upgrades Node.js to v20 and fixes some documentation links. |
| 119 | + |
| 120 | +#### Notification Manager |
| 121 | + |
| 122 | +A new version `2.4.2` of Notification Manager is available! |
| 123 | + |
| 124 | +This version fixes a bug causing reminders not aborted correctly when an appointment was updated or deleted. |
| 125 | + |
| 126 | +#### Swagger Aggregator |
| 127 | + |
| 128 | +##### Bug Fix |
| 129 | + |
| 130 | +From Swagger Aggregator version `3.8.2`, the `oauthFlows.password.tokenUrl` format has changed from `uri` to `uri-reference` in the OpenApi 3.1 schema |
| 131 | + |
| 132 | +#### Teleconsultation Service Frontend |
| 133 | + |
| 134 | +A new version `2.0.2` of the Teleconsultation Service Frontend is available! |
| 135 | + |
| 136 | +This version fixes a bug causing the UI language not matching sometimes the browser language. |
| 137 | + |
| 138 | +#### User Manager Service |
| 139 | + |
| 140 | +A new version `1.5.2` of the User Manager Service is available! |
| 141 | + |
| 142 | +This version upgrades Node.js to v20 and several dependencies, including `custom-plugin-lib` to v6. |
| 143 | + |
| 144 | +## How to update your Console |
| 145 | + |
| 146 | +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.9.0-beta.0`. |
| 147 | + |
0 commit comments