The value of 'Requested for' field on RITM changes from 'Opened by' user to 'Requested for' variable value, how to avoid seeing this change in value in the audit historyIssue When a catalog item is submitted with 'Requested for' variable set to different user, we can see that 'Requested For' on the RITM is temporarily set to the user who submits the request (opened by) and later it changes to the user specified in 'Requested for' variable . How to avoid seeing this change in value in the audit history. CauseThe OOB behavior is when an item is submitted, the 'Requested For' field will be set to the user who submits the request irrespective of the value specified in the 'Requested for' variable. In this instance, the logic to copy the variable value is defined inside the workflow which is the reason why we are seeing the change in value in the audit history.ResolutionTo avoid seeing this change in value, we can create a before insert business rule on 'sc_req_item' table where the logic to copy the variable value can be defined, instead of doing it inside the workflow. This way the field value is set during creation time itself.