23.10 LTS

Table of Contents

Part Screening, Business Case & Qualification

Part Configuration with updated AM Databases

Following our vision to support our users in managing their part qualification process within 3YOURMIND, we are bringing new Part Configuration functionality to the part detail page.

Open

AM Part configuration in the new Production tab

In a dedicated Production tab only accessible by Expert Users we are offering a new part configuration form, to create and store the AM part configuration resulting from assessment and prototyping.

For further information on using the functionality see https://3yourmind.atlassian.net/wiki/spaces/PD/pages/1905819663

Open

Create your new AM part configuration during Part Qualification

The Production tab on part detail is tied to the status type ‘Qualification’. This requires Users to assign the type Qualification to some status. Updating any part to a status of type Qualification results in the Production tab becoming accessible for Expert Users, see further details about configuring statuses and workflows here https://3yourmind.atlassian.net/wiki/spaces/PD/pages/1823440969.

Updated AM Database

With this version we are releasing our reworked, extended and standardized AM Databases. We updated our default database offerings and standardized the relations. With the update to our database we introduced:

• 450 new Material categories following the famous material categorization system of Michael F. Ashby

• 6 standardized AM Technologies

  • including links between Technologies and the Material Categories they can process

• A clean, unified list of 1200 AM Materials

  • including Manufacturer information

• 32 default and un-editable Post Processing types

  • including links between Post Processings and the Material Categories they can process

  • categorization of Post Processings into 4 groups

For further information on the structure and relation of the different database tables and how to add custom database entries can be found here: https://3yourmind.atlassian.net/wiki/spaces/PD/pages/1905852417.

Introduction of workflow status types

We introduced workflow status types in order to control available functionalities based on a part's current status. Four default status types were introduced and can be optionally assigned to a workflows statuses:

• Initial, Assessment, Qualification, Production

Improved user guidance for missing cost and savings assessment

We improved the user guidance in cases where the economic assessment is not yet available, due to missing or failing technology checks. Simply check the Technology tab for further information.

Digital Inventory Management

Enhanced IP protection: Restriction on 3D file downloads from Catalog parts

In our ongoing commitment to protect intellectual property and align with security best practices, we are enhancing the management of 3D file downloads from Catalog parts for User Panel users. With this release:

• Downloads of 3D files from Catalog parts are restricted by default.

• 3D file access remains available for Service users for convenient order processing.

This enhancement is especially tailored for organizations looking for a more controlled internal environment, offering them an added layer of IP protection.

See also .

Deleting User Groups in the Organization Panel

User Groups can now be deleted by Organisation admins directly in the Org Panel. Before, this functionality was only available in the Admin panel.

See also .

Other Improvements

Updated Styling for Enhanced 3D Viewer Clarity

We've enhanced the 3D viewer with a neutral grey background for improved visibility, standardizing this across all platforms and removing color customization options in the admin panel to avoid interference with strongly accentuated custom themes.

Analytics

Part Lifecycle Management Dashboard Updates

• Added part author filtering option to all default Part Lifecycle Management dashboards.

Bug fixes

Part Screening & Business Case

• Resolved an issue that caused choice options to ignore their sort priority setting.

• Resolved an issue causing part volume to not update after uploading a 3D file.

• Fixed an issue causing markdown tables to not render correctly in the frontend.

• Fixed a bug causing two vertical scrollbars to show on the part list.

• Fixed a bug causing non-Expert users to have access to AMPI Settings.

• Fixed a bug preventing PDF previews to be displayed on part detail.

• Added support for latest CAD software file formats.

Digital Inventory Management

• Resolved an issue where the file naming convention set in the admin panel was not being applied when downloading a Catalog part's 3D file from the Service Panel.

• Resolved an issue in the Profile > Addresses section where attempting to set an address as default would inadvertently unset the current default without assigning a new one.

Administration Actions & Information

Changes to hardware prerequisites

Our database requirements have changed:

See also

evaljs → evalrs

Under the hood, we replaced a kotlin-based microservice with an equivalent rust-based microservice, which is faster and requires less resources. Instead of an evaljs pod, there is now an evalrs pod running. Here is the default serviceConfig for evalrs, use to extend or customize your deployment configuration

3d backend logic is merged into button3d

With our merged our 3d-backend service into button3d . Please remove your serviceConfig for

Analytics: Update your custom order queries to consider the new rejected status

• For Enterprise customers with full Analytics access

With this release, we changed how canceled orders are treated. Instead of an order Status == Cancelled, an order now has a simple flag Is Rejected on the Order Order table.

In case you are using the models we provide in the Default Collection, e.g. Model - ERP - Orders with Order Status, then you do not have to do anything. We have updated the models to already consider this change.

However, if you created your own custom queries around orders, you may have to update them. If in any of those custom queries you filter out canceled orders manually, you should update the queries as follows.

Instead of filtering by the Cancelled order status, you should filter by the Is Rejected flag.

As an example, see the content of the Model - ERP - Orders with Order Status

Production sheets

In 23.6.0, the type field for production sheets has been introduced. This field is automatically populated via a data migration, nevertheless, some inconsistencies may occur.

It’s recommended, to go over existing production sheets in the platform and confirm that the correct type is assigned.

New Column “Rejected” in Order and Quote CSV Export Format

Order and Quote CSV export files now contain an additional column “Rejected” that can have the values TRUE or FALSE. In case you are automatically processing order and/or quote CSV files in another system you should check that the updated format is processed correctly.

The capability to reject Requests, Quotes, and Orders was first introduced with version 23.5.

See also

New ST Rejection Webhook for Rejected Requests, Quotes, Orders

We have published a new webhook that fires whenever any sales transaction - order, quote or request - is rejected. The ability to reject requests and quotes was introduced in 23.5. Rejecting an order used to be called “canceling an order”.

Customers who use the Order Status Change Webhook to be informed about rejected (canceled) orders need to start using the new ST Rejection Webhook.

See also

• https://demo.3yourmind.com/apidocs/#tag/Webhooks/operation/postToStRejectionWebhook

Helm Chart Changes

• Added support for custom database name for metabase.

• Removed annotations related to the cluster-autoscaler.

• Updated postgresql image.

• Increased the failureThreshold for metabase livenessProbe from 3 to 10.

• Adjust default values for rate-limits & throttling.

• Added support for evalrs.

• Increased the terminationGracePeriodSeconds for celery to 14400. This means that celery pods need longer to terminate if tasks are still being executed.

• The default resource limit of the celery pod had been increased from 512Mi to 1Gi (memory).

• Added support for custom S3 location path.

• Added possibility to turn off automatic database creation with dbConfig.createDatabase.

• Dropped support for vault.

• Added support for “Celery Flower” it can be enabled by setting celeryFlower.enabled to true.

• Dropped support for googleTagManagerId.

• Added support for authenticating to e-mail servers using certificates.

For customers running 3YD’s (Kurl.sh)

With release 23.10 we are updating our Kurl installer with a newer version of Kubernetes and updating most of the clusters’s components. Use this article to do the upgrade process.

Kubernetes - updated to 1.27.4

Contour - updated to 1.25.2

Weave - deprecated and replaced by Flannel

Docker - deprecated and replaced by Containerd

(For LTS customers) Earlier Release Notes

This section provides a summary of product additions since the last LTS release (23.4).

Expand the following sections to see details.