When setting up a System Template, consider that:
- Sharing a template is essential, as it allows users to use the template.
- Admins should remove system templates when they are no longer in use.
- Each organization must determine their needs regarding specific user groups and how to create appropriate templates for different disciplines.
Components of a System Template include:
- Auto-naming
- Auto-numbering
- Required fields
- Optional fields, such as Attributes (lists and free text fields)
Note: If using hierarchical Attributes in the template, once they are defined as required, make sure that all parent values have at least one child value so that there are no missing values when creating system objects. Hierarchical Attributes components include:
- Field Name:
- Appears in each field.
- Does not have to have the same name as the Attribute.
- Read only option: recommended for autogenerated names to prevent users from renaming.
- Placeholders for experimental components (text fields for Introduction, Conclusion, etc.).