Creating interactions in Agent Workspace

jcmings
Mega Sage

I'm confused by the process to create interactions in Agent Workspace -- why do I have to enter the subject user (opened for user) twice? The way the form is laid out does not make any sense. Right now, the process is as follows:

 

  1. Click Create Interaction
  2. Verify the employee in the interaction (enter the subject person's name), and click Next
  3. Provide the interaction details, and click Create Interaction 
  4. The interaction gets created, but it is not associated whatsoever with the person from step 2. Therefore, I have to verify the employee in the interaction again.

What's up with that? Is the person entered in my step #2 stored anywhere, so that I can auto-populate the "Opened for" field in step #4? This process is not intuitive at all.

1 ACCEPTED SOLUTION

jcmings
Mega Sage

If anyone runs into this issue in the future, for some reason, the solution is to add the Opened for field to the CSM Workspace view on the Interaction record.

View solution in original post

5 REPLIES 5

michaelj_sherid
ServiceNow Employee
ServiceNow Employee

@jcmings What family build and version are you on?  When I search the employee then provide the details (i.e. Type, Short Description & Work Notes) when the Create Interaction button is clicked, the interaction is created with the same user, I do not have to validate, reselect or search again.  I can see their details in the At a Glance section as well.

 

Regards,

Mike 

Hi @michaelj_sheridI just installed AW (for HR Case Management) 2.0.1. I'm in Tokyo Patch 9 but will be upgrading this environment to Utah in the coming weeks. My next sub-prod environment (which I'll be deploying to even sooner) is Utah Patch 4. Do you suspect this will be a non-issue in my next sub-prod environment?

@jcmings You should not see this issue on your Tokyo build either. I feel there is something else going on. This is not how it functions OOtB (what you are seeing). I recommend submitting a Hi case to investigate as to why you are seeing this in your instance.

 

Regards,

Mike

@michaelj_sherid Thanks - will do. I'll provide an update here when I get one!