Siebel Business Process Framework: Workflow Guide > Reference Materials for Siebel Workflow > Reference of Workflow Process Object Properties >

Reference of Process Properties and Arguments


This topic provides reference information for process properties and their arguments. It includes the following topics:

Argument Fields for a Process Property

This topic describes argument fields that can be defined for a process property in the MVPW. For configuration information, see About Process Properties.

Table 115 describes argument fields that can be defined for a process property.

Table 115. Description of Argument Fields for a Process Property
Argument Field
Description
Possible Value

Name

The name of the process property.

A descriptive name that is:

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

For more information, see About Naming a Process Step or Process Property.

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.

Possible values include:

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

Business Object

The name of the associated business object.

Read only. For more information, see Defining a Primary Business Component for a Business Object.

Business Component

The name of the business component containing the virtual field.

This value is chosen 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.

This value is chosen 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 property 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.

Possible values include:

  • Alias. Size limit for default value, not run-time value: 250 characters.
  • Binary. For variant or binary information, usually for XML data. Binary types must be assigned the None value in the In/Out property.
  • Date. For dates.
  • Hierarchy. Data type used by Siebel Enterprise Application Integration to store data from a property set. For more information, see Overview: Siebel Enterprise Application Integration.
  • Integration Object. For storing integration objects. Integration objects have the Hierarchy data type.
  • Number. For numeric data. Size limit for default value, not run-time value: 22 digits.
  • String. For alphanumeric data, usually for UTF-16 data. Size limit for default value, not run-time value: 250 characters.
  • Strongly Typed Integration Obj. A special data type for exposing a workflow process as a Siebel inbound Web service. Siebel business services use this property when creating WSDLs.

    NOTE:  For both the workflow process and business service engines, values in the Strongly Typed Integration Obj and the Integration Object properties are treated as the same data type.

Default Number

Initial value if the process property is a numeric type.

Numeric widget.

Integration Object

Data type used by Siebel EAI to store data from an integration object.

For 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. For more information, see About the Workflow User Event Service Business Service.

Check mark.

Access Mode

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

Read-only or Read-write.

Argument Fields for an Input Argument

Table 116 describes argument fields that can be defined on an input argument for the Business Service step, Sub Process step, and Wait step.

Table 116. Description of Argument Fields for an Input Argument
Argument Field
Description
Possible Value

Preferred Sequence (For business service steps only.)

(This cell is left intentionally empty.)

(This cell left is intentionally empty.)

Input Argument (For business service steps only.)

The name of the input argument.

(Required.) The picklist displays input arguments existing for the chosen business service method.

A method argument appears in this picklist if it is defined as a business service method argument, the Hidden flag is set to FALSE, and the type is input or input/output.

Subprocess Input (For Sub Process steps only.)

The name of the input argument.

(Required.)

Type

The type of argument.

(Required.) Choices in the picklist include:

  • Literal
  • Process Property
  • Business Component
  • Expression

Value

A string value.

For Literal and Expression type input arguments. This can be a picklist, depending on the argument chosen. String values can only be a maximum of 32,767 characters.

Property Name

The name of the process property.

For Process Property-type input arguments.

Business Component Name

The name of a business component within the business object of the business process.

For Business Component-type input arguments.

Business Component Field

The name of a field within the business component.

For Business Component Field-type input arguments.

Changed

(This cell is intentionally empty.)

Check mark.

Argument Fields for an Output Argument

Table 117 describes argument fields that can be defined on an output argument for a business service step, sub process step, and siebel operation step.

Table 117. Description of Argument Fields for an Output Argument
Argument Field
Description
Possible Value

Property Name

The name of the Process Property to store the results.

(Required.) When Property Name is clicked, a picklist of process properties that have been defined for the process appears. For more information, see Passing a Process Property In and Out of Workflow Steps.

Type

The type or argument.

(Required.) Choices in the picklist include:

  • Literal
  • Output Argument
  • Business Component
  • Expression

Value

A string value.

For Literal or Expression arguments. Note that string values can only be a maximum of 32,767 characters.

Output Argument (For business service steps only.)

The name of the output argument.

For Output Arguments type.

This is a picklist of output arguments for the chosen method. An argument appears in this picklist if it is defined as a business service method argument, the Hidden flag is set to FALSE, and the type is Output or Input/Output.

Subprocess Output (For Sub Process steps only.)

The name of the output argument.

For Output Arguments type.

Business Component Name

The name of the business component within the business object of the business process.

For Business Component type.

Business Component Field

The name of a field within the business component.

For Business Component Field type.

NOTE:  A business component field based on a multi-value group cannot be chosen as a value for an input or output argument. If you need to use a field based on a multi-value group, you must define a business component for the field and link it to the appropriate business object. For more information, see Configuring Siebel Business Applications.

Argument Fields for a Recipient Argument

Table 118 describes argument fields for a recipient argument. For configuration information, see About the Sub Process Step.

Table 118. Description of Argument Fields for a Recipient Argument
Argument Field
Description
Define This Property If. . .
Possible Value

Recipient Type Code

The type of recipient.

(This cell is intentionally empty.)

This value is fixed as "User" and cannot be changed.

Value Type Code

The source from which the recipient value comes.

(This cell is intentionally empty.)

Values in the picklist for this property include:

  • Name
  • Expression
  • Process Property
  • Business Component

Recipient Name

The name of the recipient. This property is a pick applet which displays the first name, last name, and login name of users in the database.

The Value Type Code is set to Name.

Choose one name from the list of users available in the database.

Business Component Name

The name of the business component.

The Value Type Code is set to Business Component.

Choose one business component.

Business Component Field

The name of the business component field.

The Value Type Code is set to Business Component.

Choose one business component field.

Process Property Name

The name of the process property.

The Value Type Code is set to Process Property.

Choose one process property.

Expression

If the recipient value is derived from an expression, the expression is entered in this property.

The Value Type Code is set to Expression.

The expression from which the recipient value is derived.

Argument Fields for a Search Specification Input Argument

Table 119 describes argument fields that can be defined for a search specification input argument on the Search Spec Input Arguments tab of the MVPW.

Table 119. Description of Argument Fields For a Search Specification Input Argument
Argument Field
Description

Expression Business Component

If you entered Expression in the Type argument field, enter the name of the business component that evaluates the expression.

For example, in the Search Specification argument field, you can enter:

"[Due Date] < '" + [Order Date] + "'"

The Expression business component evaluates Order Date so that the search specification becomes:

[Due Date] < '07/04/2001 18:51:26'

Filter Business Component

Enter the name of the business component that provides the group of records on which you perform your search.

Search Specification

If you entered Literal in the Type argument, enter a literal value in the form of an expression. For example, = 100.

If you entered Expression in the Type argument, enter an expression such as [Status] LIKE '*Open*'. The expression is evaluated by the Expression business component you specify.

Type

Required. Choose the type of value on which to base your search: Literal or Expression.

Comments

Enter a text description of the purpose of the search.

Changed

Check mark indicates a changed search specification.

Siebel Business Process Framework: Workflow Guide Copyright © 2008, Oracle. All rights reserved.