4.9.0 - 2021.07.02

 

[PLM] New property type Currency

We are introducing a new property type, Currency, for a more convenient way of handling currency amounts in the system. See also our documentation of the new property type under .

Prior to this new type, currencies were stored as Cents in Integer fields. For example, 12.34 EUR was stored as 1234 (cents). This had several inconveniences

  • CSV import and export of EUR amounts had to be converted to cents and vice versa

  • Blackbox and scores formulas that operate with Euro amounts had to manually convert Cent amounts into Euro amounts by dividing by 100

With this update Cent to EUR conversion is not necessary anymore for CSV import and export nor in scores.

The update automatically converts custom properties of type Integer that are used as currency fields, such as Current part price, to the new type Currency. All values on existing parts are automatically converted, too. E.g. 1234 (cents) will automatically be converted to 12.34 (Euro).

Manual formula update required

Score or Blackbox formulas using Integer (currency) properties, e.g. Current part price need to be adjusted manually.

Example

Before

const unitCost = currentPartPrice / 100

After

const unitCost = currentPartPrice

The formulas that are most likely affected are

  • bb_econ_currentPartPrice

  • bb_econ_pricePerKg

If you perform the version upgrade after updating your formulas, you have to trigger a recalculation of the scores manually. See

[PLM] Select multiple values in Choice filters

You can now select multiple values when filtering Choice properties. The result list will contain values of any of the selected values.

In the example below, results will be any of Status = Draft or Status = Submitted.

 

[ERP] Notify Service Configurators for bad pricing formula

If your service has invalid pricing formulas (that pass the validation, but produce errors with actual user data), you will now get a nice error message about it via email:

The pricing script for the material/postprocessing {material or postprocessing} has a problem:
It does not output a valid price when using the following variables: {variables}.
Please correct the error

 

[ERP/MES] Download 1 file version only

We added the option to only download one 3D file version when downloading files from the 3YOURMIND platform. In the admin panel, it is now possible to specify that all bulk downloads should only download the desired file version.

[MES] Automatic target date assignment

Starting with this version, target dates will be automatically assigned when an order is accepted. The target date calculation, depending on availability of information, is based on the preferred due date set directly by the customer, or the configured production ranges of the chosen materials and post-processing.

[MES] Automatic calculation and display of estimated finish date

We added an estimated finish date for all parts accepted for production. The estimated finish date gives feedback on the date a part is expected to finish production, based on the current date, scheduled jobs, open workflow steps and their default durations.

General improvements

  • [ERP] Date Created now includes a timestamp for all requests, quotes and orders

  • [ERP] CSS is now included in all templates

  • [ERP] Multiple order downloads now contain the order numbers in the zip file name

  • We changed OAuth to comply with OIDC

  • We enabled Javascript syntax highlighting for Helper functions

Bug fixes

  • [PLM] In status update notification e-mails a part id was shown instead of the part name. This is now fixed.

  • [PLM] Status update e-mails were sent in English although German was selected as profile language. Mails are now sent in the correct language again.

  • [PLM] We have enabled Javascript syntax highlighting for Helper functions

  • [PLM] The legend on histogram charts was missing. This is now fixed.

  • [ERP] We fixed a bug that allowed choosing a preferred due date in the past