Signals Notebook: Table Definition Updates and Origin Template Property Behavior

When updating table definitions in Signals Notebook 25.10, the system now automatically synchronizes the Origin Template (Original Name) property if a system administrator has renamed the underlying table template.

What Changed in Version 25.10

Previously, when a table template was renamed after a table had been created, the Origin Template property would retain the original template name, potentially confusing which template was actually used.

New Behavior: After updating a table definition, if the source table template has been renamed since the table's creation, the Origin Template (Original Name) property will automatically update to reflect the template's current name.

Impact

Who is affected:
• Users who update existing table definitions
• System administrators who rename table templates
• Teams working with legacy tables created from renamed templates

Benefits:
• Improved template traceability and accuracy
• Reduced confusion when identifying table origins
• Better alignment between table properties and current template names

Example Scenario

1. Initial State: A table is created using a template named "Compound Analysis v1"
2. Admin Action: System administrator renames the template to "Compound Analysis v2"
3. User Action: User updates the table definition
4. Result: The Origin Template property automatically updates from "Compound Analysis v1" to "Compound Analysis v2"

Important Notes
• This update only occurs when you actively modify the table definition
• Tables that are not updated will continue to show the original template name
• This is an automatic process and requires no user intervention
• The change ensures consistency between current template names and table metadata

Related Information
• Updating Table Definitions in Signals Notebook
• Managing Table Templates
• What's New in Signals Notebook 25.10