Feedback (Error) handling activity diagram

Activity Diagram

This activity diagram outlines various scenarios for handling error situations between the Pension Service Provider (PSP) and the Fiduciary Manager (FM). The scenarios involve synchronous and asynchronous validations with varying outcomes, such as approved, rejected, or invalid feedback messages. The flow demonstrates the sequence of interactions, validations, and responses between the participants.

Source: issue #75

---

Activity Diagram as text:

Scenario 1: Synchronous Validation - OK

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs validations.
• If the validations are successful, FM returns an HTTP status 200 (approved) without a response body.

---

Scenario 2: Synchronous Validation - NOK

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs validations.
• If the validations fail, FM returns an HTTP status 400 (bad request) and includes a VBPUO_Feedback_Message as the response body, detailing the issues.

---

Scenario 3: Asynchronous Validation - OK

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs technical validation and responds with an HTTP status 202 (accepted).
• FM then performs functional and back-office validations.
• Upon successful validation, FM sends a VBPUO_Feedback_Message with the status "Geaccepteerd" (field STATUSTYPE) to PSP.
• PSP processes the message and confirms with an HTTP status 200 or 201 (created/processed).

---

Scenario 4: Asynchronous Validation - NOK

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs technical validation and responds with an HTTP status 202 (accepted).
• FM then performs functional and back-office validations.
• If the validations fail, FM sends a VBPUO_Feedback_Message with the status "Afgewezen" (field STATUSTYPE) to PSP.
• PSP processes the rejection and responds with an HTTP status 200 or 422 (unprocessable).

---

Scenario 5: Asynchronous Validation - NOK with an Invalid Feedback Message

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs technical validation and responds with an HTTP status 202 (accepted).
• FM performs functional and back-office validations.
• FM sends a VBPUO_Feedback_Message with the status "Afgewezen" (field STATUSTYPE), but the message is invalid.
• PSP processes the message and responds with an HTTP status 400 (bad request).
• FM may escalate by contacting PSP through an alternative channel.

---

Scenario 6: Asynchronous Validation - OK with an Invalid Feedback Message

• PSP sends Bericht_1._Vermogen_(0001a) to FM.
• FM performs technical validation and responds with an HTTP status 202 (accepted).
• FM performs functional and back-office validations.
• FM sends a VBPUO_Feedback_Message with the status "Geaccepteerd" (field STATUSTYPE), but the message is invalid.
• PSP processes the message and responds with an HTTP status 400 (bad request).
• FM may escalate by contacting PSP through an alternative channel.