ER Case Requested for profile details Should Not be update while transfer the case to other service
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2025 08:14 AM
I Don't want to update the requested for profile details if any latest updates happen on HR profile while transfer the case to other services. Auto populate field should remain same as existing case, on Transferring case How to fix this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2025 03:54 PM
Hi There; In HRSD, when a case is transferred to another service, the Requested For profile is re-evaluated, so any recent updates to the HR profile can automatically populate on the new case.
If you want the values to remain exactly as they were on the original case, you’ll need to break that live dependency.
Supported approaches:
Store the required “Requested For” values in case-specific fields (copied at case creation/transfer) instead of referencing the HR profile directly.
Use a Business Rule on transfer to copy the existing values from the original case to the new case and prevent re-syncing.
Avoid using live reference lookups to the HR profile for fields that must remain static per case.
Summary:
HR profile data is designed to stay current, so preserving historical values requires copying them to the case at the time of transfer rather than continuing to reference the profile.
Hope this helps clarify the behavior.
@MUDIGOLAM BHANU - Please give a Thumbs up if you find Helpful!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2025 11:24 PM
Hi @Matthew_13 ,
Thanks for the reply,
Having before insert BR when new Case is getting created those auto populate action is required. Without effecting above BR how to restrict without any changes while transferring case, How we can achieve with script? any sample script might be helpful.
Thanks in advance!,
Thanks,
Bhanu.
