Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Pre-defined Lifecycle States

StateActiveFocus activeAssignments activeDescription
draftnono

Definition of the new object in progress. The object is NOT active. The definition may change at any moment. It is not ready yet.

proposednono

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.

activeYESYES

Active and working definition. Ready to be used without any unusual limitations.

deprecatedYESYES

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.

archivednono

Inactive historical definition. It is no longer used. It is maintained only for historical, auditing and sentimental reasons.

failednono

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.

...

 StateActiveDescription
draftno

Definition of a new assignment in progress (e.g. being selected in the shopping cart, but not yet requested) - EXPERIMENTAL. NOT USED.

proposedno

Requested assignment. The assignment was requested but it was not yet being granted. E.g. there is a pending approval.

activeYES

Active and working assignment.

deprecatedYES

NOT USED

archivedno

Assignment that was active in the past but it was revoked. It is kept for historical reasons.

failedno

Unexpected error has occurred during assignment lifecycle. Result of that event is that the assignment is rendered inactive. The situation cannot be automatically remedied. Manual action is needed.

In midPoint 3.6 and later the assignment state is also determined by the focus (user) lifecycle state. When the focus (user) is inactive then also the assignments are considered inactive. In that case the assignment lifecycle state is not considered. The inactive focus lifecycle state overrides assignment lifecycle state.

Note

In midPoint 3.5 the assignment lifecycle state is being taken into consideration when deciding whether assignment/inducement is active or not. But the assignment state is otherwise not used by midPoint. I.e. midPoint is not storing proposed assignments for requested assignments yet. Improvements are planned for midPoint 3.6.

...