I have a relatively simple catalog item where the "Requested For" on the REQ and associated RITM are relying on the default value in those tables (there is no option for the end user to select the Requested For). For each of these tables, the default value is dynamic using the "Sender" dynamic filter, which corresponds to gs.getUserID();. In almost every REQ/RITM record for this catalog item, the Requested For is appropriately recorded as the end user submitting the catalog item. However, I have 1 record where the Requested For is not the name of the user submitting the catalog item. In this case, the Requested For and Opened By are different users, with the person listed in the Opened By being the actual end user. There does not seem to be any business rules setting the Requested For and from what I can tell, it is only being set based on the dynamic default value.
Has anyone experienced this where gs.getUserID() is not evaluating to the current user? Is there perhaps a script include or somewhere else I should be looking to see how the Requested For value is being set if it is not relying on the default value? We are pretty much out-of-box for our Service Catalog and have not made any changes to business rules, client scripts, or UI scripts that would affect this field.
