Signals Notebook provides a default notebook template (DEFAULT_NOTEBOOK) that serves as the foundation for all notebooks created in the system. Unlike other system objects, notebooks can only have one template, which cannot be renamed or deleted. This article explains how to view, configure, and customize the default notebook template to meet organizational requirements while maintaining system integrity.
Solution:
Understanding the Default Notebook Template
The DEFAULT_NOTEBOOK template has several unique characteristics:
- It is automatically generated by the system
- It is the only notebook template available (no new notebook templates can be created)
- It cannot be renamed or deleted
- It is automatically shared with the Administrators and All Users groups
- Only users with system administrator roles can edit the template
Accessing the Default Notebook Template
- Log in to Signals Configuration with system admin or config admin privileges
- Click on the System Objects smart folder
- Select Notebook from the list of system objects
- Click on Template to access the DEFAULT_NOTEBOOK template page
Customizing the Default Notebook Template
System administrators can customize the default template in several ways:
Adding Comments:
- Add comments to provide guidance or context for notebook creation
Managing Fields:
- Click the Fields button to access field management
- View default fields (Name and Description)
- Add new fields to capture standardized notebook metadata
- Edit existing fields to change their properties or requirements
Template Properties:
- View template properties including description
- Monitor creation and modification history
Sharing Settings:
- Share the template with individual users or groups with Read, Write, or Full Control privileges
- Note: All Users group cannot be removed from the template's sharing list
- The default sharing privilege for All Users is set to Read and cannot be changed
Configuring Fields in the Default Notebook Template
Editing Existing Fields: The Name and Description fields are editable but not deletable. The Name field can be configured as:
- Text type: Users must manually enter notebook names
- Number sequence: Notebook names are generated automatically based on the selected sequence format
- Date: Includes date information in the notebook name
- Hyperlink: Allows linking to external resources (supports HTTP, HTTPS, FTP, FTPS, SFTP)
- Internal Reference: Creates references to internal system objects
Adding New Fields:
- Click the "Add New Field" button
- Configure the field with:
- Field Label: Enter a name for the field
- Attribute: Select the field type (text, number, list, date, etc.)
- Multi Select: Allow selection of multiple values from a list (if applicable)
- Read Only: Make the field non-editable if checked
- Required: Make the field mandatory if checked
Creating Parent-Child Field Relationships
- Add a field and select a parent list as the attribute type (this parent list should be created under Attributes first)
- Add another field and select the child field associated with the parent
- In the "Specify Parent List" field, select the parent list
- A tree icon will appear next to child fields in the Fields page, indicating the parent-child relationship
Template Management Options
While the default template cannot be deleted or renamed, administrators can:
- Export to ZIP: Generate a ZIP file of the template by selecting Export to ZIP from the Actions button menu
Important Notes
- Changes to template attributes only affect newly created notebooks, not existing ones
- Parent-child relationships affect how users select values:
- When a parent value is selected, only associated child values are displayed
- If no parent value is selected, all child values are displayed (including orphans)
- Selecting an incorrect parent value after selecting a child value will clear the child value
Best Practices
- Standardization: Configure the default template to include standard fields required for all notebooks
- Documentation: Maintain documentation of changes made to the default template
- User Communication: Inform users about significant changes to the default template
- Regular Review: Periodically review the default template to ensure it continues to meet organizational needs
- Field Organization: Design fields to support your organization's notebook categorization and search requirements
By properly configuring the default notebook template, organizations can ensure that all notebooks maintain consistent structure and capture essential information required for compliance and data management.
Comments
0 comments
Article is closed for comments.