App Engine Studio: cannot submit application for approval

[_calvinr]

Hello and thanks for reading.

Using the App Engine Studio feature, I am unable to submit my application for approval after completing all of the tasks. This issue is persistent across users, including the super-user "System Administrator" account.

After completing the build of tables for data, experiences for catalog items and portal, building automation pipelines, adding security permissions, the submission button remains greyed out with the message:

"there was an error while retrieving your application deployment information. Contact your admin in order to submit your app."

Doesn't matter if I base my application on a template or if I build everything from scratch. This is the forth app I've tried to build today, so eager to hear any ideas.

edit: adding link I've been referring to throughout the process

https://docs.servicenow.com/bundle/quebec-application-development/page/build/app-engine-studio/task/...

[Gopi22]

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

[Brad Tilton]

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.

[Gopi22]

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

[Brad Tilton]

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.

[Gopi22]

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