Registered App For Web with Printing
Répondu
This app contains references to items stored in different portals or items that use a different Registered App for signing in. Deploying is not supported in this scenario.
-
Doesn't seem to have an issue tied into Workflows that are in the app.
0 -
Ted Cronin ... This is when trying to deploy your app in app designer (i.e. from Dev > Prod).
Have a quick read through:
https://docs.vertigisstudio.com/webviewer/latest/admin-help/Default.htm#gwv/deploy-an-app.htm
Most often something like this occurs because Designer is trying to access the same Esri portal using two different security app items (i.e. you've configured Web Designer to use one app item for security and Printing to use a different app item for security). If you can't figure it out after poking at it, suggest you open a support ticket and get them to walk you through it.
0 -
Cam Barnard
I am seeing this same issue after upgrading to Web 5.18.1, Workflow 5.28.1, and Printing 5.18 where all of my URLs changed from '.../Geocortex/WebViewer/...' to '.../VertigisStudio/Web/...', etc.
I am only getting errors though on my server workflows and my print templates. These items previously had to be shared with 'Everyone' to bypass all security checks and allow users to access them - other than that there is no difference between those items and the other workflows in my viewer. I am not certain if that sharing requirement still exists in the latest versions of Workflow and Printing. However, changing the sharing settings of my workflows does not have any affect on whether I receive the deployment errors.
My client side workflows appear to be just fine, even though they use the same Portal item for authentication as my server workflows and print templates. I am indeed using a separate Portal item for authentication of Web as this was the recommended architecture when I initially implemented our environment.
Thanks,
Brian
0 -
Cam Barnard, I'm struggling to deploy an app with a Server WF in it (nested in a client one), and am getting this "references to items stored in different portals " error unless I remove the call to that server-side workflow entirely. Am I supposed to be able to do that, or are the server workflows not supported? I tried making the server WF public, unfortunately to no avail. Web and WF Designers do have separate items for Portal authentication, should I consider updating that? Like Brian Cunningham, my client workflows deploy without issue.
If you have an idea or a reference for me to review before making a support ticket, I'd like to have a crack at things before going to support.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires