Stream: implementers
Topic: AuditEvent for operations
Ariadna Roman (May 06 2019 at 10:41):
In the case of executing an operation that implies multiple actions, how should an AuditEvent be mapped so that it contains for each resource that has been modified the corresponding action?
Example: Let's say we have an operation that: updates a Schedule and creates multiple Slots. How can we map that the Schedule was UPDATED and the slots were CREATED? Can the field "detail" of Entity be used to this purpose?
Grahame Grieve (May 06 2019 at 10:42):
I would expect that you would have multiple entities in this case, with different roles on the different resources
Ariadna Roman (May 06 2019 at 11:00):
And how can we present the action (create, update, delete) that was executed on each resource using the roles?
Grahame Grieve (May 06 2019 at 11:21):
life cycle looks appropriate to me
Ariadna Roman (May 06 2019 at 11:30):
Got it! Thank you!
John Moehrke (May 06 2019 at 13:47):
I would expect that you just record one auditEvent describing the Operation. It is known what the operation does, so it doesn't seem important to record each micro-activity.
Last updated: Apr 12 2022 at 19:14 UTC
