- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2023 06:10 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2023 05:40 AM
The app publishing process really only applies to it moving to another instance. If you've built an app on your PDI it should already be usable. There is no concept of a "draft" app or publishing it in the same instance. Just start using it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 06:31 AM
Yes, I am using the below PDI,
https://dev113599.service-now.com/now/appenginestudio/my-apps/794c1ff61b7030109c726288b04bcbd3
I'm wondering that which admin we need to connect, I owned this PID and created the APP. But not able to add the user or raise the incident.
I am not able to see the error while submitting it. Which development pipeline we need to built up here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2021 06:19 AM
The pipelines in a PDI won't work because you only have one PDI. If you need to move an app to another instance you can open it in Studio (not AES) and commit it to git or publish it to an update set and move that to the other instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2023 06:19 AM
Hi Brad, what if this issue occurs outside of a PDI? I am experiencing this issue in a real mainline stack that has AES licenses.