mirror of
https://github.com/SuiteCRM/SuiteCRM.git
synced 2026-03-02 19:16:58 -05:00
Record Creation From Inbound Emails Missing #5169
Labels
No labels
Area: API
Area: Campaigns
Area: Cases
Area: Clean Up
Area: Clean Up: Performance
Area: Dashlets
Area: Databases
Area: Developer Tools
Area: Elasticsearch
Area: Elasticsearch
Area: Emails
Area: Emails:Campaigns
Area: Emails:Cases
Area: Emails:Compose
Area: Emails:Config
Area: Emails:Templates
Area: Environment
Area: Installation
Area: Language
Area: Mobile
Area: Module
Area: PDFs
Area: PHP8
Area: Reports
Area: Studio
Area: Styling
Area: Upgrading
Area: Workflow
Area:Activity Stream
Area:Calls
Area:Import
Area:Projects
Area:Search
Area:Surveys
Area:Themes
Area:Users
Branch:Hotfix
Good First Issue
Hacktoberfest
Help Wanted
PR:Community Contribution
PR:Type:Enhancement
Priority:Critical
Priority:Important
Priority:Moderate
Severity: Major
Severity: Minor
Severity: Moderate
Status: Requires Code Review
Status: Requires Updates
Status: Stale
Status: Team Investigating
Status:Assessed
Status:Fix Proposed
Status:Needs Assessed
Status:Requires Automated Tests
Type: Bug
Type:Deprecated
Type:Discussion
Type:Duplicate
Type:Invalid
Type:Question
Type:Suggestion
Type:Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SuiteCRM-SuiteCRM#5169
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pstevens71 on GitHub (Feb 20, 2024).
Issue
The issue is that if an email is already imported there are a whole bunch of other options in the ACTIONS menu like: Create Case, Create Bug, Create Lead... etc.

However, when an email is not imported yet, these options are missing (and would be super convenient!!!)
I found the problem. These two views use different viewdefs depending if the email has been imported or not. These button options are just missing from the non-imported email view.
Expected Behavior
I'd expect to see the same options on non-imported email as I do when I'm viewing an already imported email.
Actual Behavior
What actually happens is for non-imported emails this template is used instead: \modules\Emails\metadata\nonimporteddetailviewdefs.php which doesn't contain all the button options. It's almost like they are forgotten.
Possible Fix
The fix is easy, just copy in the button code to the nonimporteddetailviewdefs.php as well as the includes for the quickcreate:
@chris001 commented on GitHub (Feb 20, 2024):
Nice discovery! When you
Create Bug,Case,Contact,Lead,Opportunity, from a not-imported email, isn't that bad, because the email's sitting out at the mail server, it's not imported, so that means you don't have its contents/headers saved in thedbto refer back to later on when needed. You want the email to be imported to thedbwhen it's relevant enough to create these actionable CRM objects: a bug, case, contact, lead, or opportunity, right?@SuiteBot commented on GitHub (Feb 21, 2024):
This issue has been mentioned on SuiteCRM. There might be relevant details there:
https://community.suitecrm.com/t/suitecrm-email-client-how-to-create-any-record-lead-contact-etc-manually-directly-in-7-10-2/56212/11
@pstevens71 commented on GitHub (Feb 21, 2024):
Hey Chris, there are many use cases where you want to create the record first and then import it. For example, you get a referral ie; "company abc referred me to you, lets talk about xyz" What you really want to do is attach the email to a lead, but there is no lead yet. So you have to go and create a lead in the lead module, come back to email and then attach it. With this modification, you can now create the lead right from the inbox. Once the lead is created, it gives you the option to return to the email, which you can then import and attach to the lead. Not perfect, but way better. Ideally, the email would be imported and related to the record just created. I'm going to further investigate how hard it would be to hook into the import function at the same time and maybe do it all in one step.