IAR for HR not working

ge3
Tera Expert

Issue Auto-Resolution (IAR) for sn_hr_core_case records continuously unassigns bot from target record due to AI Search not finding results.

 

After setting up IAR for HR on sn_hr_core_case on GI as HR service, upon submission of case from portal, the HR bot is assigned to the case for a second and unassigns immediately, What else needs to be configured?

1 ACCEPTED SOLUTION

1. Can you make this system property true "com.glide.cs.notification_newuser_webclient "

2. Can you change requester from Opened for to Subject person

Shruti_0-1730089083751.png

 

View solution in original post

10 REPLIES 10

Are you trying in PDI? IAR won't work in PDI's

 

Can you assign both admin and sn_hr_core.admin role to HR BOT user

Make sure short description is removed from predicted fields

While submitting general inquiry request please enter "request for leave", or "download a policy document" keywords

No i am on my client instance plus org instance which i newly installed IAR but HRSD is already installed. Still no success in adding roles to hr bot.

 

Here's my current config:

Screenshot 2024-10-25 at 7.53.33 PM.png

Screenshot 2024-10-25 at 7.53.46 PM.png

Screenshot 2024-10-25 at 7.54.03 PM.png

Screenshot 2024-10-25 at 7.54.36 PM.png

ge3
Tera Expert

No valid user for AI Search,Intent prediction service is not enabled for this task - this is another error i am getting.

1. Can you make this system property true "com.glide.cs.notification_newuser_webclient "

2. Can you change requester from Opened for to Subject person

Shruti_0-1730089083751.png

 

I think I got it to work. Wondering why Opened for is not working? I did a few customization to get this to work including the predicted fields. 

 

Now i am getting recommendation links with incorrect URL (hrportal_default when it should just be hrportal) for KBs and catalogue pages that won't open. Where do I change the links of the recommended articles/catalogues?

 

Also, in the conversation passed onto the case, the links are not accessible (security constraints) - see screenshot below.

Screenshot 2024-11-01 at 12.10.51 AM.png