This form has not been configured for Workspace. To edit the form, select a different type of record, or contact your administrator.

mattgr
Kilo Guru

HI All, 

We have upgraded out DEV instance to Madrid this weekend and I wanted to configure Agent Workspace to see how it works. When I added Lists, links to new records, ect I have noticed that I can't populate fields and I go the below message:

 

This form has not been configured for Workspace. To edit the form, select a different type of record, or contact your administrator.

 

find_real_file.png

 

Any idea on how to make this form available for Agent Workspace?

1 ACCEPTED SOLUTION

Alberto Consonn
ServiceNow Employee
ServiceNow Employee

Hi,

please ensure to Activate the Agent Workspace for ITSM plugin (com.snc.agent_workspace.itsm) to get the functionality of Agent Workspace for ITSM.

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

View solution in original post

18 REPLIES 18

alexanderk
Tera Contributor

I had the same error message described above for an own created workspace.

None of the described suggestions helped on my side.

 

What fixed the issue at the end:

  1. Open the View you create for the workspace in system ui -> views.
  2. Configure the Form Layout of system UI views and add Workspace View rule
    find_real_file.png
  3. Enter the Name of your workspace, the table the workspace is for and the name of the workspace like this:
    find_real_file.png

This immediately fixed my issue and the correct view was used in the workspace.

It seems the system did not know which view to use when opening a record on my workspace. The workspace view rule achieves exactly that. 

Elton Thomas
Kilo Contributor

If anyone is still having issues with this, try creating a new workspace view rule. See my short video for step-by-step instructions. Note, in the video I applied this in global; if you are developing an app to publish then you will want to do this in your app instead of global.

 

Hope this helps!

 

https://www.youtube.com/watch?v=mUibfrDUX6U

 

Runjay Patel
Giga Sage

Learn Agent Workspace from scratch to end with real world implementation and get live project hands-on.

Step by Steps implementation: https://www.youtube.com/playlist?list=PLIGcZxQaeEoj0XXBqTfReQwR44OeDYYb0

This Series help you to understand below topics

  1. How to setup Agent Workspace
  2. Plugins required.
  3. Create Studio application for Agent Workspace.
  4. Lading Page configuration in details.
  5. List Layout and Categories configuration.
  6. Form Layout, Header and Ribbon configuration
  7. UI Actions and notifications.
  8. Global search and Agent assist.
  9. Live Agent chat configurations.
  10. Integrate Connect Support with Agent Workspace
  11. Difference between Agent Workspace and ITSM Agent Workspace?
  12. Custom form for app: UI page, service portal widget or Agent Workspace component?
  13. View and Create Reports in Agent Workspace
  14. For LIVE AGENT where the service desk can access to the chat in back-end? via AGENT WORKSPACE OR CONNECT SUPPORT
  15. Agent Workspace - convert incidents to Request Items and vice-versa
  16. Add Knowledge search in Agent Workspace to Contextual form
  17. UI Action to pop up Email from Agent Workspace
  18. Bar Graph
  19. Open frame API in Agent Workspace
  20. How to use Assignment workbench in Agent Workspace?
  21. Viewing Interaction Records in Agent Workspace
  22. Agent Chat in Service Portal without Virtual Agent
  23. And many more.

K M
Kilo Explorer

Hello,

I have the opposite requirement. There are OOB tables which are part of the workspace view but I do not want users to be able to use them.

 

e.g. I want the banner "This form has not been configured for Workspace" to show up if a user opens a problem record in the workspace.

 

Best Regards.