Item Summary
Name	Type	Multiplicity	Description
name	property PolyStringType	[0,1]	Human-readable, mutable name of the object.
description	property string	[0,1]	Free-form textual description of the object.
fetchResult	property OperationResultType	[0,1]	Result of the operation that fetched this instance of the object.
extension	container ExtensionType	[0,1]	Extension container that provides generic extensibility mechanism.
parentOrgRef	reference ObjectReferenceType	[0,-1]	Set of the orgs (organizational units, projects, teams) that the object relates to.
trigger	container TriggerType	[0,-1]	Defines triggers for an object.
metadata	container MetadataType	[0,1]	Meta-data about object creation, modification, etc.
tenantRef	reference ObjectReferenceType	[0,1]	Reference to the tenant to which this object belongs.
lifecycleState	property string	[0,1]	Lifecycle state of the object.
taskIdentifier	property string	[0,1]
ownerRef	reference ObjectReferenceType	[1,1]	The user that owns this task.
channel	property anyURI	[0,1]
parent	property string	[0,1]
subtaskRef	reference ObjectReferenceType	[0,-1]	Set of task's subtasks references.
dependent	property string	[0,-1]
dependentTaskRef	reference ObjectReferenceType	[0,-1]	Dependent tasks references, i.
executionStatus	property TaskExecutionStatusType	[1,1]
waitingReason	property TaskWaitingReasonType	[0,1]
node	property string	[0,1]
nodeAsObserved	property string	[0,1]
category	property string	[0,1]
handlerUri	property anyURI	[0,1]
otherHandlersUriStack	property UriStack	[0,1]
result	property OperationResultType	[0,1]
resultStatus	property OperationResultStatusType	[0,1]
objectRef	reference ObjectReferenceType	[0,1]
lastRunStartTimestamp	property dateTime	[0,1]
lastRunFinishTimestamp	property dateTime	[0,1]
completionTimestamp	property dateTime	[0,1]
nextRunStartTimestamp	property dateTime	[0,1]
nextRetryTimestamp	property dateTime	[0,1]	If the start of a task was delayed (typically because of unsatisfied execution constraints), the planned retry time is reported here.
progress	property long	[0,1]
operationStats	property OperationStatsType	[0,1]
stalledSince	property dateTime	[0,1]
expectedTotal	property long	[0,1]
recurrence	property TaskRecurrenceType	[1,1]
binding	property TaskBindingType	[0,1]
canRunOnNode	property string	[0,1]	Whether a task is constrained to be run on a particular node, i.
executionConstraints	property TaskExecutionConstraintsType	[0,1]	Constraints on task execution, e.
schedule	property ScheduleType	[0,1]
threadStopAction	property ThreadStopActionType	[0,1]
modelOperationContext	container LensContextType	[0,1]	Model context of the operation that is to be executed within this task.
workflowContext	container WfContextType	[0,1]	Workflow context of the operation that is to be executed within this task.

Items
- name
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Human-readable, mutable name of the object. It may also be an identifier (login name, group name). It is usually unique in the respective context of interpretation. E.g. the name of the UserType subtype is usually unique in the whole system. The name of the ShadowType subtype is usually unique in the scope of resource (target system) that it belongs to.
  
  The name may not be human-readable in a sense to display to a common end-user. It is intended to be displayed to IDM system administrator. Therefore it may contain quite a "ugly" structures such as LDAP DN or URL.
  
  Name is mutable. It is considered to be ordinary property of the object. Therefore it can be changed by invoking usual modifyObject operations. However, change of the name may have side effects (rename process).
  
  Although name is specified as optional by this schema, it is in fact mandatory for most object types. The reason for specifying the name as optional is that the name may be generated by the system instead of supplied by the clients. However, all objects stored in the repository must have a name.
- description
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Free-form textual description of the object. This is meant to be displayed in the user interface.
- fetchResult
  
  Flags: RAM,runtime,oper
  
  Multiplicity: [0,1]
  
  Result of the operation that fetched this instance of the object. It is mostly used to indicate that the object is not complete or there is some problem with the object. This is used instead of exception if the object is part of larger structures (lists as in list/search operations or composite objets). If not present then the "SUCCESS" state is assumed.
  
  This field is TRANSIENT. It must only be used in runtime. It should never be stored in the repository.
- extension
  
  Flags: dyn,RAM,runtime
  
  Multiplicity: [0,1]
  
  Extension container that provides generic extensibility mechanism. Almost any extension property can be placed in this container. This mechanism is used to extend objects with new properties. The extension is treated exactly the same as other object properties by the code (storage, modifications, etc), except that the system may not be able to understand their meaning.
- parentOrgRef
  
  Flags: RAM
  
  Multiplicity: [0,-1]
  
  Set of the orgs (organizational units, projects, teams) that the object relates to. This usually means that the object belongs to them but it may have other meanings as well (e.g. user manages an organizational unit).
- trigger
  
  Flags: RAM,runtime,oper
  
  Multiplicity: [0,-1]
  
  Defines triggers for an object. Trigger is an action that should take place at specified time or under some other condition.
- metadata
  
  Flags: RAM,runtime,oper
  
  Multiplicity: [0,1]
  
  Meta-data about object creation, modification, etc.
- tenantRef
  
  Flags: RAM
  
  Multiplicity: [0,1]
  
  Reference to the tenant to which this object belongs. It is a computed value set automatically by midPoint. It is determined from the organizational structure. Even though this value is compted it is also stored in the repository due to performance reasons.
- lifecycleState
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Lifecycle state of the object. This property defines whether the object represents a draft, proposed definition, whether it is active, deprecated, and so on.
  
  There are few pre-defined lifecycle states. But custom lifecycle states may also be defined. Pre-defined lifecycle states are:
  - draft: Definition of the new object in progress. The object is NOT active. The definition may change at any moment. It is not ready yet.
  - proposed: Definition of a new object is ready for use, but there is still a review process to be applied (e.g. approval). The object is NOT active. However the definition should not change in this state.
  - active: Active and working definition. Ready to be used without any unusual limitations.
  - deprecated: Active definition which is being phased out. The definition is still fully operational. But it should not be used for new assignments. E.g. it should not be requested, it should not be approved, etc.
  - archived: Inactive historical definition. It is no longer used. It is maintained only for historical, auditing and sentimental reasons.
  - failed: Unexpected error has occurred during object lifecycle. Result of that event is that the object is rendered inactive. The situation cannot be automatically remedied. Manual action is needed.
- taskIdentifier
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- ownerRef
  
  Flags: RAM
  
  Multiplicity: [1,1]
  
  The user that owns this task. It usually means the user that started the task or a system user that is used to execute the task. The owner will be used to determine access rights of the task, will be used for auditing, etc.
- channel
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- parent
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- subtaskRef
  
  Flags: RAM
  
  Multiplicity: [0,-1]
  
  Set of task's subtasks references. TRANSIENT attribute. In the repository the parent-child relationship is stored using "parent" property.
- dependent
  
  Flags: RAM,runtime
  
  Multiplicity: [0,-1]
- dependentTaskRef
  
  Flags: RAM
  
  Multiplicity: [0,-1]
  
  Dependent tasks references, i.e. tasks that wait for the completion of this task. TRANSIENT attribute. In the repository only the identifiers are stored (see "dependent" attribute).
- executionStatus
  
  Flags: RAM,runtime,AVals:4
  
  Multiplicity: [1,1]
- waitingReason
  
  Flags: RAM,runtime,AVals:3
  
  Multiplicity: [0,1]
- node
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- nodeAsObserved
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- category
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- handlerUri
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- otherHandlersUriStack
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- result
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- resultStatus
  
  Flags: RAM,runtime,AVals:8
  
  Multiplicity: [0,1]
- objectRef
  
  Flags: RAM
  
  Multiplicity: [0,1]
- lastRunStartTimestamp
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- lastRunFinishTimestamp
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- completionTimestamp
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- nextRunStartTimestamp
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- nextRetryTimestamp
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  If the start of a task was delayed (typically because of unsatisfied execution constraints), the planned retry time is reported here. EXPERIMENTAL. TRANSIENT. This value is not stored in the repo, it is queried dynamically. (It is currently not possible to use it for filtering or sorting.)
- progress
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- operationStats
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- stalledSince
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- expectedTotal
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- recurrence
  
  Flags: RAM,runtime,AVals:2
  
  Multiplicity: [1,1]
- binding
  
  Flags: RAM,runtime,AVals:2
  
  Multiplicity: [0,1]
- canRunOnNode
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Whether a task is constrained to be run on a particular node, i.e. it will *not* be executed on a different node. If this attribute is not specified, the task will be executed on any available node.
  
  (There may be other constraints on the node(s) where this task may be run, determined e.g. by task handler.)
  
  NOTE: This attribute is not used. Please use executionConstraints/allowedNode instead.
- executionConstraints
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Constraints on task execution, e.g. a execution group, allowed/disallowed nodes, etc. EXPERIMENTAL
- schedule
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- threadStopAction
  
  Flags: RAM,runtime,AVals:4
  
  Multiplicity: [0,1]
- modelOperationContext
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Model context of the operation that is to be executed within this task. This is NOT a live information: it is a serialized form of a model context. Currently there is a specialized task handler that takes this context, unmarshalls and executes it.
- workflowContext
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Workflow context of the operation that is to be executed within this task. Points to a process instance in a workflow engine, and to an externalized view of its state.

TaskType (Object Definition)

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

Items