Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: cleaned up grammar

...

  • Unspecified Positions when the new appointment is missing the position ID (potential data issue/bug) - fairly uncommon unless org data is altered after the proposal is created.

  • Inactive Position when the position for a new primary appointment is set to inactive - fairly uncommon unless org/position data is altered after the proposal is created.

  • Potentially Vacant Position when an active position will no longer have anyone appointment appointed to the position. This takes into account multiple-type positions where other appointments to that position may or may not change with moves.

  • “Normal” Positions with Multiple Incoming Persons when a position is set to normal - style (limited to one active appointment) has multiple appointments set to start or overlap with the moves.

  • “Joint” Positions with More than Two Incoming Persons when a joint-style position (limited to two people or one couple) has multiple appointments set to start or overlap with the new moves.

  • Persons with Multiple Primary Appointments when somebody has multiple primary appointments that start or overlap with the execution of the new moves.

  • Persons without Primary Appointments when somebody no longer has a primary appointment or has a gap between primary appointments with the execution of the new moves.

  • Persons Being Moved to Appointments They are in Already when the proposal items “moves” somebody into the same primary or additional position they’re in already - fairly uncommon but could arise with data updates after the proposal is created.

...

Page Properties
hiddentrue


Related issues

Jira Legacy
serverId97afdc6c-014b-3402-a56a-74629435c6f5
keyOMSSD-382