Is it best to create a new Service Portal in a scoped app?

[patricklatella]

Hi all,

we are getting ready to develop a new Service Portal...is it best practice to do the development for the new SP in a scoped app?

thanks!

[scott barnard1]

Hi Patrick

Personally unless I have a pressing need for a scoped app then I just put the portal in global and go oldskool and deploy with an update set.

You can go scoped app or use a git repo and put all the stuff in one place but your re-use will suffer a bit.

Portals are basically widget instances and pages.

So if you go scope You have to have a widget in that scope and then create an instance etc.

For example we have dozens of different business entities in different countries that use different portals.

Most of the widgets used are the same with the widget instances spawning from the centre. You get a change to a core widget and it cascades to all the portals instantly.

If you go scoped you have to maintain that widget environment separately.

The one thing I have noticed about portals is you think you only need 1 or 2 but they are prone to spring up everywhere once folk start using them

Regards

[patricklatella]

Thanks very much for the info Scott!  Sounds like the best way to go is to develop portals in Global scope.