# WfProcessSpecificationType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

Specification of a process that is to be started. EXPERIMENTAL

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
ref | property string | [0,1] | Reference to existing process specification.
name | property string | [0,1] | Name for this process specification.
order | property int | [0,1] | In what order this process specification is to be considered.
deltaFrom | container DeltaSourceSpecificationType | [0,-1] | TODO
includeAction | property string | [0,-1] | What approval actions to include during approval schema creation for this process.
includeActionIfPresent | property string | [0,-1] | What approval actions to include during approval schema creation for this process.
approvalDisplayName | property LocalizableMessageTemplateType | [0,1] | Name for approval process.

- ### Items

  - #### ref

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Reference to existing process specification.

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Name for this process specification.

  - #### order

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    In what order this process specification is to be considered.

  - #### deltaFrom

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    TODO

  - #### includeAction

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    What approval actions to include during approval schema creation for this process. If they are not triggered an exception is thrown.

  - #### includeActionIfPresent

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    What approval actions to include during approval schema creation for this process. If they are not triggered they are silently skipped.

  - #### approvalDisplayName

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Name for approval process. If not specified, name from approval action(s) is taken. If not specified even there, the name is derived from triggered constraints (short messages).