Capture User Details as part of a User Action
How-to GuideStep-by-step guides to achieve a specific scenario or setup.
Author:
Girish Padmanabha
Changed on:
10 Apr 2024
Key Points
- Need to capture user details for critical actions like Order Cancellation in Fluent OMS or Store.
- An audit trail necessitates knowing which user performed an action.
- Ideally, the username should be available in Rubix event logs as "GeneratedBy," but currently only the user's first name is retrieved.
- As a workaround, acquiring user inputs via an OOTB API query called the "me" query. User details are then sent as part of the UserAction event.