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

[Nicolas Malin (Jira)]

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

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

Hans,
Thanks. We'll get to them asap.

> 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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: Sfa_Lead_12-05-08

modified implementation of createLead service.

> 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_12-05-08, 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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment:     (was: Sfa_Lead_12-05-08)

> 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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: Sfa_Lead_12-05-08.patch

> 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_12-05-08.patch, 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)]

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

Vikas Mayur commented on OFBIZ-1643:
------------------------------------

Thanks Jyotsna,

Your patch is in trunk rev.655499

-
Vikas

> 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_12-05-08.patch, 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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: SfaCloneLead.patch

This patch is for Clone Lead functionality for SFA Lead.
It also includes some bug fixes.

> 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_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: SfaCloneLead.patch

> 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_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.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)]

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

Vikas Mayur commented on OFBIZ-1643:
------------------------------------

Thanks Jyotsna,

Your patch for Clone Lead Functionality is in trunk rev. 657104

- Vikas

> 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_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: SfaMergeLeads.patch

This patch contains implementation of Merge Lead for SFA Lead.
Also created data for lead statuses and modified create lead service and convert lead service accordingly.

Mridul thanks for your help.

> 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_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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)]

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

Vikas Mayur commented on OFBIZ-1643:
------------------------------------

Thanks Jyotsna,

Your patch for Merge Lead functionality is in trunk rev. 658118

- Vikas

> 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_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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)]

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

Jyotsna Rathore updated OFBIZ-1643:
-----------------------------------

    Attachment: importLead.patch

Uploaded patch (importLead.patch) for implementation of import Lead from vCard.

> 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: importLead.patch, Sfa_Lead_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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)]

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

Vikas Mayur commented on OFBIZ-1643:
------------------------------------

Thanks Jyotsna and others,

Patch (importLead.patch) is in trunk rev. 659489.

- Vikas

> 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: importLead.patch, Sfa_Lead_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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)]

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

Marco Risaliti updated OFBIZ-1643:
----------------------------------

    Component/s: marketing

> 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
>          Components: marketing
>            Reporter: Anil K Patel
>            Assignee: Anil K Patel
>            Priority: Minor
>         Attachments: importLead.patch, Sfa_Lead_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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)]

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

Vikas Mayur closed OFBIZ-1643.
------------------------------

       Resolution: Fixed
    Fix Version/s: SVN trunk

All remaining issues can be added as a sub-task under https://issues.apache.org/jira/browse/OFBIZ-2363

> 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
>          Components: marketing
>            Reporter: Anil K Patel
>            Assignee: Anil K Patel
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: importLead.patch, Sfa_Lead_12-05-08.patch, Sfa_Lead_26-04-08.patch, SfaCloneLead.patch, SfaCloneLead.patch, SfaLead.patch, SfaLead.patch, SfaMergeLeads.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.