What is the best practice around scope for new feature development

[Fred Jean]

Hello,

When implementing new features that are (a bit) related to a scoped application, but would not actually touch objects of that application, I am wondering what would be the best practice.
For instance let's say we have the HAM plugin and we want to create a new Catalog item with a bespoke flow working with Asset records, this could also involve some Business Rules; we have similar OotB flows that are in the HAM scope.

Should we :

• Do it in Global scope ?
• Do it in the scope of the existing application ? (for my example "Hardware Asset Management" or may be "Asset Management Common" ?)
• Create a new scoped application ?

[Community Alums]

Hi @Fred Jean ,

Please follow a basic thumb rule that, if it's a scoped application then all the Business rules, client Scripts, flows, etc should be built under that particular scope ONLY. You should not touch Global Scope.

[Fred Jean]

Hello @Community Alums 

You say " if it's a scoped application", well that's a bit the question; is it (should it be) a scoped app ? And if so should it be an existing one (and if so, should be "Hardware Asset Management" or "Asset Management Common" as some existing OotB flows are in "Hardware Asset Management" and others in "Asset Management Common")
So for we have nothing implemented related to these needs, so I'm wondering where they belong.

[Community Alums]

Hi @Fred Jean ,

Yes, it's an existing Scoped App.

[Fred Jean]

When you say "it", are talking about our additional features (Flow and catalog item) ?

are saying this is (actually should be) part of an existing scoped app and not a new one ? If so what is the reason for saying that and how do you choose which scope it would then be part of ?