AnsweredAssumed Answered

Filter for unassigned Cases

Question asked by Kristjan Geir Mathiesen on Dec 4, 2018
Latest reply on Dec 12, 2018 by Kristjan Geir Mathiesen

Like • Show 0 Likes0
Comment • 13

Hi good people!

I´m setting up another inbound email handler that will create sales related Cases.

I need to be able to identify those sales related Cases from other brake-fix Cases so I can make a filter for those employee´s attending only to those sales related Cases.

I was going to filter on the unassigned until I remembered that we only have two options there:

I don´t seem to be able to set any fields in the inbound email handlers :/ Any ideas how I could solve this use case?

Thanks in advance,

KGM

Kristjan Geir Mathiesen Dec 12, 2018 6:32 PM

Correct Answer

Hi Björn Canales Pfisterer

I´ve got a solution, part of it from Dennis Wangerin and then three logic hooks:

1. In Studio > Cases module create two calculated text fields:

- related_email_c calculated with formula: related($emails,"to_addrs_names")

- is_assigned_c calculated with formula: greaterThan(strlen(toString(related($assigned_user_link,"last_name"))),0)

( or any other required field in users that can be used to check if a user exists)

2. Add the two text fields to Studio > Cases > Layouts > Search ( And to recordview to test )

3. Either import a new email to create a case, or resave an existing case to confirm the values populate to the two fields

4. In Cases listview create two new filters:

- related_email_c - exactly matches: <sales emailaddress>

- is_assigned_c -exactly matches: false

5. Logic hook for changing Teams on the Case

6. Logic hooks for changing Teams on the associated email

Thanks again everyone,

KGM

See the reply in context

No one else had this question

Outcomes

13 Replies

B_Canales Dec 4, 2018 12:19 PM
Mark Correct
Correct Answer
Hi Kristjan Geir Mathiesen,

this might also interest Zac Sprackett as he answeared to this thread some days ago: "Unexpected values found in emails" when upgrading to 8.0

FYI: Kristján and I discussed this topic separately in Skype and I'm aware the original quetion is about unassigned cases but the issue we have on this is the same.

--

In my experience, setting up several queues based on multiple imports from "role based" email inboxes might be tricky and as far as I know can't be done by out of the box abilities.

Let's say we have an international support team with own local email adresses and also a sales department per subsidary. Here we need to set up multiple inbound email records.

The issues we are facing here is the team assignment. If we set up a team per job, the case AND attached email got only those teams set, which means everyone who is not be supposed to be in the assignment group will never see the case or its attached email.

Due to advanced workflows criteria does not have access to teams of a current record or the email module, we can't create workarounds with adv. workflows.

For now the only solution is a logic hook which for sure does the trick but is not a good solution for me as a CRM consultant.

I would like to see at least the following enhancements which can be build in easily I think:

1. Adding the possibility on "Inbound email" to add a distribution team additionaly to the a teamset for visibility
2. Adding the possibility on "Inbound email" to set a value to the standard "source" dropdown list for flagging the source the case comes from. Not a beautifuly solution but it will work.
3. *Bling bling* solution: have access to all fields incl. custom fields to set on automatic case creation per "inbound email" configuration.

This might be a quick win and would solve alot until a new cases solution will be released in later versions.

Bests

Björn Canales Pfisterer
Technical Support Manager

provalida GmbH
1 person found this helpful
Like • Show 0 Likes0
Actions
- Kristjan Geir Mathiesen @ B_Canales on Dec 4, 2018 12:22 PM
  Mark Correct
  Correct Answer
  Thanks Björn Canales Pfisterer for this.
  
  Yes, it would be awesome to be able to tag the Cases in the Inbound Email config - even if it was just a Tag. That would make it possible to identify which Cases came from which Inbound Email handler. Definitely an enhancement request Or allow the advanced workflow to use Teams on the record for criteria
  
  Thanks,
  KGM
  Like • Show 1 Like1
  Actions
Kristjan Geir Mathiesen Dec 5, 2018 6:18 AM
Mark Correct
Correct Answer
Anyone else have an idea?

Thanks,
KGM
Like • Show 0 Likes0
Actions
Patrick McQueen Dec 5, 2018 10:24 AM
Mark Correct
Correct Answer
Hi Kristjan Geir Mathiesen,

The goal as I understand it (please correct me if I have misunderstood):
- Two Inbound Email group accounts create Cases for two distinct groups: sales and techSupport
- The created case will round-robin to all members of the specified team, but self-service is desired.
- sales and techSupport Regular-type users can only see records assigned to a team they are on, so they won't have access to cases or emails not in round-robin assignment to them (distribution vs visibility).
- Advanced Workflow cannot access the Emails module to evaluate fields and make field changes.
- Logic hooks are not the desired solution for some consultants and clients.
I agree that the above goal is not 100% achievable using only features available in the application. A logic hook is needed for at least one simple part of this, as described below.

My brainstorm idea:
1. Create/specify a user to own all new cases for each team. Cases owned by this user are considered unassigned.
2. Create a team for only this one user
3. In the Inbound Email Group Account settings, set this team to the "Assign To Teams" so all cases go to this user.
4. Create an Advanced Workflow Process Definition that appends the appropriate team(s) to the new case so now those other Regular Users can search for and see the cases.
5. (This is the one part the application features cannot currently do) A logic hook fires for the case after step 4, updating the related email's team set to match the Case so now those other Regular Users can see the email(s).
6. Implement the Cases filter on Assigned To equals the user in step 1 so the team can find and self-service assign the cases.
I appreciate that this does not satisfy all of the parameters of the goal as it does use a logic hook, but I hope it is helpful to the discussion.
Like • Show 2 Likes2
Actions
- Kristjan Geir Mathiesen @ Patrick McQueen on Dec 5, 2018 2:18 PM
  Mark Correct
  Correct Answer
  Hey Patrick McQueen
  
  Yes, pretty much like you said except in this particular use case, the sales and techSupport have the same visibility (teams). The core of this challenge is: identify unassigned cases that come from the sales mail handler (even if standard Sugar would offer "is empty" option for the "Assignee" field in the filter, it still would not cut it since we don´t know from which mail handler the Case comes from). Hope I am making myself understandable
  
  I´m having trouble with the gmail account at the moment but it seem´s that with Cases are not being assigned to my Group user, that is the only one in the Team that gets assigned via Round Robin :/
  
  Yes, I´m working on a after_save Logic Hook that populates a filed that I can then show in the search to filter on.
  
  Thanks,
  KGM
  Like • Show 0 Likes0
  Actions
  - sugar.dennis @ Kristjan Geir Mathiesen on Dec 6, 2018 6:33 AM
    Mark Correct
    Correct Answer
    Hi Kristjan Geir Mathiesen,
    
    I have been spinning this is my mind for a bit and I think you can get to it with calculated fields.
    
    1. In Studio > Cases module create two calculated text fields:
       - related_email_c calculated with formula: related($emails,"to_addrs_names")
       - is_assigned_c calculated with formula: greaterThan(strlen(toString(related($assigned_user_link,"last_name"))),0)
       ( or any other required field in users that can be used to check if a user exists)
    2. Add the two text fields to Studio > Cases > Layouts > Search ( And to recordview to test )
    3. Either import a new email to create a case, or resave an existing case to confirm the values populate to the two fields
    4. In Cases listview create two new filters:
       - related_email_c - exactly matches: <sales emailaddress>
       - is_assigned_c -exactly matches: false
    
    In my tests this allowed to show any cases created from email to a certain account with no assigned user.
    
    Would that work for you?
    
    Thanks,
    Dennis
    
    // Edit: would be more elegant to use a dropdown for the is_assigned_c field so you can select false as a filter
    1 person found this helpful
    Like • Show 2 Likes2
    Actions
    - B_Canales @ sugar.dennis on Dec 6, 2018 6:56 AM
      Mark Correct
      Correct Answer
      Hi Dennis,
      
      good thinking!
      
      Am I right that "to_addrs_names" pointing to the 'to_addrs" field in the email_text table? On the imported email there can be more than one email address , also saved in different formats like:
      
      support@mydomain.de, Mr Boss <mrboss@mydomain.de>
      
      or
      
      Support <support@mydomain.de>, mrboss@mydomain.de
      
      So the filter should at least use another operator than "starts with" or "exactly matches" but this also needs a custom operator on text fields, right? My concern is that some cases will never be touched due to this.
      
      //Edit: and when we implement a custom operator we should do this for the assigned user ^^
      
      Bests
      
      Björn Canales Pfisterer
      Technical Support Manager
      
      provalida GmbH
      Like • Show 0 Likes0
      Actions
      - sugar.dennis @ B_Canales on Dec 7, 2018 7:02 AM
        Mark Correct
        Correct Answer
        That is a valid point Björn Canales Pfisterer, to cover this usecase the following approach would work:
        
        For related_email_c instead of getting the related address, check if it contains a relevant address with the following formula ( obviously can be extended to check against more addresses or what to do when both addresses are in the To (or CC) Recipients:
        
        ifElse(contains(related($emails,"to_addrs_names"),"sales@example.com"),"Sales","Support")
        
        With that when the To-Field contains the Sales address the field shows "Sales". Again add this and the is_assigned_c field to the search Layouts in studio. Then you can add a listview filter to for all Cases where related emails contain the Sales address and are unassigned.
        2 people found this helpful
        Like • Show 2 Likes2
        Actions
        B_Canales @ sugar.dennis on Dec 7, 2018 7:20 AM
        Mark Correct
        Correct Answer
        Awesome Dennis Wangerin !
        
        Thank you for that! Sometimes I need to remind myself more often about what is possible with Sugarlogic
        
        Have a nice weekend!
        
        Bests
        
        Björn
        Like • Show 0 Likes0
        Actions
        Kristjan Geir Mathiesen @ sugar.dennis on Dec 7, 2018 8:58 AM
        Mark Correct
        Correct Answer
        Thanks Patrick McQueen, Björn Canales Pfisterer and Dennis Wangerin for your inputs.
        I´ve implemented logic hook and workflow:
              Logic hook to populate a custom field (that I then use in the filter)
              Workflow to change the Team on the Case.
        I was going to do another workflow for Emails but now I see that´s not an option. So I´m still stuck with wrong Team on the email :/ I´ll have to try to do another logic hook for that.
        Thanks,
        KGM
        Like • Show 1 Like1
        Actions
        B_Canales @ Kristjan Geir Mathiesen on Dec 7, 2018 12:13 PM
        Mark Correct
        Correct Answer
        Hey Kristján,
        
        I saw that comming so back to my initial post
        
        Björn Canales Pfisterer wrote:
        
        1. Adding the possibility on "Inbound email" to add a distribution team additionaly to the teamset for visibility
        2. Adding the possibility on "Inbound email" to set a value to the standard "source" dropdown list for flagging the source the case comes from. Not a beautifuly solution but it will work.
        
        Using Teams for assigning cases AND assigning teams to records in one option is the major issue here and I think that can be fixed by Sugar quickly in the next release by adding a second option :-)
        
        Kveðjur
        Björn
        Like • Show 1 Like1
        Actions
        Kristjan Geir Mathiesen @ B_Canales on Dec 12, 2018 6:32 PM
        Unmark Correct
        Correct Answer
        Hi Björn Canales Pfisterer
        
        I´ve got a solution, part of it from Dennis Wangerin and then three logic hooks:
        1. In Studio > Cases module create two calculated text fields:
           - related_email_c calculated with formula: related($emails,"to_addrs_names")
           - is_assigned_c calculated with formula: greaterThan(strlen(toString(related($assigned_user_link,"last_name"))),0)
           ( or any other required field in users that can be used to check if a user exists)
        2. Add the two text fields to Studio > Cases > Layouts > Search ( And to recordview to test )
        3. Either import a new email to create a case, or resave an existing case to confirm the values populate to the two fields
        4. In Cases listview create two new filters:
           - related_email_c - exactly matches: <sales emailaddress>
           - is_assigned_c -exactly matches: false
        5. Logic hook for changing Teams on the Case
        6. Logic hooks for changing Teams on the associated email
        
        Thanks again everyone,
        KGM
        Like • Show 0 Likes0
        Actions
Greg Barrass Dec 5, 2018 4:40 PM
Mark Correct
Correct Answer
Our Case Creation Email Handler assigns cases to a New Case Team of which there are no members (this gets around the Round Robin/Least Busy limitation). In our situation we don't need a Sales and a Service team so we don't use multiple Case Creation Email Handlers but our solution would still work if that was the case - we would just have multiple empty teams (New Sales Case Team, New Service case Team etc).

All new Cases get a status of New automatically.

Because only Administrators would be able to see those Cases and linked emails, we have a Legacy Workflow (because Advanced can't do this) that changes the Team to the "real" team - in our case we use Global, but it could be whatever valid team is needed (e.g. Sales Team, Service Team etc). That would require multiple Legacy Workflows - one for each New Case Team.

We now can run reports or do list enquiries on Cases with a Status of New for the Service Team (or Sales team etc to determine unassigned cases.) When we assign a Case to a specified user, we change the status to Assigned, but we could have Legacy workflow do that if we wanted.

I hope this is of help.

I agree that there are two functional problems that cause all of us to have to find workarounds:

1. The Least Busy/ Round Robin assignment is not necessarily suitable for many of us.

2. Advanced Workflow is not where we need it to be to handle things ike this and so we have to fall back to Legacy Workflow

Hopefully SugarCRM press ahead with a significantly improved Customer Self Service Portal as we really want to move around from email based Case creation but that is not easy to do with the functional limitations of the current portal.

Regards
Greg Barrass
3 people found this helpful
Like • Show 1 Like1
Actions

Filter for unassigned Cases

Outcomes

Related Content

Recommended Content