Scoped applications - best practices

marclindsay · ‎01-13-2023

working on setting up FSO Insurance model / Claims. With these are existing scope applications, at the same time we will be creating new Case tables & Service Definitions extending from the core FSO Insurance case tables.

Question, should we be doing this in the existing commercial claims scope application that ServiceNow provides, or should we create a new Scope Application and put our new tables and customizations in this New Scope Application?

Thanks

Marc....

kmohammed · ‎01-13-2023

When setting up an FSO Insurance model/Claims in ServiceNow, it is important to consider the scope of your customizations and how they will interact with existing applications.

Here are a few things to consider when deciding whether to use an existing scope application or create a new one:

Reusability: If your customizations are specific to the FSO Insurance model/Claims and will not be used in other areas of the platform, it may be best to create a new scope application. This will keep the customizations specific to this use case and will make it easier to maintain and upgrade in the future.
Interoperability: If your customizations will interact with other applications in the platform, it may be better to use an existing scope application. This will ensure that your customizations are compatible with other applications and will make it easier to integrate with other features.
Security: If you are creating custom tables and service definitions, it is important to consider the security implications of these customizations. You may need to create a new scope application to ensure that your customizations are secure and are not exposed to potential security risks.

Ultimately, the decision of whether to use an existing scope application or create a new one depends on the specific requirements and use cases of your FSO Insurance model/Claims. It's recommended to work with a ServiceNow consultant to evaluate your specific use case and determine the best course of action.

View solution in original post

kmohammed · ‎01-13-2023

When setting up an FSO Insurance model/Claims in ServiceNow, it is important to consider the scope of your customizations and how they will interact with existing applications.

Here are a few things to consider when deciding whether to use an existing scope application or create a new one:

Reusability: If your customizations are specific to the FSO Insurance model/Claims and will not be used in other areas of the platform, it may be best to create a new scope application. This will keep the customizations specific to this use case and will make it easier to maintain and upgrade in the future.
Interoperability: If your customizations will interact with other applications in the platform, it may be better to use an existing scope application. This will ensure that your customizations are compatible with other applications and will make it easier to integrate with other features.
Security: If you are creating custom tables and service definitions, it is important to consider the security implications of these customizations. You may need to create a new scope application to ensure that your customizations are secure and are not exposed to potential security risks.

Ultimately, the decision of whether to use an existing scope application or create a new one depends on the specific requirements and use cases of your FSO Insurance model/Claims. It's recommended to work with a ServiceNow consultant to evaluate your specific use case and determine the best course of action.