ServiceNow UI Action Missing in Workspace: Find Why, Fix It

Transcript

1. 0:00

   Here you're on an incident in Service Operations Workspace, and your team's own Escalate button, which works fine on the classic form, isn't anywhere in this header. You want it here too, working, without breaking the classic one.

2. 0:13

   So you open TorchTiger Engineer, a side panel for ServiceNow developers that reads your instance, and ask it why your button is missing from this page.

3. 0:22

   First it looks up your Escalate button on this instance, then reads how it's set up.

4. 0:26

   On the button's own record it finds what's wrong, a workspace setting that's switched off.

5. 0:31

   And it warns you that the classic script won't work there as written.

6. 0:34

   Then you ask it to bring Escalate here as well, without touching the classic form's button, its script, or who is allowed to see it.

7. 0:41

   Next it searches the web for how a workspace button is built, checks which app it's writing into, and drafts its plan.

8. 0:48

   Its plan keeps the same button and server code, and adds a script for the workspace.

9. 0:53

   Nothing is written until you approve, with Grant and Execute.

10. 0:57

    You press it, and it creates an update set for the work, then updates the Escalate button.

11. 1:03

    Reading the record back, it reports everything else as before, the classic script and condition included.

12. 1:08

    Now Escalate shows.

13. 1:10

    You click it, and it asks for a reason.

14. 1:13

    You type VIP caller and press OK.

15. 1:17

    Your reason is saved as a work note, so your own test shows Escalate working here too.

16. 1:22

    Try TorchTiger Engineer on your own dev instance, at torchtiger dot com.