ATF Test Steps Script execution step view is hidden

[Denielle Pamint]

I am trying to use the OOB Test Steps that ServiceNow has created as reference for the custom test steps that I am planning to run, is there any way to unhide the Script execution step in the form?

EDIT: Especially for the "Server" category test steps. It seems like all of the steps coming from this category have a hidden Script editor.

Thank you!

[larralapid]

When the “Script Execution” step’s script field is hidden in Automated Test Framework (ATF), it’s usually due to:

---

✅ 1.

Step Configuration (Step Config vs Test Step)

Make sure you’re editing the test step, not just referencing a pre-configured Step Config. Sometimes the script is defined at the Step Config level and locked at the test level.

🔍 Try:

• Opening the test step directly.

• Checking if the script field is editable in that context.

---

✅ 2.

ACLs or UI Policies

It’s also possible a UI Policy or ACL is hiding the Script field based on your role or the test type.

📌 Check:

• Table: sys_atf_step

• Field: script

• ACL: sys_security_acl table (filter for object = sys_atf_step.script)

• UI Policy: Any policy triggered when step_config.name = “Script Execution”

---

✅ 3.

Form Layout or View Issues

If you’re using a custom form layout or non-default view, the field might not be on the form.

📎 Navigate to:

Test Step record → Form Layout

Ensure the Script field is added to the form view.

[Denielle Pamint]

Thank you for your response.
Steps done to test if I can see / access the script written in the Script execution editor.
1. Deactivated the sys_atf_step_config.step_execution_generator in the sys_security_acl table after elavating admin role to Security Admin

3. Updated the UI Policy with a 'Visibility=True' for the Script execution step (step_execution_generator) field in the form default view.

I was able to unhide the editor but it is empty. Refer to the attached file.