Basic Fields

These fields appear for all source types; they are displayed when the Create New Component dialog opens. Other fields, discussed below, are displayed when a source type is selected.

Fields Available for All Source Types table

Field	Description
Name	Identifies the component; appears in many UI features. Required.
Description	The optional description can be used to convey additional information about the component. If the component is used by more than one application, for example, entering "Used in applications A and B" can help identify how the component is used.
Template	A component template enables you to reuse component definitions; components based on templates inherit the template's source configuration, properties, and process. Any previously created templates are listed. A component can have a single template associated with it. The default value is None. If you select a template, the Template Version field is displayed which is used to select a template version. By controlling the version, you can roll-out template changes as required. The default value is Latest Version which means the component will automatically use the newest version (by creation date). See Component Templates. Note If you select a template that has a source configured for it, the dialog box will change to reflect values defined for the template. Several fields, including the Source Config Type field, will become populated and locked.
Source Config Type	Defines the source type for the component's artifacts; all artifacts must have the same source type. Selecting a value displays additional fields associated with the selection. Source-dependent fields are used to identify and configure the component's artifacts. If you selected a template, this field is locked and its value is inherited from the template.
Import Versions Automatically	If checked, the source location is periodically polled for new versions; any found are automatically imported. The default polling period is 15 seconds, which can be changed with the System Settings pane. If left unchecked, you can manually create versions by using the Versions pane. By default, the box is unchecked.
Copy to CodeStation	This option—selected by default—creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. If unchecked, only meta data about the artifacts are imported. Serena recommends that the box be checked.
Default Version Type	Required. Defines how versions are imported into CodeStation. Full means the version is comprehensive and contains all artifacts; Incremental means the version contains a subset of the component's artifacts. Default value is: Full.
Inherit Cleanup Settings	Determines how many component versions are kept in CodeStation, and how long they are kept. If checked, the component will use the values specified on the System Settings pane. If unchecked, the Days to Keep Versions (initially set to -1, keep indefinitely) and Number of Versions to Keep (initially set to -1, keep all) fields are displayed, which enable you to define custom values. The default value is checked.

Field

Description

Name

Identifies the component; appears in many UI features. Required.

Description

The optional description can be used to convey additional information about the component. If the component is used by more than one application, for example, entering "Used in applications A and B" can help identify how the component is used.

Template

A component template enables you to reuse component definitions; components based on templates inherit the template's source configuration, properties, and process. Any previously created templates are listed. A component can have a single template associated with it. The default value is None.

If you select a template, the Template Version field is displayed which is used to select a template version. By controlling the version, you can roll-out template changes as required. The default value is Latest Version which means the component will automatically use the newest version (by creation date). See Component Templates.

Note

If you select a template that has a source configured for it, the dialog box will change to reflect values defined for the template. Several fields, including the Source Config Type field, will become populated and locked.

Source Config Type

Defines the source type for the component's artifacts; all artifacts must have the same source type. Selecting a value displays additional fields associated with the selection. Source-dependent fields are used to identify and configure the component's artifacts. If you selected a template, this field is locked and its value is inherited from the template.

Import Versions Automatically

If checked, the source location is periodically polled for new versions; any found are automatically imported. The default polling period is 15 seconds, which can be changed with the System Settings pane. If left unchecked, you can manually create versions by using the Versions pane. By default, the box is unchecked.

Copy to CodeStation

This option—selected by default—creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. If unchecked, only meta data about the artifacts are imported. Serena recommends that the box be checked.

Default Version Type

Required. Defines how versions are imported into CodeStation. Full means the version is comprehensive and contains all artifacts; Incremental means the version contains a subset of the component's artifacts. Default value is: Full.

Inherit Cleanup Settings

Determines how many component versions are kept in CodeStation, and how long they are kept. If checked, the component will use the values specified on the System Settings pane. If unchecked, the Days to Keep Versions (initially set to -1, keep indefinitely) and Number of Versions to Keep (initially set to -1, keep all) fields are displayed, which enable you to define custom values. The default value is checked.