ATF test fails to find Complete button on Problem form with UI action not defined errorSummary During an ATF test run, the test fails to find the Complete button on the Problem form and returns the error: FAILURE: UI action not defined in the step. This occurs when the sys_ui_action record for the Complete button is in a different domain than the one the impersonating user belongs to, or when the ATF step is referencing the wrong sys_id for the Complete UI action. Release All supported releases Instructions Follow these steps to identify and resolve the domain mismatch causing the ATF failure. Open the Problem form in the browser and right-click the Complete button. Select Inspect to open the developer tools Elements panel.Locate the sys_id of the Complete button in the element markup. Note this value.Navigate to the sys_ui_action table and search for the record using the sys_id identified in step 2. Observe the domain of the sys_ui_action record. Compare it to the domain of the user being impersonated during the ATF test run.If the domains do not match — for example, the impersonating user belongs to domain TOP/R-AT/RIT but the Complete button sys_ui_action record is in global scope — the ATF step will not be able to locate the button, producing the FAILURE: UI action not defined in the step error.Create or locate a sys_ui_action record for the Complete button within the domain that the impersonating user can access (for example, TOP/R-AT/RIT). Use the sys_id of that correctly scoped record in the ATF test step. Update the ATF test step to reference the sys_id of the correctly scoped Complete button sys_ui_action record, then re-run the test to confirm the error is resolved.