Will it be a problem if we create new field on sn_customerservice_task under Scoped application

[Supriya25]

Hi ,

my CSM application is fully scoped application ABCD . x_i<app_name>.abcd   ,    under this scoped application 10+ Major tables created, extended sn_customerservie_case

when I create fields on sn_customerservice_task
table : sn_customerservice_task 
Application : Customer Service
new field: Due Date of Claim , field name coming as. "u_due_date_of_claim "


table : sn_customerservice_task 
Application : Scoped Application
new field : Due Date of Claim , field name coming as  "x_i<app_name>_due_date_of_claim ".

Will it be a problem if I create fields on sn_customerservice_task under Scoped application (x_i<app_name>),  field name coming as  "x_i<app_name>_due_date_of_claim " . Is it best practice . Or it is bad practice ?

[YaswanthKurre]

HI @Supriya25 ,

It will not be a problem, please follow below recommendations:

• If  you need to extend sn_customerservice_task, it's okay to add scoped fields like x_abcd_due_date_of_claim.
•  Document these fields well and ensure your team knows they are scoped fields on a global table.
• Alternative: Consider creating a custom extension table of sn_customerservice_task in your scoped app and add fields there. This keeps your fields isolated and avoids modifying the global table directly.

Please mark this as helpful/correct, if this helps you.

Thanks,

Yaswanth

[Supriya25]

Hi @YaswanthKurre ,
Thanks your reply.

We are not going to creating a custom extension table of "sn_customerservice_task " . Just going to create new fields on "sn_customerservice_task" . 

CSM scoped application (x_i<app_name>.abcd) each custom table record has multiple csm-task (sn_customerservice_task) records  .

NOW we got requirement like create 25+ new fields in sn_customerservice_task table and add them on  sn_customerservice_task form Layout level.   Now kindly help me which application I have to take while crating those 25+ new fields  on sn_customerservice_task table  ? under CSM (scoped application (x_i<app_name>.abcd) ) Or "Customer Service" ? because sn_customerservice_task belongs to "Customer Service" OOB application .

Please advise me best practice here how the things works.

[YaswanthKurre]

hi @Supriya25 ,

Since sn_customerservice_task belongs to the Customer Service Management (CSM) OOB application, modifying it directly poses risks during upgrades (customizations in OOB tables can be overwritten). Instead:

• Create the 25+ new fields in your CSM Scoped Application (e.g., x_i<app_name>.abcd).
• Directly modify the sn_customerservice_task table within your scoped app to avoid conflicts with OOB updates.

So, you can add your fields in custom scope and maintain accordingly.

Thanks,

Yaswanth

[Supriya25]

Exactly Yashwanth, I don't want to see any issue in future upgrades and patch updates. that's why I want to learn and earn knowledge from you peoples on this purticuar things in best practice way.

yesterday when we got request like 25+ custom new fields to be created on sn_customerservice_task, there I got stuck. how to deal this  ? that's why Particularly I want know this,  sn_customerservice_task is OOB Table, and sn_customerservice_task designed & belongs "Customer Service" OOB Application.

• Create the 25+ new fields in your CSM Scoped Application (e.g., x_i<app_name>.abcd) on  sn_customerservice_task table. 
  OR
• Create the 25+ new fields in your "Customer Service" application on  sn_customerservice_task table. 

Please correct me if my understand is wrong here. So   Creating the 25+ new fields in my CSM Scoped Application (e.g., x_i<app_name>.abcd) on  sn_customerservice_task table is best practice/advisable method. like below 

table : sn_customerservice_task 
Application : Scoped Application x_i<app_name>.abcd)
New custom field : Due Date of Claim , field name coming as  "x_i<app_name>.abcd_due_date_of_claim ".