Reply structured error messages in RuntimeCR to KEB

[tobiscr]

Description

KIM is currently replying plain strings to KEB in RuntimeCRs. This has several limitations and makes it hard to provide well formatted and informative error messages to our BTP customers.

We agreed to use structured data in the future (e.g. JSON) in our error messages. This has several advantages:

• Provide metadata about error cases (e.g. which logic e.g. extender / converter fired the failure, timestamp etc.)
• Deliver more flexible error messages which can be translated in the UI smoothyl (distinguish between static error string and it's dynamic parts)
• Make the error processable by machines
  etc.

AC:

• Replace the plain error / feedback strings in RuntimeCRs with structured data (e.g. JSON)
• Discuss within Framefrog and Gophers whether we should provude a library to standardised the processing of replied structured data easily (e.g. shared factory library for error messages etc.)

Reasons

Enhance error messages provided to KEB to improve UX in BTP Cockpit.

Attachments