Ensure we populate data that somehow were not set (performedBy for example)

[arealmaas]

Introduksjon

Example: If we fail to fetch data from registries when populating performedBy on an activity if not present, we should not fail the request, but we should ensure that we in a near future update this data when the registry is available again.

Beskrivelse

Related issue: #387

Implementasjon

TODO: Spec out an implementation here.

Rough draft:

• If request fails, add a message on the the service bus
• In the body of the message, indicate what should be done.

Message:

{
      "orgNumber":"qr23r2",
      "activityId": "qr23r2",
      "event": "PopulateData",
      "type": "PopulatePerformedBy"
 }

Oppgaver

Preview Give feedback

1. Implementasjonsoppgaver legges inn her
2. Utarbeide dokumentasjon (hvis relevant - enten oppdatere arbeidsdokument, eller legg inn ny fil i docs)
3. Legge inn e2e-test (hvis relevant)

Akseptansekriterier

GITT that we want to store data from third party systems
NÅR the data fetch from these third party systems fail
SÅ the system should:

• Complete the request without the data being set.
• Log a warning indicating the failure.
• Ensure we refetch this data asynchronously and store it

[elsand]

As far as I can tell, the only case where this is relevant is handling actor name lookups in relation to the seen log. For all other cases, including performedBy in activity, failing the lookup should also fail the dialog create/update command, avoiding a state where the name is missing.

Closing this.