Hello Brad,

I agree, but to see the workspace, is it required to submit the application ?

Because when I search for the workspace I created in the "Workspace Experience > Administration > All Workspaces", I am unable to find the new workspace I created. I am concerned if I am missing any steps so as to make the workspace available. 

Thanks,

Gopi

The submittal process is all about moving the application up the instance stack and should not affect whether someone in the existing instance can see a workspace. 

I would try adding your workspace to the unified nav menu if you have the next experience ui turned on. If not you may have to create an application menu module for it.

Hi Brad, 

I found out another way to implement my requirement. 

My requirement is to create a custom workspace - where a particular set of incidents, requests, changes can be viewed by a specific group in ServiceNow. 

But I believe I don't have to go for a custom workspace for this, instead I can create a new page to the agent workspace and make this new page as default landing page only to the users part of this group. 

Is it possible to do this according to you ? Any pointers you could share on the above mentioned ?

Thanks,

Gopi

If you want a workspace for incidents for ITSM I would try to use the Service Operations Workspace we shipped via the store in the San Diego release. 

Agent workspaces are a legacy product at this point and not nearly as configurable and customizable as the individual configurable workspaces.

Hello Brad,

Sorry for waking up this post after so many years but recently I'm dealing with this very problem of getting pipeline errors in AES when I try to publish the app. I already understood from your previous reply that we were not able to publish any apps on PDIs, but is there any way to run an app that we designed on AES on aPDI, so that we can get some experience with using it? Thanks.