Inbound emails from someone NOT apart of the HR Case

Rob Sestito · ‎04-10-2019

Hey there SN Comm!!

I am looking to see what (if at all), others might be doing when it comes to allowing people that do not have access to view a Case/are not part of a Case - to be able to email into a Case.

Example:

recently we had a Case that was for one person, and they were the Requestor and Subject Person and Opened By (because they emailed into the system). The assigned to person of this Case, needed to reach out to the Requestor's manager. They did so, via emailing them from the Case itself. The manager then replied to that email from the Case. However, since they are not apart of the Case, and not in any assignment group from the system, their reply never reached the actual Case. It was ignored.

I reached out to SN with a HI Case because I was confused at first. I thought that if someone gets emailed from the actual Case, they would be able to reply and their reply would be posted to the Case. SN however, said that since the person being emailed does not have access to the Case (or apart of the Case in any way), that they cannot post anything to the Case - which includes their emails.

I then as a test, added that manager to the watch list, reprocessed their email, and it was posted to the Case.

We do not want to make this a thing, where we keep adding people to watch list, just to allow them to reply back to a Case when they are not actually involved in the Case.

First, does anyone out there know of this issue/scenario? Second, if you know about this, has anyone built anything as a work around? Is there something that can be done for this?

My initial thought was to create an addition field that is like the watch list field, but tie NO Out going emails like the watch list does. The watch list currently sends out emails for work noted AND additional comments, which we do not want. Especially when it is with someone not technically involved in the Case. But just reached out for additional information.

Thanks in advance!

-Rob

Rob Sestito · ‎04-16-2019

Hey John,

So yeah - seems like I needed to add the correct .addOrCondition line within the Restrict Query Business Rule. I tested with a few different tables that I am using this new field on within our HR Cases (COEs). Sure enough, each time I added the dummy account to the new field and sent my email in, the email posted. Once I removed the dummy account from the field, sent in another email, the email was blocked from being posted to the Case. It is a bit strange that the Business Rule would control all of that access, but I guess it does make sense when we really think about it. I was sure that I needed a new ACL, or at least had to modify an OOTB one (as provided by asifnoor). Then we went through also modifying the Include Script. But, turns out it was not needed. But I am glad we went through it, as I definitely learned a lot!

So, here is what was needed for the access:

Modify the OOTB Business Rule 'Restrict Query', with the new field I created (which is a List Field with a reference qualifier)

Here is my new field as a reference:

I hope this helps you, and anyone else - as this entire post has helped me!

Cheers!!

-Rob

View solution in original post

Rob Sestito · ‎04-16-2019

also, had a random question.

Within the script include we are messing with, could we do anything like this:

asifnoor · ‎04-16-2019

Yes, that should work.

Just that we are changing their code, but since its a separate block, you can try that once.

Rob Sestito · ‎04-16-2019

Meh!

Nothing seems to be working with this 😞

Kiel Sanders · ‎04-16-2019

Have you tried temporarily disabling the Restrict query business rule and processing the email again to see if you receive the same errors? I think that's why you are receiving the unable to locate the record errors.

Rob Sestito · ‎04-16-2019

Hey Kiel,

So I first tried to see if I could add in a .addOrCondition for the new field - however still did not work. Then, I went ahead and disabled the BR like you suggested, and yes - the email then found the record and posted to the Case.

Would I be able to basically, put the Script Include and ACL back to what they were, disable this BR and be all set? I know it is NOT recommended to disable this BR in Prod.

What do you think?

Thanks,

-Rob