CS
SCALE.sdm
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage
Confidential information

1.254

Release date: January 27, 2026

New featureThere is a new function that automatically cleans up unused data in the local vault. [ #1199 ]

This function can be accessed by clicking on the red   icon in the upper right corner, selecting Settings from the drop-down menu and expanding the Local storage section. The following settings can be configured here:

  • Target size (in GBs): The target size of the data stored in the vault in gigabytes.
  • Perform unattended cleanups: If this option is selected ( ), then unused data in the local vault will automatically be cleaned up at the specified times.
  • Time window start time: The time when the cleanup function should start.
  • Time window end time: The time when the cleanup function should end.
  • Repeat option: How often the cleanup function should be repeated.
  • Select a Day: The day of the week when the cleanup function should run.

image
Local storage settings

New featureWhen an assembled run is assembled again, the UUID of the selected assembled run is now provided in the run context. [ #11435 ]

The context parameter SELECTED_PRIOR_RUN_UUID is now available. It can be used, e.g. in assembly scripts to specify whether a run configuration or an assembled run is assembled.

Bug fix"has_parameter()" no longer leads to a parameter evaluation error. [ #246 ]

In the past, after duplicating a table and selecting a run, the parameters that used has_parameter() led to an evaluation error. This has been fixed.

Bug fixThe names of runs and run configurations are no longer truncated in the "Runs" view. [ #11542 ]

This fix relates to the Runs view. In the past, the last few characters were cut off the names of runs and run configurations. This has been fixed. The names are now displayed in their entirety.

Bug fixThe remote assemble batch client no longer fails with a traceback right before the blob download. [ #11534 ]
Bug fixWhen editing components, groups without history comments are now correctly displayed as empty. [ #45 ]

This fix relates to the way that history comments are propagated when editing components. In the past, it looked like the groups above an edited component already had history comments, even though they did not. Rather than being displayed as empty, the groups were temporarily displayed with the comment from the pool version. This has been fixed.