Hi Brad,

Ok. I think I understand. Once you've built it, it's ready for us locally. So, we can just ignore the launch, approve, submit part.

By the way, I'm enjoying your videos and blogs!

For those that haven't seem them : https://community.servicenow.com/community?id=community_blog&sys_id=e2f91736db5f6090fa192183ca96192e

Regards,

Rick

Hello Brad,

Thank you for the information provided in this community article. 

I am facing the same issue where I am not able to submit the application I developed using App Engine Studio because I use a PDI. 

But my purpose is to create a custom workspace - where a particular set of incidents, requests, changes can be viewed by a specific group in ServiceNow. Only this group should have access to this workspace. How can I achieve this if I am not able to submit my application in AES ? 

Regards,

Gopi

Submitting the application is all about moving it to another instance so that doesn't affect who can access the app in your current instance. You should be able to use the workspace security settings to limit who can access the workspace within your PDI.

If this is an experience you're planning on deploying eventually to a production environment, you should really be working on the development in the development instance associated with that production environment. If not you'll likely run into some scoping issues. The purpose of PDIs is learning and testing.

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.