Adam Bise Posted June 25, 2015 Report post Posted June 25, 2015 I wanted to know if there is a way to support a loose deployment of conflicting applications. Let's say I have app A, which conflicts with app B, and I want to publish them both as available for one collection. There is no requirement I can set on app B that says app A = not installed. (that I know of) I may look into creating a custom global condition but not sure how that works yet. I know I can always check for conflicting apps during an install script. I also know I can be more granular with my deployments, and deploy them to separate collections. But I am curious if anyone else has ran into this? If so, how did you work around it? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 25, 2015 Report post Posted June 25, 2015 I think in a scenario like that the granular deployment would be the obvious solution and if not possible I would look at global conditions to simply verify if the app is installed. Quote Share this post Link to post Share on other sites More sharing options...
