metasfresh - procurement audit #12600
Conversation
| @NonNull Object content; | ||
| @Nullable String eventUUID; | ||
| @Nullable String relatedEventUUID; | ||
| @Nullable IHostIdentifier host; |
There was a problem hiding this comment.
i think it would make sense to also have a property for indicating the service on which the "in" or "out" happened (app or webapi).
Then we could also use this for intra-metasfresh-auditing.
There was a problem hiding this comment.
also, we might add a "status", like success, warning or error..and in the case of error we might have an AD_Issue_ID
| } | ||
| catch (final JsonProcessingException e) | ||
| { | ||
| logger.warn("Failed converting `{}` to JSON. Returning toString().", content, e); |
There was a problem hiding this comment.
here, instead of cluttering the console, we might ceate the entry with status="Warn" and an ad_issue
| } | ||
| catch (final Exception ex) | ||
| { | ||
| logger.warn("Failed converting message to JSON: {}. Returning toString().", message, ex); |
There was a problem hiding this comment.
here we could again create an ad_issue and create the record with status="Warn"
| { | ||
| return; | ||
| } | ||
|
|
||
| final PutBPartnersRequest syncBPartnersRequest = PutBPartnersRequest.of(syncBPartner); | ||
| agent.syncBPartners(syncBPartnersRequest); |
There was a problem hiding this comment.
we should record this in the export audit log, and make sure to have a reference between it and the RabbitMQ_Message_Audit record
Audit on metasfresh side
Audit on procurement side