1.250

For example:

• The comment must explain the reason why the change was made.
• If the comment is about a material change, the comment should specify the material that was changed and the material it was changed to.
• If the comment is about a change to a shell thickness, the comment should specify the original thickness and the new thickness.

When users enter a history comment, the AI checks if the history comment meets all of the requirements. If the comment does not meet the requirements, then the user sees a warning that explains which information is missing.

All OpenSearch-specific names and icons were replaced with SCALE.sdm names and icons. For example:

• The name “OpenSearch Dashboard” was changed to “SCALE.search”.
• The OpenSearch logo was changed to the SCALE.sdm logo.

Clicking on this link causes a new  Model tab to open. The pool version is selected in this tab. Note: The pool version link can only open a new  Model tab automatically, if the client was configured for such links in the operating system. Alternatively, the link can be copied and then pasted into a  Model client that is already running.

For example:

• App scripts could now open the job log file of a remote submit job and automatically “jump” to the part of the log file that corresponds to the job node the user selected and started the app on.
• Information could automatically be sent from the clicked job node as a query to an LLM model to help the user investigate errors.

The AuxiliaryContentLoader now provides this information. Usage:

from external_application import edit_data, JobMetadata

for entry in edit_data.selection:
    if isinstance(entry, JobMetadata):
        print(f"JOB INFO:\ntitle: {entry.title}\nmessage: {entry.message}\nstatus: {entry.status}")

In the past, it was not possible to add or change the history comment for multiple objects at once. Instead, the text “Symbol()” was displayed in the Changes window and the history comment could not be changed. This has been fixed.