- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 01:45 PM
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:
- Click Create Interaction
- Verify the employee in the interaction (enter the subject person's name), and click Next
- Provide the interaction details, and click Create Interaction
- 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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 10:08 AM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 02:08 PM
@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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2023 06:12 AM
Hi @michaelj_sherid, I 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?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2023 06:20 AM
@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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2023 06:55 AM
@michaelj_sherid Thanks - will do. I'll provide an update here when I get one!