Issues with mapped field from RP into HR Case form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 11:18 AM
We are facing an issue where we have mapped variable u_test_cause to the back end (HR Case form) from the record producer. When we submit the case through the portal, this field on the back end form does not capture the inputs from the record producer.
Yes, the names and values match on both sides, and yes the XML on the case form displays the value we selected on the portal, but it does not display it on the variable itself on the back end hr case form.
- Labels:
-
Human Resources Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 09:01 PM
you could try a few things
1. Impersonate as the same user who is doing from esc and see if tat user can update tat field from platform directly.
2. Write a log on record producer script to print the input entered to see if it is actually getting captured.
3. Are other fields getting populated correctly from record producer to HR case form.
4. Try to map any other field from record producer to this field by using the record producer script instead of direct field mapping and see if that updates that field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 09:12 PM
Hello @Dario Idrovo1
Check for UI policies or Client scripts present on that variable/field.
Are there any other variables in different form with same name?
check the ui policies if that variable is set to hidden.
Please mark the answer as helpful and correct if helped.
Kind Regards,
Ravi