Auto populate feature is erasing variable value after submit

[dvelloriy]

Hello All,

We have a catalog item with 2 reference variables. One variable is Manager and other is Director.

Manager is present in a variable set (auto populated by requested for's manager) and getting auto populated using below ref qual script:

javascript:new global.TaskUtils().GetActiveManagerList() + "^sys_id!=" + current.variables.requested_for;

Director is a separate variable.(auto populated with Manager's Manager) using auto-populate feature.

Screenshot below

When i create the request, i see both manager and director values getting auto populated, however when i submit the form, director value is erased.

Please assist.

[Brad Bowman]

I was asking about manually changing the value of the dependent question, then letting the new Director value auto-populate.  Come to think of it, I think the bug was if you did that it would auto-populate back to the dependent question relationship, but maybe it's the same or different bug.  Do you have a PDI or other instance on a later release that you can mockup to test the same? By manually changing the Director, you've eliminated any errant client scripts, UI Policies, or Business Rules since it isn't happening until/after submit.