PATCH /obp/dynamic-entity/training_progress/TRAINING_PROGRESS_ID

Partially update training_progress: only the fields supplied in the body are changed; others are preserved.

This is also the write path for field-level write-restricted fields (those declared with write_role_required or an explicit write_role). Authorisation is per field present in the body: a write-restricted field requires that field's write role, and an unrestricted field requires the entity update role. You may change a field if (and only if) you hold the role that governs it; the request is rejected with 403 (missing role) listing the roles you lack. There is no blanket entity-update precondition — holding only a field's write role is sufficient to PATCH that field alone.

Training_progress entity

Property List:

name: Name field
age: Age in years
active: Is active
internal_note: Write-restricted: settable only via PATCH by a holder of the field's write role

MethodRouting settings example:

{
  "is_bank_id_exact_match":false,
  "method_name":"dynamicEntityProcess",
  "connector_name":"rest_vMar2019",
  "bank_id_pattern":".*",
  "parameters":[
    {
        "key":"entityName",
        "value":"training_progress"
    }
    {
        "key":"url",
        "value":"http://mydomain.com/xxx"
    }
  ]
}

</details>

User Authentication is Required. The User must be logged in. The Application must also be authenticated.

{ "training_progress": { "training_progress_id": "d8839721-ad8f-45dd-9f78-2080414b93f9", "name": "Example Name", "age": 25, "active": true, "internal_note": "set by a privileged service" } }