DOM manipulation techniques cause ATF failuresIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> DOM manipulation techniques for making fields read-only on a form can cause ATF failures. It causes ATF failure with error: Client request did not provide serialized form data. ReleaseAllCauseDOM manipulation is not advised in Servicenow, as it causes issues such as these. Read more in the product documentation: Avoid DOM Manipulation. Example: If we use a client script which contains the code with DOM Manipulation (.disabled=true;) to make field read-only, causes the parameters not to be able to get serialized from the form and It causes ATF failure with error: Client request did not provide serialized form data. var form = document.getElementById('change_request.do');if (form) {for (var x=0; x< form.elements.length; x++) {form.elements[x].disabled=true;}}ResolutionUse the supported API called GlideForm(g_form)