mirror of
https://github.com/SuiteCRM/SuiteCRM.git
synced 2026-03-02 19:16:58 -05:00
Prospects and ProspectLists not available through the V8 modules API #4493
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#4493
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 @shaung999 on GitHub (Mar 1, 2021).
Issue
I need to query a target (Prospect) by email as a response to a campaign, however, it seems there is no access to Prospects or ProspectList API, when I issue a {suite.url}/V8/meta/modules request neither Prospects (Targets) nor ProspectLists (Target lists) are returned in the available modules.
Expected Behavior
I should be able to interact with Prospects in the same way I can with Leads or Contacts.
Actual Behavior
Nothing as the modules are not available
Possible Fix
My first assumption was that the this was an ACL issue as the module appeared in the $moduleList, however, after step by step debugging through the whole process I found that that actual issue was the $modInvisList (also in globals) contained both Prospects and ProspectLists (and a number of other modules), which implies at some point it was decided not to include these, by removing both of these from the $modInvisList they became available and during my testing (mainly create, search and get) they seem to function exactly as Leads and Contacts.
I am raising this bug report so that I can provide a hot-fix for review but also (as I am very new to this product) to ensure that I have not missed something fundamental.
Steps to Reproduce
Any call to {suite.url}/V8/meta/modules.
Please see this link for the full commentary on the issue
Context
I am using my workaround until this is updated as I have an extremely complex target management process that runs across a number of different systems, so for me personally this was a V. HIGH requirement, but for the general use I guess this would be MEDIUM
Your Environment
@rmetcalf9 commented on GitHub (Dec 6, 2023):
I want to be able to add a lead to a target list via the api as well.
@chris001 commented on GitHub (Dec 6, 2023):
Normally, when a Prospect responds to a Campaign, you convert (upgrade) that Prospect to a Lead.
@rmetcalf9 commented on GitHub (Dec 7, 2023):
Yes, after bashing my head against a brick wall looking for an API I found that I could use SuiteCRM workflow to automatically add new leads to target lists. I was able to put descriptions into the lead record and have the workflow trigger on the description and add to the right target list.
Very annoying but it forced me to learn the suiteCRM workflow feature which is very powerful and easy to use.
Still, the functionality should be in an API.