Solutions

Claim solution configurations (ReclamoTipoReclamoSolucion / ges_reclamo_solucion).

📄️ Get solution by ID

Returns a single claim solution configuration by its primary key, including synthesized {@code actions} from legacy permission flags.

📄️ Update solution

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

📄️ Delete solution

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

📄️ Merge-patch solution

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 solutions

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

📄️ Create solution

Creates a new claim solution configuration. Business logic runs in the legacy WAR via the internal commands gateway. Requires `claimTypeId` and `solutionTypeId`.

📄️ Prototype solution for a creation form

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