Setting Use Properties

Record Relationship Settings

Field or Control	Description
Parent Record	If this is a subordinate or child record, specify the parent record.
Related Language Record	Specify a related language record: The master record definition, which contains the appropriate key and non-key field definitions. A clone of the master record definition, to which you add an additional key for language code. This is the related language record definition. This definition should contain only those non-key fields for which contents vary by language. Link the two record definitions by specifying the name of the related language record definition in this field on the master record definition. At runtime, the system checks the user’s language preference and retrieves the data value from the appropriate related language record definition.
Query Security Record	Specify a query security record if you want secure access to a record using a security view.
Advanced Query Security	Click to display Advanced Query Security Record Mapping dialog box, which you can use to specify multiple query security records. Using multiple query security records is described in more detail in the product documentation for PeopleTools: Query. See Query: Using Row-Level Security and Query Security Record Definitions.
Analytic Delete Record	Specify a delete record to use for optimization.
Record Name	Specify the user-defined audit record.

Audit Options

While you can audit individual fields at the field level, you might find it more efficient to have the system audit the entire row whenever a user adds, changes, or deletes information. For record-level audits, the system focuses on rows of data instead of specific fields. Consequently, a record-level audit writes a single row of audit data rather than writing multiple rows for each insert, change, or delete transaction at the field level.

Field or Control	Description
Add	Inserts an audit table row whenever a new row is added to the table underlying the record definition.
Change	Inserts one or two audit table rows whenever a row is changed in the table underlying this record definition.
Selective	Inserts one or two audit table rows whenever a field that is also included in the record definition for the audit table is changed.
Delete	Inserts an audit table row whenever a row is deleted from the table underlying the record definition.

Record-Level Auto-Update Options

These settings are used exclusively for mobile applications, enabling developers to display derived values on a mobile page. These settings are not available for subrecords.

Important:

PeopleSoft Mobile Agent is a desupported product. These features exist for backward compatibility only.

Field or Control	Description
System ID Field	Set this field to assign a unique way to identify the record for mobile synchronization purposes. You must create a user-defined index for this field.
Timestamp Field	Set this field to automatically update the field with the date and time when there is a change to the record for mobile synchronization purposes.

Record Information

Record Information contains options used during PeopleSoft upgrades.

Field or Control	Description
Tools Table	Identifies SQL tables owned by PeopleSoft PeopleTools development, which is typically the same ownership as indicated by the PPLTOOLS project.
Managed	Identifies SQL tables owned by PeopleSoft PeopleTools development that contain information that is used by managed (cached) objects.

Field or Control	Description
Append ALL (Dynamic Views)	Applies to dynamic views. If it is set, then at runtime the system appends the WHERE clause generated at runtime to all the SELECT statements in a dynamic view with a UNION. Also, if it is set, at runtime the system generates FILL as the table alias in the WHERE clause condition. For example, FILL.<record field name> LIKE '%O%'. You need to specify which table corresponds to the FILL in the dynamic view definition. For example, FROM table A FILL. You must specify the corresponding table because the same record field name may exist in two different records.

Field or Control

Description

Append ALL (Dynamic Views)

Applies to dynamic views. If it is set, then at runtime the system appends the WHERE clause generated at runtime to all the SELECT statements in a dynamic view with a UNION.

Also, if it is set, at runtime the system generates FILL as the table alias in the WHERE clause condition. For example, FILL.<record field name> LIKE '%O%'. You need to specify which table corresponds to the FILL in the dynamic view definition. For example, FROM table A FILL. You must specify the corresponding table because the same record field name may exist in two different records.

Oracle In Memory

These settings apply only to the Oracle database, beginning with Oracle 12c. Use these settings to implement Oracle In-memory Column Store (IM column store) technology with your PeopleSoft system.

For more information on the Oracle In Memory feature, see Data Management: Working With Oracle Database In-Memory.

Field or Control	Description
All Fields	Select if you want all fields in the record definition to be stored in the IM column store. When selected, the system prepares all record fields to become part of the IM column store, except for those fields which are not supported for IM operations. That is, the In Memory check box will be enabled and selected for all record fields in the record definition where the record field is supported for IM column store processing. IM column store technology does not support these data types: LONG VARCHAR LONG RAW Out-of-line columns (LOBs, VARRARYs, nested table columns) Extended data type columns Note: If you select All Fields, and the table contains any fields with a data type that is not supported for IM processing, the system will change your selection to Selective Fields upon Save. Only the record fields that are supported for IM column store processing will have the In Memory check box selected automatically by the system in the record field properties. Note: If All Fields is selected, and the record definition contains fields that are not supported for IM column store processing, those fields will be explicitly excluded from the build process DDL.
Selective Fields	Select if you want to choose individual fields to include in IM column store processing. Once selected, the In Memory check box becomes enabled on the Record Field Properties, Use tab for all record fields supported for IM column store processing. For more information on the In Memory record field property, see Setting Record Field Use Properties.

Field or Control

Description

All Fields

Select if you want all fields in the record definition to be stored in the IM column store.

When selected, the system prepares all record fields to become part of the IM column store, except for those fields which are not supported for IM operations. That is, the In Memory check box will be enabled and selected for all record fields in the record definition where the record field is supported for IM column store processing.

IM column store technology does not support these data types:

LONG VARCHAR
LONG RAW
Out-of-line columns (LOBs, VARRARYs, nested table columns)
Extended data type columns

Note: If you select All Fields, and the table contains any fields with a data type that is not supported for IM processing, the system will change your selection to Selective Fields upon Save. Only the record fields that are supported for IM column store processing will have the In Memory check box selected automatically by the system in the record field properties.

Note: If All Fields is selected, and the record definition contains fields that are not supported for IM column store processing, those fields will be explicitly excluded from the build process DDL.

Selective Fields

Select if you want to choose individual fields to include in IM column store processing. Once selected, the In Memory check box becomes enabled on the Record Field Properties, Use tab for all record fields supported for IM column store processing.

For more information on the In Memory record field property, see Setting Record Field Use Properties.

Note:

After selecting any Oracle In Memory options, you must alter the table in order for the feature to take effect. See Specifying Alter Options.