- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2022 07:04 AM
We have facing one issue- when a user submitted their HR case on wrong HR Service, or COE case, so we like to transfer to correct COE case. I read some posts and ServiceNow release documents- know current ServiceNow release has HR transfer feature, but somehow it doesn't work for us. Please advise.
Solved! Go to Solution.
- Labels:
-
Multiple Versions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2022 07:49 AM
You can create and use methods to reclassify or transfer an opened HR case from one HR service to another.
The reclassify method is that the HR case number does not change after transferring an HR case from one HR service to another with linking redirect to the new case. However Standard method is that the HR case number changes when transferring an HR case from one HR service to another. Both HR case numbers appear on the HR case for reference
Please following configure steps:
- Activate “Transfer Case” UI action, which is “false” in default.
- Ensure the following 3 the existing script includes are “Active”
- hr_TransferCase
- ReclassifyCaseTransfer
- StandardCaseTransfer
You can perform you HR case transfer following steps:
Please mark my answer as useful if it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2025 01:33 PM
Hi John (and anyone else),
Great post! Definitely gave a thumbs up! I have a related question that I am posting as a reply in case others on this thread face, are facing, or have faced a similar issue. Definitely can post as a separate thread if that's a better approach.
We are using the Reclassify option for Transfer Case, which has been working fine. However, we recently introduced a new Category and Subcategory attribute on sn_hr_core_case. When we have an HR service for a very specific inquiry/request (i.e., Dental Benefits Inquiry), we are using an HR Template to set Category to Benefits and dependent Subcategory to Dental. We then use a UI policy to lock Category and if applicable, Subcategory, based upon HR Service so that the categoricals matches the HR service for data quality. For our swiss army knife, General HR Inquiry, we leave the Category and Subcategory fields as always editable.
The issue I am running into is when someone tries to transfer a Dental Benefits Inquiry (i.e., locked down Cat = Benefits and Subcat = Dental) to a Vision Benefits Inquiry (i.e., should be locked down Cat = Benefits, and Subcat = Vision) because the wrong HR Service was chosen, it does not look like the HR Template fires on the newly reclassified-to case, now with the original case number. It continues to show Subcategory = Dental despite the HR Service being Vision Benefits Inquiry (e.g., Subcategory should be Vision).
Is my assumption correct that HR Templates don't fire on a transfer as reclassify? If they do not, do you have a recommendation as to how to handle wanting to force set certain values as outlined above? I have considered ignoring the fields via sn_hr_core.transfer_case.ignored_fields and setting my UI policy so it doesn't lock down a field for editing until there's a value in it, but I could still end up with bad data. I am also exploring extending the HR service record with a default value for Category and Subcategory when applicable -- instead of using HR Templates to set the value. There has to be a better way...
Thanks in advance for any suggestions provided.
Shawn

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2022 12:46 PM
Hi Pece,
Can you describe in more detail what part does not work for you? Does it work if you are part of the assignment group? Or does transfer case never work?
/Markus
Markus Nilsson
+46709389974