Capture User Details as part of a User Action

How-to Guide

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.

Steps

Step 1: Manifest fragment change

Girish Padmanabha

Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.

Capture User Details as part of a User Action

Key Points

Steps

Step 1: Manifest fragment change

Girish Padmanabha

Building Blocks

By Type

Helpful Resources