My first thought is that after you set the value programmatically, you should trigger the change event for the field you altered to make sure it sticks.

$('.tag input').val("HIPAA").change();

My second thought is that I have had problems with read only fields not wanting to save values input programmatically. When working with read only fields I usually:

• remove the read-only attribute
• set the value
• trigger the change event
• set it back to read-only

Setting it to disabled instead of read-only on the Doc Control form might be causing issues, but I'm not 100% sure of that.

I use something like this to change the read-only state, with the first input being the element and the second input being a true/false.

function yourFunction(){
    //remove read-only
    setReadOnly($('your field'),false);
    
    //set value
    //trigger change event

    //make read-only again
    setReadOnly($('your field'),true);
}

function setReadOnly(e,x){
    if(x){
        // Set input element to read-only
        e.attr({'readonly': 'readonly', 'backend-readonly': 'True'});
    } else {
        // Remove readonly from input element
        e.removeAttr('readonly backend-readonly');
    }
}

If that doesn't make a difference, I would add a line of code to each form to pop up a JavaScript alert with the current value of the fields when the form loads and/or when the field's change event is triggered. That way you can narrow down where in the process the value is getting lost.

If the value is passed back to the initiator form correctly, it is possible something in the code is changing it back to default (in my experience the change events for form fields tend to fire right after the form first loads).

Thanks for the feedback. Just got back from a few days vacation. For now, I removed the feature. If Doc Control needs that field changed, they'll have to reject back to initiator. However, now that you've provided some ideas, just might try them. Thanks. Will let you know how it goes.