I am, thank you for that clarity.

Would it be safe to suggest that the App Engine Studio provides no value to PDI? Is there nothing that I've developed here that can be used elsewhere in my PDI?

I don't think I would say that. Using AES allows you to create an app, data model, experiences, etc. more quickly than you could otherwise, especially with experiences as it can spin you up starter workspace and portal experiences you can't find anywhere else.

What is it you're looking to use AES for in your PDI?

I am trying to sell my leadership on building SNOW integrations for their customer data centers infrastructure.

I have this functionality working through traditional (Service Catalog / Item / Workflow) process, but decided to port my work efforts into AES after being prompted every time I login.

The submission aspect blocked the kick, but honestly Workflow wasn't very intuitive for issuing Scripts (trying to send a REST Message to an external API service). I was hoping to get the app submitted so that I could return to the workflow issues, but it seems that this is all for naught.

Perhaps I can find a way of using the Portal experience with my traditional approach

AES is really meant to be a low-code tool for building apps, so if your goal is to create integrations I wouldn't worry about doing it through AES.

Hi Brad,

I have this same issue. But I would like to develop apps in my PDI. I often use my PDI before moving to one of our Development instances. That way I can try new things and prepare for future development in isolation. Plus, our development instances are not yet at Quebec level. 

Is there a way around this error?

Regards,

Rick