IS IT RECOMMENDED TO SHARE THE SERVICENOW MODULE ACROSS DIFFERENT TEAMS , ARE THERE ANY PITFALLS

[kudidi_anilkum1]

WE USE THE SIR MODULE IN SERVICENOW , ANOTHER TEAM WANT TO SHARE THE SAME MODULE , ARE THERE ANY KNOWN KNOWN PITFALLS , WHILE SHARING THE MODULE BETWEEN TWO TEAMS , WE MIGHT NEED TO HEAVY CUSTOMIZATIONS IN ORDER TO SET THE BOUNDARIES LIKE SEPARATING THE DATA AND ANY OTHER CONFIGURATIONS ON FORM LEVEL , SCRIPTS TO RUN ON BUSINESS RULES ETC....

[Asal Moezi]

Hello,

in order to separate your data, you can use Domain Seperation. However, module configurations and customizations will affect all domains, unless you find a way to base your customizations to also apply to only one domain. 

For example for form level differences you can create different Views or on Business Rules add the Domain to the BR condition. 
I hope this helps!

[Sohail Khilji]

Hi @kudidi_anilkum1 ,

I would say you would decide this sharing based on the business criticality, There will not be any major pitfalls unless you configure the application carefully considering the architecture of it. You can make use of domain sepration to seprate a data and process of the module. or elseyou can strongly customize the module but making use of ROLES, ACL, BR , Data filteration etc...

I hope the question is answered...