Partially update supervisory_finding
PATCH /obp/dynamic-entity/banks/ogcr/supervisory_finding/SUPERVISORY_FINDING_ID
OBPv4.0.0-dynamicEntity_patchsupervisory_finding_ogcr Roles: CanUpdateDynamicEntityRecord_supervisory_finding(per bank) _Supervisory_finding(ogcr)Dynamic-EntityDynamic
Partially update supervisory_finding: 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.
A Member State finding of non-conformity (Art. 10). This is separate from the audit report's non_conformities_list, which the certification body writes. This Dynamic Entity is part of OGCR.
Property List:
- supervisory_finding_id: Internal identifier for the finding.
- authority_id: The authority that raised the finding.
- certification_body_id: The body the finding concerns.
- certification_scheme_id: The scheme informed. Optional.
- audit_report_id: The audit report concerned, if any. Optional.
- finding_date: Date the non-conformity was identified.
- description: What was found.
- notified_date: Date the body and scheme were informed.
- published: Whether the finding is public in the registry.
MethodRouting settings example:
<details>
{
"is_bank_id_exact_match":false,
"method_name":"dynamicEntityProcess",
"connector_name":"rest_vMar2019",
"bank_id_pattern":".*",
"parameters":[
{
"key":"entityName",
"value":"supervisory_finding"
}
{
"key":"url",
"value":"http://mydomain.com/xxx"
}
]
}
</details>
User Authentication is Required. The User must be logged in. The Application must also be authenticated.
Example request body
{
"supervisory_finding_id": "sf_01HZZ6P9S4Q",
"authority_id": "auth_01HZZ4K7Q2M",
"certification_body_id": "cb_01HZZ1M2A3B4C",
"certification_scheme_id": "cs_01HZZ1K0X5F6Q7R8S9T0",
"audit_report_id": "ar_01HZZ7R1T5U",
"finding_date": "2027-03-10",
"description": "Audit sampling below scheme minimum",
"notified_date": "2027-03-11",
"published": true
}Example success response
{
"bank_id": "ogcr",
"supervisory_finding": {
"supervisory_finding_id": "sf_01HZZ6P9S4Q",
"authority_id": "auth_01HZZ4K7Q2M",
"certification_body_id": "cb_01HZZ1M2A3B4C",
"certification_scheme_id": "cs_01HZZ1K0X5F6Q7R8S9T0",
"audit_report_id": "ar_01HZZ7R1T5U",
"finding_date": "2027-03-10",
"description": "Audit sampling below scheme minimum",
"notified_date": "2027-03-11",
"published": true
}
}Possible errors (4)
- OBP-20001: User not logged in. Authentication is required!
- OBP-20006: User is missing one or more roles:
- OBP-10001: Incorrect json format.
- OBP-50000: Unknown Error.