Solution Types

Claim solution types (ReclamoTipoSolucion / ges_reclamo_tipo_solucion).

📄️ Get solution type by ID

Returns a single claim solution type by its primary key.

📄️ Update solution type

Full replacement of an existing claim solution type. Send the `If-Match` header for optimistic concurrency (accepted but ignored ÔÇö not versioned).

📄️ Delete solution type

Deletes a claim solution type. Send the `If-Match` header with the current ETag (accepted but ignored ÔÇö not versioned).

📄️ Merge-patch solution type

RFC 7396 merge-patch over `application/merge-patch+json`. Send only the fields you want to change; include a field with value `null` to remove it. Use the `If-Match` header for optimistic concurrency control.

📄️ List solution types

Returns a paginated list of claim solution types with envelope `{data, totalCount, skip, limit, hasMore}`. Supports optional RSQL `filter`, `sort` (default `name:asc`), `skip`/`limit` pagination and `modifiedAfter`/`modifiedBefore` bookends.

📄️ Create solution type

Creates a new claim solution type. Business logic runs in the legacy WAR via the internal commands gateway.

📄️ Prototype solution type for a creation form

Returns a non-persisted claim solution type pre-populated with backend defaults (`enabled=true`, next `code`, current company). Optional JSON hints: `companyId`, `copyFromId`. The response has no `id`, `version` or audit fields; call `POST /api/v2/solution-types` afterwards to persist.