Changes to Get person reports

• info

  added the non-success response with the status 400

• info

  added the non-success response with the status 401

• info

  added the non-success response with the status 403

• info

  added the non-success response with the status 408

• info

  added the non-success response with the status 423

• info

  added the non-success response with the status 429

• info

  added the non-success response with the status 500

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/person_type/oneOf[subschema #1: Person Type -> subschema #2: Person Type]/ was specialized from string to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/person_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/contains was specialized from string to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/person_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/eq was specialized from string to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/person_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_contain was specialized from string to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/person_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_eq was specialized from string to integer

• breaking

  the data/items/attributes/autotracking response's property type changed from integer to boolean for status 200

• breaking

  the data/items/attributes/custom_fields response's property type changed from string to object for status 200

• breaking

  the data/items/attributes/role_id response's property type changed from integer to no type for status 200

• warning

  deleted the header request parameter X-Organization-Id

This list may be incomplete.

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #1: Filter person report]/job_role_id/oneOf[job_role_id -> subschema #1: Job Role]/ was specialized from no type to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #1: Filter person report]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/contains was specialized from no type to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #1: Filter person report]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/eq was specialized from no type to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #1: Filter person report]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_contain was specialized from no type to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #1: Filter person report]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_eq was specialized from no type to integer

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/shared_seat/oneOf[shared_seat -> subschema #1: Shared Seat]/ was specialized from no type to boolean

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/shared_seat/oneOf[subschema #1: Operation -> subschema #2: Operation]/eq was specialized from no type to boolean

• breaking

  for the query request parameter filter, the type of property oneOf[subschema #2: Filter person report]/shared_seat/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_eq was specialized from no type to boolean

• breaking

  the data/items/attributes/shared_seat response's property type changed from no type to boolean for status 200