1.253

It is now possible to define execution dependencies between post-edit scripts (e.g., script A must complete successfully before script B starts). These dependencies are now enforced whenever post-edit scripts are executed.

Introduced fine-grained access control in SCALE.search Dashboards for component search data based on the logged-in user’s role, pool, and group permissions. Users can now only view and interact with data if they hold the appropriate role (currently limited to ProjectManager) and if they have sufficient pool and group access rights. This change replaces the previous behavior where all logged-in users had unrestricted access to all visualizations and data.

Added visualization of tags for assembled runs and run configurations in the Runs view. Users can now see tags directly alongside their assembled runs, enabling quick categorization (e.g., marking runs as relevant or not relevant). This supports workflows where the same run configuration is assembled multiple times and needs to be distinguished through tagging.

When there are a large number of pools and pool entries, the secondary sync can take longer than a day. During this time, service outages are expected and sometimes even inevitable. Restarting the whole sync process again each time would take considerable ramp-up time on each restart. Therefore, we have added more fine-grained retry and back-off mechanisms to the secondary service sync and the BLOBDownloader.

Now when users right-click on a pool version and select Derive new from the context menu, the newly created pool version is immediately displayed in expanded form. That means, the user can edit the history comment directly.

This issue occurred when editing two snippets of the same (private or live) component. In the past, changes to the second snippet were lost when a first snippet of the same component was saved afterward. This has been fixed. The system now correctly preserves edits made to all snippets of the same component, even when they are edited and saved in sequence.

In the past, canceling local assembly jobs had no effect and assemblies continued running until completion. This has been fixed. Local assembly jobs are now reliably stopped when canceled.

In the past, importing new files failed after an edit if the target component group did not yet exist in the corresponding sub-pool. This has been fixed, ensuring that new files can be imported regardless of the prior existence of their target component group.

Fixed an inconsistency where deprecated objects in run configurations of private pool versions were shown as warnings in the UI, even though they caused errors during assembly. Deprecated objects that will lead to assembly failure are now correctly displayed as errors in the Properties tab, ensuring the severity shown in the UI matches the actual assembly behavior.

For example, imagine you select a run config that has the attribute “Region = EU”, but this attribute is inactive. In the past, any components with different values (e.g. “Region = US”) were considered as not matching in the new component grid. This behavior has been fixed. These components are now considered as matching since the attribute is inactive.