Name

The name of the process property.

Required. A descriptive name that is:

• Consistent with your overall naming strategy
• Meaningful to the designer of the process
• Unique

Display Name

A user-friendly version of the property name.

The Display Name can be the same as or different from the Name.

In/Out

Describes whether or not the process property is passed in or out of the process, passed into the process and returned, or used only within the process.

• In. The process property is passed into the process. (Binary types cannot be assigned this value.)
• Out. The process property is passed out of the process. (Binary types cannot be assigned this value.)
• In/Out. The process property is passed into the process and returned. (Binary types cannot be assigned this value.)
• None. The process property is used only within the process.

Business Object

The name of the associated business object.

Read only. See Planning Workflow Processes for more information on defining the primary component for a business object.

Business Component

The name of the business component containing the virtual field.

(Optional) This value is selected from a picklist of business components belonging to the workflow process business object.

Virtual Field

The name of the business component field mapped to the workflow process property.

(Optional) This value is selected from a picklist of fields belonging to the business component. Only calculated fields with no calculated values appear in this picklist.

Default String

Initial value if the process property is a string type.

Free-form text. If you enter <Value>, the process property is initialized with the value in the Value field of the workflow input property set.

Default Date

Initial value if the process property is a date type.

Calendar widget.

Data Type

The type of data that can be stored in the process property.

• String. For alphanumeric data.
• Date. For dates.
• Number. For numeric data.
• Hierarchy. Data type used by eBusiness Application Integration to store data from a property set. For more information, see Overview: Siebel eBusiness Application Integration Volume I.
• Binary. For variant or binary information. Binary types must be assigned the None value in the In/Out field.
• Integration Object. For storing integration objects. Integration objects have the Hierarchy data type.

Default Number

Initial value if the process property is a numeric type.

Numeric widget.

Integration Object

Data type used by eBusiness Application Integration to store data from an integration object.

Example: "Account - Get Oracle Customer (Oracle)"

Correlator Flag

Makes the process property ready for use as a correlator (a piece of business data that identifies the recipient of the incoming message). See About the Workflow User Event Business Service.

Check mark.

Access Mode

Controls whether a process property is read-only or read-write.

Read-only or Read-write.