Weekly feature improvement and bugfix summary

The following feature improvements have been implemented, and bugs fixed in the past week:

Inventory

• In the fact sheet creation form, admins can now make a subscription type mandatory, whereas previously, only subscription roles could be made mandatory. This ensures that a subscriber is assigned to the fact sheet at the time of fact sheet creation, even if specific subscription roles are not defined, promoting accountability and responsibility for maintaining data quality.

Reports

• We fixed an issue on roadmap reports so that drilling down into a selected fact sheet type does not result in an error when no clustering is applied to the report.

Diagrams

• It is now possible to assign a fact sheet type to a connector shape when creating fact sheet shape templates.

• Previously, when a fact sheet name was changed in the inventory, the fact sheet shape label in the diagram was automatically marked for update, even if you had intentionally modified the label in the diagram.

  Now, any changes made to the fact sheet shape label in the diagram will be preserved, even if the fact sheet name is updated in the inventory. This allows you to customize the fact sheet shape label to make it more meaningful in the diagram's context.

Reference Catalog

• The 'Log4Shell Remediation' information for application fact sheets has been removed from the reference catalog as the information related to the vulnerability reported in November 2021 is no longer relevant to architectures. The information is also no longer available in the user interface nor via the Catalog API.

Discoveries

• In workspaces with activated self-built software discovery, we added the additional date field 'Last Updated (SBOM)' to the 'Name and Description' section of microservice fact sheets. The new field indicates the last time the SBOM information was updated for a given microservice to help you better manage the timeliness of SBOM data.

  We've also implemented validation of the CycloneDX schema for SBOM files imported through the Self-Built Software Discovery API. If a file in the CycloneDX format does not comply with the schema, the API now rejects file processing and returns a descriptive error message.

Integrations

• We've enhanced the user interface of the webhook configuration page and added new features to the OAuth 2.0 authorization method in PUSH webhooks. The new 'Credentials Location' attribute lets you specify where to place credentials in your request, either in the authorization header or the request body. Additionally, you can define request body and query parameters to send to the token URL, which offers greater flexibility and control over your webhook configurations.