ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharan Foga (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OFBIZ-2427) Cases - Sales Force Automation component
Date Sat, 21 Feb 2015 07:38:47 GMT

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

Sharan Foga updated OFBIZ-2427:
-------------------------------
    Sprint: Bug Crush Event - 21/2/2015

> Cases - Sales Force Automation component
> ----------------------------------------
>
>                 Key: OFBIZ-2427
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2427
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: marketing
>    Affects Versions: Trunk
>            Reporter: Ashish Vijaywargiya
>            Priority: Minor
>
> - A case corrospond to a Request(CustRequest) in OFBiz.
> - There are many types of requests including RFI (for information), RFQ (for quote),
RFS (for support), and so on.
> Following screens should be implemented in this :
> - Create/Edit Case: Following fields should be present on the GUI.
> "* (Start next to fields)" - showing the required field.
> — Company Name - Lookup showing all the Party Group in the role of "Account"
> — Requesting Party* - Lookup to select the existing party in the role of "Contact"
> — Priority - Keep default priority as the medium (either 4 or 5 on the user interface)
> — Type
> — Subject* - Map this field into custRequestName field of CustRequest entity.
> — Reason - associate this field with the enumeration entity and create few records
there so that it could be referred here.
> Reason can be "Unexpected Behaviour of Application", "New Feature Request" etc.
> — Description -
> — Status - Show this field in Edit mode of request only. (While updating request)
> - There will be summary section for the cases and following block will be shown in it.
> — First block will be the history of the customer request.
> — Party / Roles - All will be shown in the read mode (Party Group, Requesting Party
& Logged in party details who has created request).
> — Request Items.
> - There will be following tab button adjucent to Summary Section.
> — Party / Roles(The two records for Party Group and Requesting Party will be in readable
mode. and user should only be able to change the details of Request Tracker i.e the person
who has logged in the Request.)
> — Request Items
> Details Left Navigation Section.
> First Block: Shortcuts
> Create New Case
> Find Case
> My Cases - List all the cases of logged in party by default. So it will be easy for him
to select and update on those cases accordingly.
> Only show those cases that are not in complete status.
> Second Block: Quick Add Case
> Fields to be present in this block are:
> Company Name
> Requesting Party*
> Subject*
> For the quick add case block we should keep the default priority as medium (i.e 5)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message