You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Anil K Patel (JIRA)" <ji...@apache.org> on 2008/02/15 02:35:08 UTC
[jira] Created: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Screens to manage Contacts in SFA webapp
----------------------------------------
Key: OFBIZ-1642
URL: https://issues.apache.org/jira/browse/OFBIZ-1642
Project: OFBiz
Issue Type: New Feature
Reporter: Anil K Patel
Priority: Minor
In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
These may be best as separate screens or as desired certain ones can be combined.
Find Contact
• Accessed from the application/header level "Contacts" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by Contacts 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 "CONTACT" roleTypeId.
• Includes a link to the Create/Edit Contact page with no "partyId" to identify the account
for the purpose of creating a new Contact; note that for Edit Contact the
partyId can correspond to either the Group or Person
• Contact Home (Summary)
• This page will include summary information for the account including basic Contact
fields plus other related information (to be defined....)
• Will have link to and information about Account associated with contact; since this
is modeled as a PartyRelationship can theoretically have multiple Accounts but the
UI will limit the setup of a single Account per Contact.
• Create/Edit Contact
• If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "JyotsnaRathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JyotsnaRathore updated OFBIZ-1642:
----------------------------------
Attachment: SfaContact.patch
This patch also contains modifications related to viewprofile link in Lead.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "JyotsnaRathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JyotsnaRathore updated OFBIZ-1642:
----------------------------------
Attachment: (was: SfaContact.patch)
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Jyotsna Rathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jyotsna Rathore updated OFBIZ-1642:
-----------------------------------
Attachment: quickAdd.patch
updated patch with some cleanups.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: quickAdd.patch, quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Vikas Mayur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599388#action_12599388 ]
Vikas Mayur commented on OFBIZ-1642:
------------------------------------
Jyotsna, this patch looks fine but I would like to suggest few modifications in quick add functionality. These modifications are based on idea of using existing services like createLead and createContact for quick add.
1) Instead of creating new services for Lead and Contact, we can add an boolean attribute say quickAdd to these services.
2) This attribute can be passed from forms with appropriate values (like quickAdd = true for quick add forms and quickAdd = false for other forms)
3) In services createLead and createContact, add a conditional check on this parameter. If it is false than keep the process as it is and if it is true...
4) ... if it is true we need to create only (a) a person (b) a role (c) an email address. All these can be kept in a simple method which than can be called inline
in both services.
This way the code will be reduced and will be more cleaner, manageable.
Please let me know if this is doable.
- Vikas
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Marco Risaliti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Risaliti updated OFBIZ-1642:
----------------------------------
Component/s: marketing
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Components: marketing
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: quickAdd.patch, quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "JyotsnaRathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JyotsnaRathore updated OFBIZ-1642:
----------------------------------
Attachment: SFAContact.patch
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
> Attachments: SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Mridul Pathak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591589#action_12591589 ]
Mridul Pathak commented on OFBIZ-1642:
--------------------------------------
In Create Contact form, for now the most basic details that we can have are
1) Personal Details (firstName, lastName mandatory)
2) General Correspondence Address Details (mandatory)
3) Primary Phone details
4) Primary Email Address Details
5) An input and party lookup to create a party relationship record
We can allow user to add more details on the summary screen.
I'll update soon if we can have more details in the create form.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "JyotsnaRathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JyotsnaRathore updated OFBIZ-1642:
----------------------------------
Attachment: SFAContact.patch
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
> Attachments: SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Vikas Mayur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Mayur closed OFBIZ-1642.
------------------------------
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 Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Components: marketing
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: quickAdd.patch, quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Jyotsna Rathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jyotsna Rathore updated OFBIZ-1642:
-----------------------------------
Attachment: quickAdd.patch
Uploaded patch(quickAdd) for quick add contact and quick add lead functionality.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Anil K Patel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593500#action_12593500 ]
Anil K Patel commented on OFBIZ-1642:
-------------------------------------
Jyotsna Rathore, Thanks for your help. Patch is in rev # 652443
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
> Attachments: SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "JyotsnaRathore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JyotsnaRathore updated OFBIZ-1642:
----------------------------------
Attachment: SFAContact.patch
Done minor changes in the profile page and few cleanups in the code.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
> Attachments: SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Anil K Patel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anil K Patel updated OFBIZ-1642:
--------------------------------
Description:
In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
These may be best as separate screens or as desired certain ones can be combined.
Find Contact
• Accessed from the application/header level "Contacts" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by Contacts 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 "CONTACT" roleTypeId.
• Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
• Contact Home (Summary)
• This page will include summary information for the account including basic Contact
fields plus other related information (to be defined....)
• Will have link to and information about Account associated with contact; since this
is modeled as a PartyRelationship can theoretically have multiple Accounts but the
UI will limit the setup of a single Account per Contact.
• Create/Edit Contact
• If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
partyId can for the Group
was:
In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
These may be best as separate screens or as desired certain ones can be combined.
Find Contact
• Accessed from the application/header level "Contacts" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by Contacts 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 "CONTACT" roleTypeId.
• Includes a link to the Create/Edit Contact page with no "partyId" to identify the account
for the purpose of creating a new Contact; note that for Edit Contact the
partyId can correspond to either the Group or Person
• Contact Home (Summary)
• This page will include summary information for the account including basic Contact
fields plus other related information (to be defined....)
• Will have link to and information about Account associated with contact; since this
is modeled as a PartyRelationship can theoretically have multiple Accounts but the
UI will limit the setup of a single Account per Contact.
• Create/Edit Contact
• If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
partyId can for the Group
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Anil K Patel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anil K Patel reassigned OFBIZ-1642:
-----------------------------------
Assignee: Anil K Patel (was: Vikas Mayur)
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Mridul Pathak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591586#action_12591586 ]
Mridul Pathak commented on OFBIZ-1642:
--------------------------------------
In the find form we can have a drop-down for partyTypeId, displaying only two options, "PERSON" and "PARTY_GROUP", which will allow user to filter results by any of these two partyTypeId's.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Mridul Pathak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592307#action_12592307 ]
Mridul Pathak commented on OFBIZ-1642:
--------------------------------------
I am working on this issue.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Anil K Patel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593146#action_12593146 ]
Anil K Patel commented on OFBIZ-1642:
-------------------------------------
Jyotsna Rathore, Committed your patch in svn rev#652167. There are lots of other things remaining so we'll keep this issue open. Thanks for help.
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
> Attachments: SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Vikas Mayur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Mayur reassigned OFBIZ-1642:
----------------------------------
Assignee: Vikas Mayur
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Vikas Mayur
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Anil K Patel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anil K Patel updated OFBIZ-1642:
--------------------------------
Description:
In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
These may be best as separate screens or as desired certain ones can be combined.
Find Contact
• Accessed from the application/header level "Contacts" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
• Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
• Contact Home (Summary)
• This page will include summary information for the account including basic Contact
fields plus other related information (to be defined....)
• Will have link to and information about Account associated with contact; since this
is modeled as a PartyRelationship can theoretically have multiple Accounts but the
UI will limit the setup of a single Account per Contact.
• Create/Edit Contact
• If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
partyId can for the Group
was:
In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
These may be best as separate screens or as desired certain ones can be combined.
Find Contact
• Accessed from the application/header level "Contacts" tab
• Includes a search fields entry form and a search results display form
• All search results will be filtered by Contacts 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 "CONTACT" roleTypeId.
• Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
• Contact Home (Summary)
• This page will include summary information for the account including basic Contact
fields plus other related information (to be defined....)
• Will have link to and information about Account associated with contact; since this
is modeled as a PartyRelationship can theoretically have multiple Accounts but the
UI will limit the setup of a single Account per Contact.
• Create/Edit Contact
• If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
partyId can for the Group
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Priority: Minor
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1642) Screens to manage Contacts in SFA
webapp
Posted by "Vikas Mayur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599596#action_12599596 ]
Vikas Mayur commented on OFBIZ-1642:
------------------------------------
Thanks Jyotsna and others,
Patch (quickAdd.patch) for quick add functionality is in trunk rev. 659822.
- Vikas
> Screens to manage Contacts in SFA webapp
> ----------------------------------------
>
> Key: OFBIZ-1642
> URL: https://issues.apache.org/jira/browse/OFBIZ-1642
> Project: OFBiz
> Issue Type: New Feature
> Reporter: Anil K Patel
> Assignee: Anil K Patel
> Priority: Minor
> Attachments: quickAdd.patch, quickAdd.patch, SFAContact.patch, SFAContact.patch, SFAContact.patch
>
>
> In OFBiz a Contact is a Person, which is a type of Party (the other main type being Party Group, which would correspond to an Account). For a more general description of the Party structure see the Accounts section above. Each contact will be in the Contact role. The following are screens and details for them related to a contact.
> These may be best as separate screens or as desired certain ones can be combined.
> Find Contact
> • Accessed from the application/header level "Contacts" tab
> • Includes a search fields entry form and a search results display form
> • All search results will be filtered by Contacts the current user is associated with (PartyRelationship in relationship of type CONTACT_REL TO logged in user) 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 "CONTACT" roleTypeId.
> • Includes a link to the Create/Edit Contact page with no "partyId" to identify the account for the purpose of creating a new Contact; note that for Edit Contact the partyId can correspond to either the Group or Person. After a contact is created, it should be setup in Relationship of type CONTACT_REL with logged in user.
> • Contact Home (Summary)
> • This page will include summary information for the account including basic Contact
> fields plus other related information (to be defined....)
> • Will have link to and information about Account associated with contact; since this
> is modeled as a PartyRelationship can theoretically have multiple Accounts but the
> UI will limit the setup of a single Account per Contact.
> • Create/Edit Contact
> • If a "partyId" parameter is passed in this page will act as an Edit Contact page (the
> partyId can for the Group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.