Share this page

# Example of Completed Object Type Configuration Sheets

The following tables are an example of a completed set of object type configuration sheets.

Table A-16. Example of object type information
Field Name | Value
--- | ---
Object Type Name | Dev to Test File Migration
Description | Deployment of a file from Dev server to Test server.

Table A-17. Example of object type fields
# | Field Name | Description
--- | --- | ---
1 | File Location | The name of the field. SeeTable A-18. Example of validation for File Location and Table A-19. Field validation for File Location.
2 | Sub Path | The name of the field. User this field to select the directory containing the file to be deployed. See Table A-20. Example of validation for Sub Path and Table A-21. Field validation for Sub Path.
3 | File Name | The name of the file. See Table A-22. Example of validation for File Name and Table A-23. Field validation for File Name.

Table A-18. Example of validation for File Location
Field Name | Definition
--- | ---
Field Name | File Location
Validation | See Table A-19. Field validation for File Location.
Field Behavior
Attributes: | Display: Yes, the field is visible on the package line. Editable: Yes, the field can be edited after the package is submitted. Display Only: Never. This field can be edited. If set to Always, you can never edit this field. Required: Always. This field must contain a value.
Default Value | None
Dependencies
Clear field when | None
Display only when | None
Required when | None

Table A-19. Field validation for File Location
Validation | Definition
--- | ---
Existing Validation? | DLV - File Location
New Validation? | Not Applicable
Validation Type (text field, auto-complete list, and drop-down list) | Drop-down list.
Validation Definition (list of values or SQL) | SQL

Table A-20. Example of validation for Sub Path
Field Name | Definition
--- | ---
Field Name | Sub Path
Validation | See Table A-21. Field validation for Sub Path.
Field Behavior
Attributes: | Display: Yes, the field is visible on the package line. Editable: Yes, the field can be edited after the package is submitted. Display Only: Never. This field can be edited. If set to Always, you can never edit this field. Required: Always. This field must contain a value.
Default Value | None
Dependencies
Clear field when | None
Display only when | None
Required when | None

Table A-21. Field validation for Sub Path
Validation | Definition
--- | ---
Existing Validation? | Directory Chooser
New Validation? | Not Applicable
Validation Type (text field, auto-complete list, and drop-down list) | Directory Chooser
Validation Definition (list of values or SQL) | Default behavior

Table A-22. Example of validation for File Name
Field Name | Definition
--- | ---
Field Name | File Name
Validation | See Table A-23. Field validation for File Name.
Field Behavior
Attributes: | Display: Yes, the field is visible on the package line. Editable: Yes, the field can be edited after the package is submitted. Display Only: Never. This field can be edited. If set to Always, you can never edit this field. Required: Always. This field must contain a value.
Default Value | None
Dependencies
Clear field when | None
Display only when | None
Required when | None

Table A-23. Field validation for File Name
Validation | Definition
--- | ---
Existing Validation? | File Chooser - Full File Name
New Validation? | Not Applicable
Validation Type (text field, auto-complete list and drop-down list) | File Chooser
Validation Definition (list of values or SQL) | Default Behavior

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: