OFBiz › OFBiz - Dev

[jira] Created: (OFBIZ-1643) Screens to manage Leads in SFA webapp

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

34 messages Options

Nicolas Malin (Jira)

[jira] Created: (OFBIZ-1643) Screens to manage Leads in SFA webapp

Screens to manage Leads in SFA webapp
-------------------------------------

Key: OFBIZ-1643
URL: https://issues.apache.org/jira/browse/OFBIZ-1643
Project: OFBiz
Issue Type: New Feature
Reporter: Anil K Patel
Priority: Minor

Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.

The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
• Find Lead
• Accessed from the application/header level "Leads" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by leads the current user is associated with unless the user has permission to view all
• Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
• Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
• Lead Home (Summary)
• This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
• Create/Edit Lead
• If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
• Contact Mechs (Contact Info)
• Work Efforts (Activities/Events and Tasks)
• Opportunities
• Campaigns
• Teams (Team)
• Notes
• Convert Lead to Account/Contact
• Merge Leads
• Clone Lead
• Import Leads (formats?)
• Automatic Lead Assignment Rules (constraints?)
• Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569621#action_12569621 ]

Anil K Patel commented on OFBIZ-1643:
-------------------------------------

PartyDataSource table links Party (Lead) to the DataSource (Lead Source).

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569622#action_12569622 ]

Anil K Patel commented on OFBIZ-1643:
-------------------------------------

Which entity is used to link Party (Lead) with Marketing Campaign?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569642#action_12569642 ]

David E. Jones commented on OFBIZ-1643:
---------------------------------------

For the Party (Lead) and MarketingCampaign: what is the usage scenario/story for this? In other words, what would the association be used for? The catch-all entity for this is the "MarketingCampaignRole" entity, and then it's just a matter of using the appropriate RoleType to describe the relationship.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Issue Comment Edited: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569723#action_12569723 ]

anilpatel edited comment on OFBIZ-1643 at 2/17/08 9:16 AM:
--------------------------------------------------------------

From what I understand, Some times, Lead we get is from a MarketingCampaign we had. So I thought it will be good to relate Lead with MarketingCampaign, may be its another way to analyze success of Campaign.

was (Author: anilpatel):
From what I understand, Some times, Lead we get is from a MarketingCampaign we had.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569723#action_12569723 ]

Anil K Patel commented on OFBIZ-1643:
-------------------------------------

From what I understand, Some times, Lead we get is from a MarketingCampaign we had.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570106#action_12570106 ]

David E. Jones commented on OFBIZ-1643:
---------------------------------------

Yes, that makes sense. A lead party could be associated using the MarketingCampaignRole using the lead RoleType to model this.

If the requirements around associating leads to campaigns become too much more complex at some point we might want to move those to a new entity. For now though I can't think of any such complexities, so the generic M-C-Role entity mentioned above should do the trick just fine.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576457#action_12576457 ]

Sumit Pandit commented on OFBIZ-1643:
-------------------------------------

Fields that should include in create / edit lead form : -
1) Lead Source : Data source
2) Lead Source Description :
3) Lead Campaign : *******
4) Status : need to create data for it like :-
StatusType statusTypeId="LEAD_STTS" description="lead"
StatusItem sequenceId="01" statusCode="NEW" statusId="LEAD_NEW" statusTypeId="LEAD_STTS" description="New"
StatusItem sequenceId="02" statusCode="ASSIGNED" statusId="LEAD_ASSIGNED" statusTypeId="LEAD_STTS" description="Assigned"
StatusItem sequenceId="03" statusCode="IN_PROCESS" statusId="LEAD_IN_PROCESS" statusTypeId="LEAD_STTS" description="In_Process"
StatusItem sequenceId="04" statusCode="CONVERTED" statusId="LEAD_CONVERTED" statusTypeId="LEAD_STTS" description="Converted"
StatusItem sequenceId="05" statusCode="RECYCLED" statusId="LEAD_RECYCLED" statusTypeId="LEAD_STTS" description="Recycled"
StatusItem sequenceId="06" statusCode="DEAD" statusId="LEAD_DEAD" statusTypeId="LEAD_STTS" description="Dead"

5) Status Description
6) Referred By : partyLookup
7) First name
8) Last name
9) Account Name
10) Department
11) Team
12) AssignTo : PartyLookup
13) phone : office Country Code Area Code Phone Number ext Allow Solicitation?
14) Phone : Home Country Code Area Code Phone Number ext Allow Solicitation?
15) Phone : Other Country Code Area Code Phone Number ext Allow Solicitation?
16) Fax Number Country Code Area Code Phone Number ext Allow Solicitation?
17) Email Address
18) Address : Primary
Mailing/Shipping Address
Address 1 Required
Address 2
City Required
State Required
Zip/Postal Code Required
Country Required
Allow Address Solicitation?
19) Address : other
Mailing/Shipping Address
Address 1 Required
Address 2
City Required
State Required
Zip/Postal Code Required
Country Required
Allow Address Solicitation?
Steps for create/edit lead :
20 ) Description Information.

There are all fields according to my view. Parimal has start working on it. Do some one suggest more fields. If yes it will be very help full for us.

Thanks.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Assigned: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anil K Patel reassigned OFBIZ-1643:
-----------------------------------

Assignee: Ashish Vijaywargiya

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

parimal gain updated OFBIZ-1643:
--------------------------------

Attachment: SfaLead.patch

The attached patch contains the code for create and find lead but the problem occured during find by firstName and lastName on findLead and couldn't save fields that are unreachable for me like-
status
refferedBy
team
assignTo
accountName
on createLead

suggest me how i can find by firstName and lastName
and where i can save the fields

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579009#action_12579009 ]

Anil K Patel commented on OFBIZ-1643:
-------------------------------------

Parimal, Please use camelCase for variable naming.

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579034#action_12579034 ]

Jacques Le Roux commented on OFBIZ-1643:
----------------------------------------

For any new contribuitors, please be sure to read http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices

Thanks

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588602#action_12588602 ]

Mridul Pathak commented on OFBIZ-1643:
--------------------------------------

From the description given here what I understand is:
A lead can either be a Person or Party Group. That means we can either create a Lead Person or a Lead Group. And associate any Lead Person to a Lead group.
So should we have create two different forms to create Lead Person and Lead Group?

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592308#action_12592308 ]

Mridul Pathak commented on OFBIZ-1643:
--------------------------------------

I am working on this issue. Will post a patch in not more than two days.

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592331#action_12592331 ]

Mridul Pathak commented on OFBIZ-1643:
--------------------------------------

Should we add a new dataResourceTypeId = "LEAD_SOURCE" for creating PartyDataResource records for Lead Source?

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Pathak updated OFBIZ-1643:
---------------------------------

Attachment: Sfa_Lead_26-04-08.patch

Here is the patch for this issue. This patch also contains general simple methods to create Person/PartyGroup, Role and ContactMechs in partymgr. These simple methods will be used by Lead, Accounts and Contact in SFA.
Thanks to Jyotsna, Ratnesh and Brajesh for their help and efforts.

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: Sfa_Lead_26-04-08.patch, SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Assigned: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: Sfa_Lead_26-04-08.patch, SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Closed: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anil K Patel closed OFBIZ-1643.
-------------------------------

Resolution: Fixed

Thanks Mridul Pathak and others who helped. Patch is in rev 651848.

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: Sfa_Lead_26-04-08.patch, SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Reopened: (OFBIZ-1643) Screens to manage Leads in SFA webapp

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker reopened OFBIZ-1643:
--------------------------------

can you please have a look at the implementation list?

many thngs are not yet implemented like the conversion to contact/account copy/clone etc etc

> Screens to manage Leads in SFA webapp
> -------------------------------------
>
> Key: OFBIZ-1643
> URL: https://issues.apache.org/jira/browse/OFBIZ-1643
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: Sfa_Lead_26-04-08.patch, SfaLead.patch, SfaLead.patch
>
>
> Lead is both a Person and PartyGroup (related by a PartyRelationship) because much of the information in a lead translates directly into Account and Contact information and this way the Lead records can either be duplicated, or simply modified adding the Account and Contact roles. For the Person and Party-Group parties will be in the Lead role.
> The following are screens and details for them related to a lead. These may be best as separate screens or as desired certain ones can be combined.
> • Find Lead
> • Accessed from the application/header level "Leads" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by leads the current user is associated with unless the user has permission to view all
> • Like the normal Party Search except with a filter on partyTypeId=PARTY_GROUP or PERSON and include a PartyRole record for the "LEAD" roleTypeId; may also constrain by existing PartyRelationship to join the Lead Group to the Lead Person.
> • Includes a link to the Create/Edit Lead page with no "partyId" to identify the account for the purpose of creating a new lead; note that for Edit Lead the partyId can correspond to either the Group or Person
> • Lead Home (Summary)
> • This page will include summary information for the account including basic lead fields plus other related information (to be defined....)
> • Create/Edit Lead
> • If a "partyId" parameter is passed in this page will act as an Edit Lead page (the partyId can for the Group or Person), if not it will act as a Create Lead page (both being very similar)
> • Contact Mechs (Contact Info)
> • Work Efforts (Activities/Events and Tasks)
> • Opportunities
> • Campaigns
> • Teams (Team)
> • Notes
> • Convert Lead to Account/Contact
> • Merge Leads
> • Clone Lead
> • Import Leads (formats?)
> • Automatic Lead Assignment Rules (constraints?)
> • Capture Leads from Web Site (ecommerce or other public facing)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.