MetadataType (Complex Type)

Items

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  The timestamp of "create" operation request. It is set once and should never be changed.

  In case of "background" processes to create object (e.g. create with approval) this should be the timestamp when the process started. I.e. the timestamp when the operation was requested.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,1]

  Reference to the user that requested the "create" operation for this object or assignment.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  Comment of the user that requested the "create" operation for this object or assignment.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper,I

  Multiplicity: [0,1]

  The timestamp of data creation. It is set once and should never be changed.

  In case of "background" processes to create object (e.g. create with approval) this should be the timestamp when the process ended. I.e. the timestamp when the operation was executed.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,1]

  Reference to the user that created the data.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,-1]

  Reference to the user that approved the creation of the data (if there was such a user). This is multi-value reference therefore multiple approvers may be recorded. However the order and hierarchy of the approvers is lost.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,-1]

  Comments of the approvers during the creation of the data. Note that these comments are in no particular order, so basically it is not known who entered which comment.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  The timestamp of creation approval.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper,I

  Multiplicity: [0,1]

  Channel in which the object was created.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,1]

  Reference to the task that created the object (if it was a persistent one).

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper,I

  Multiplicity: [0,1]

  The timestamp of last data modification. It should be updated to a current time when the object is modified. The modifications that change only operational attributes may not update the modify timestamp.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,1]

  Reference to the user that modified the data.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,-1]

  Reference to the user that approved the last modification of the data (if there was such a user). This is multi-value reference therefore multiple approvers may be recorded. However the order and hierarchy of the approvers is lost.

  Even though this is multi-value reference it will get overwritten after each approval. The multiple values are used only if all the approvers are known at the same time, e.g. if multi-level approval is evaluated at the same time. But generally this refers only to the last approval event.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,-1]

  Comments of the approvers during the last modification of the data. Note that these comments are in no particular order, so basically it is not known who entered which comment.

  Even though this is multi-value property it will get overwritten after each approval.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  The timestamp of last modification approval.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper,I

  Multiplicity: [0,1]

  Channel in which the object was last modified.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,1]

  Reference to the task that last modified the object (if it was a persistent one). If the last modification was carried out by synchronous task, this reference will be empty.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  The timestamp last provisioning operation that was based on this object. E.g. the timestamp of last modification of any account based on the data from the user. This value is only updated if there was any real change in the resource.

  This meta-datum is used as an informational property that tells when the data were last synchronized in outbound direction. But it has another important role. It is used indirectly to trigger optimistic locking conflicts that are used to detect a "clean" recompute (i.e. recompute that is processing data without any outside interaction).

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  When last certification related to this item was finished. Only certifications that resulted in non-null outcome are taken into account.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  Outcome (URI) of the last certification. Only certifications that resulted in non-null outcome are taken into account.

• $itemDefinition.Name.LocalPart

  Flags: RAM,oper

  Multiplicity: [0,-1]

  Reference to the user that certified the data. Contrary to approver/modifierRef, this field is filled-in also when certifier denies the item status. Only certifications that resulted in non-null outcome are taken into account.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,-1]

  Comments of the certifiers during the last certification of the data. Note that these comments are in no particular order, so basically it is not known who entered which comment.

  Even though this is multi-value property it will get overwritten after each approval.

  Only certifications that resulted in non-null outcome are taken into account.

• $itemDefinition.Name.LocalPart

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  Identifies the mapping that caused the automated creation of this object or assignment.