Release Notes - 08 November 2022 Updates
Explore the new features added in this update!
Updated on: 08 November 2022
Release Version: 0.9.0
| Feature | Description |
|---|---|
| Team member report now includes allocation period and membership status | The team member report that is downloaded from the Teams tab of Users, Roles, Teams includes allocation period as well as membership status. Status can be past, current, or future. |
| Confluence base page can be created from the Lazsa Platform | You can set the Confluence base path from the Others tab of Product details. You can use an existing Confluence page as the base page, or create a new Confluence base page from the Lazsa Platform. The specified base page acts as a root or a parent page, and all other Confluence pages created by the product are created under the specified base page. |
| Portfolio Owners dashboard added | The Portfolio Owners tab is now added to Dashboards, which provides a complete view of the portfolio and products within it, and the budget and revenue details. The details include portfolio spend, breakdown by product, CPI data, revenue by portfolio, and revenue by product. |
| Delink release name from a feature | While editing feature details, you can now remove the release name that is linked with the feature. Delinking the release name automatically removes the fix version of that release from the epics, stories, tasks, defects of the feature. |
| Versioning for templates for integration jobs | While creating a data integration job by using Databricks, the latest version of the wheel package template is available for creating the job. |
| Bitbucket dependency for transformation jobs is removed | If you disable Databricks Repository Integration while configuring a Databricks instance, it eliminates cloning of the repo in Databricks and therefore, it avoids failure of repository creation. |
| Glue metastore support for S3 | You can now store the metadata of data in Amazon S3 in AWS Glue. For this, you must configure an AWS Glue instance by adding a new datastore in Databases and Datawarehouses, and select a database to store the metadata. |
| Proxy server support for Lazsa Orchestrator Agent | Proxy server configuration is now supported for Lazsa Orchestrator Agent. The Orchestrator Agent connects to the Lazsa platform and the tools via the configured proxy server. |
| User onboarding to Confluence | You can assign user access to your Confluence spaces and pages from within the Lazsa Platform. All you need to do is create a Product role having the required Confluence space and page permissions and assign it to the intended teams or individual users. |
| Support to run existing Jenkins jobs | You can run your existing Jenkins jobs from the Deployment Workflow of the Lazsa platform. For this, in your Jenkins configuration in the Cloud Platform, Tools & Technologies section, add the Jenkins job details such as project name, project path, and job parameters. |
| New version of Lazsa Orchestrator Agent is available | The Lazsa Orchestrator Agent is updated to a new version. On the Lazsa Orchestrator Agents screen, click Update Available for instructions to upgrade the agent to the latest available version. See Lazsa Orchestrator Agent. |