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

You can still take an app developed in AES, open it in studio, and export or connect to git as you would normally would. You just can't use AES to move an app in a PDI because PDIs are not connected to an app repo.

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