Aller au contenu principal

Application Lifecycle Management d-t-p across different Portals

Terminée

Commentaires

1 commentaire

  • Cam Barnard

    Hi Brian,


    First, your use case is 100% valid, and one we've wrestled with how we might assist with.


    Unfortunately, it isn't as simple as being able to save your app config to a different place. Often a Geocortex Web application is made up of an app config, one or more referenced web maps and scenes, and possibly some workflows, report templates, and print templates. All these referenced items would need to exist in ArcGIS Online, and be properly wired up. We have a mechanism today that takes care of that in Designer with the application management (e.g. pushing from Dev to Prod) but this doesn't work across portals.


    We've done some preliminary proof-of-concept work around allowing the application management in Designer to work 'across portals'. For example. you may want your development and test versions on your Portal, but your Prod version in ArcGIS Online. It is a challenging problem, and we've been hoping that Esri will implement something to make it easier to connect information between an organization's Portal and their ArcGIS Online instance ... these are currently treated by Esri as two separate things (including not sharing authentication tokens) which makes it a tricky problem.

    0

Vous devez vous connecter pour laisser un commentaire.